Repository navigation
docs: Delete the legacy versions page - #2042
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
marcleblanc2
changed the title
9dedef5 to
02947e7
Compare
|
@enriquegh this PR is at odds with retaining the v6 docs, but I haven't yet sorted out how / when / why retain the v6 docs as legacy. |
I would say we can remove mentions from prod docs but just not delete the In terms of the "why" still retain v6 is simply that we are still too early in 8.0 to fully erase 6.0 (at least IMO). This is a thought for somewhere else but maybe we can define some sort of policy where after X months (or minor releases?) we then do the cleanup so that come 9.0 this is easier to do |
The version dropdown already links every supported version's docs site (8.x latest, 7.x); /legacy duplicated that list and added only unsupported majors (3.x-6.x), and had to be edited by hand every release. - Delete docs/legacy.mdx and redirect /legacy to /releases - Drop the 'Legacy versions' item from the version dropdown - Drop the page's Algolia product mapping - Drop the page from the publishing-docs-versions skill Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-01a0e411-740d-71b7-8c31-99c244094a01
02947e7 to
9d857a3
Compare
This branch was successfully deployed
2 participants
Follow-up to #2038 (comment), the
/legacypage is not needed, so this PR deletes itdocs/legacy.mdx/legacyto/releasespublishing-docs-versionsskillAmp thread: https://ampcode.com/threads/T-01a0e411-740d-71b7-8c31-99c244094a01