Skip to content

Remove v2.0-preview docs and clean up old redirects#1105

Open
adamwg wants to merge 3 commits into
crossplane:masterfrom
adamwg:awg/rm-preview
Open

Remove v2.0-preview docs and clean up old redirects#1105
adamwg wants to merge 3 commits into
crossplane:masterfrom
adamwg:awg/rm-preview

Conversation

@adamwg
Copy link
Copy Markdown
Member

@adamwg adamwg commented Jun 5, 2026

v2.0-preview was the docs branch for the v2 RC releases last year. v2 is now the main content of the docs, and v2.0 is EOL, so we should clean these up.

While we're here, clean up old redirects for EOL v1.x releases and replace them with a generic redirect that covers all EOL versions.

adamwg added 2 commits June 5, 2026 10:12
v2.0-preview was the docs branch for the v2 RC releases last year. v2 is now the
main content of the docs, and v2.0 is EOL, so we should clean these up.

Signed-off-by: Adam Wolfe Gordon <awg@upbound.io>
The netlify config had redirects for v1.10 through v1.12 to the latest
docs. Most of these redirects would result in a 404 anyway, since the structure
of the docs changed significantly in v2.

Signed-off-by: Adam Wolfe Gordon <awg@upbound.io>
@netlify
Copy link
Copy Markdown

netlify Bot commented Jun 5, 2026

Deploy Preview for crossplane ready!

Name Link
🔨 Latest commit a52f568
🔍 Latest deploy log https://app.netlify.com/projects/crossplane/deploys/6a231d5f18dee00008e34fce
😎 Deploy Preview https://deploy-preview-1105--crossplane.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 93 (🟢 up 1 from production)
Accessibility: 90 (🔴 down 2 from production)
Best Practices: 92 (no change from production)
SEO: 100 (no change from production)
PWA: 70 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Copy Markdown
Member

@jbw976 jbw976 left a comment

Choose a reason for hiding this comment

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

Cool, this seems like the same experience folks would have going to a v2.0 docs link which was EOL'd with the v2.3 release - so status quo would be achieved.

However, should we consider just reviving this redirect process that seems to have died with v1.12? e.g. should we keep these redirects, add ones for all other EOL'd versions since then, and update the release issue template to include adding a new redirect with each release? 🤔

that may be a nice way to go here, to at least give a chance for an old link, that still has a content path that exists on newer versions, to work. what do you think?

Add a Netlify redirect using placeholders and globs to redirect all requests for
EOL (deleted) docs versions to latest. This might still return 404 for docs that
have moved (e.g., most v1 content), but will work for many common cases where
our docs are relatively stable. The redirect rule relies on the fact that exists.

Signed-off-by: Adam Wolfe Gordon <awg@upbound.io>
@adamwg
Copy link
Copy Markdown
Member Author

adamwg commented Jun 5, 2026

However, should we consider just reviving this redirect process that seems to have died with v1.12? e.g. should we keep these redirects, add ones for all other EOL'd versions since then, and update the release issue template to include adding a new redirect with each release? 🤔

that may be a nice way to go here, to at least give a chance for an old link, that still has a content path that exists on newer versions, to work. what do you think?

@jbw976 I've pushed a commit that adds a wildcard redirect to cover all old versions. It will still return a 404 if a page doesn't exist in the latest docs, of course, but should work for many common cases since most of our docs are pretty stable.

This redirect relies on the fact that Netlify won't redirect requests for pages that exist. I tested it by manually building the docs with the netlify_build.sh script locally and then serving them as static content with netlify dev -d public --framework '#static'.

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