-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Legacy Docs #1220
Remove Legacy Docs #1220
Conversation
Do we want to remove the v1 adopters as well? |
I'd be tempted to remove the long "feature parity" section in our roadmap as well. |
Yes for sure. |
With copying the docs back over into the original repositories, this should be a lot less controversial. |
This PR is based on top of the changes in #1218. |
@@ -30,3 +28,5 @@ | |||
|
|||
/docs/contributing/* /contributing/:splat 301! | |||
/docs/* /flux/:splat 301! | |||
|
|||
/legacy/* /flux/migration 301! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could theoretically redirect to GitHub, but that would require a bit of special casing... any strong opinions here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would go with the redirect to migration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the feedback!
Fixes: #1219 Signed-off-by: Daniel Holbach <[email protected]>
Signed-off-by: Daniel Holbach <[email protected]>
Fixes: #1219
Signed-off-by: Daniel Holbach [email protected]