Skip to content

Separate 5S-TES content from Weave/Patterns docs site - #196

Merged
AndrewThien merged 8 commits into
mainfrom
move-5s-tes
Aug 21, 2026
Merged

Separate 5S-TES content from Weave/Patterns docs site#196
AndrewThien merged 8 commits into
mainfrom
move-5s-tes

Conversation

@AndrewThien

Copy link
Copy Markdown
Contributor

This PR removed the docs related to 5S-TES. Also, add a note directing the reader to the new 5S-TES docs site.
This keep the route /five_safes_tes intact because the same route in the new docs redirects here.

@AndrewThien AndrewThien changed the title Separate 5S-TES content from this docs site Separate 5S-TES content from Weave/Patterns docs site Aug 20, 2026

@beforan beforan left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a question on this - since having redirects on the new site to preserve links to existing patterns and weaves pages is a thing that has come up, should we be keeping some of these routes as redirects to their new pages? I know it's not 1:1 for each document, but it might make sense to:

  • have the routes still work
  • have the routes not be in the nav
  • if there's an obvious choice to redirect to, automatically redirect.
  • if there's not an obvious page, add a page with options and links
    • e.g. where an old guide has split into multiple guides?

Or decide this is all too much maintenance effort and just deal with people finding broken links...

Thoughts?

@beforan

beforan commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Or decide this is all too much maintenance effort and just deal with people finding broken links...

I guess the very easiest version is to have a custom 404 inside five_safes_tes or software routes to say that the docs have moved (similar to the base five_safes_tes route as modified in this PR)?

@AndrewThien

Copy link
Copy Markdown
Contributor Author

Or decide this is all too much maintenance effort and just deal with people finding broken links...

I guess the very easiest version is to have a custom 404 inside five_safes_tes or software routes to say that the docs have moved (similar to the base five_safes_tes route as modified in this PR)?

yeah, I think this is a good idea. I will make it

@AndrewThien

Copy link
Copy Markdown
Contributor Author

@beforan I added a global custom 404. Whenever users enter a non-existent route, it will show the 5S-TES has moved and other links.

@AndrewThien
AndrewThien requested a review from beforan August 21, 2026 10:40
@AndrewThien
AndrewThien merged commit 77804d9 into main Aug 21, 2026
4 checks passed
@AndrewThien
AndrewThien deleted the move-5s-tes branch August 21, 2026 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants