There has been some discussion in the following tickets that has resulted in sidebars and other ideas about having docs.fp.o/current/XXX always point to the current release.
This could also theoretically help our google ranking because the url stays stable.
Is this something we want?
If so, I see three options for implementations (and am open to more ideas):
Antora provide a way to do that. We can set the latest_version_segment key with active (or current) and Antora will use that for urls for the latest version of components automatically. docs.fp.o/en-US/fedora/f35/ will become docs.fp.o/en-US/fedora/latest/ (or docs.fp.o/en-US/fedora/current/) but everything in the website will still say f35.
latest_version_segment
active
current
docs.fp.o/en-US/fedora/f35/
docs.fp.o/en-US/fedora/latest/
docs.fp.o/en-US/fedora/current/
f35
Downside of that is every "hard" links to docs.fp.o/en-US/fedora/f35/ will not work anymore. By "hard" link, I mean all links outside of docs website, or not using xrefs (like the homepage).
xrefs
The google ranking can be further facilitated by solving #187
Both also reduce the risk to end up at legacy Docs pages given the increasing ranking of /latest/.
Metadata Update from @darknao: - Issue assigned to darknao - Issue priority set to: Medium - Issue tagged with: in-progress, tooling
This is implemented on staging : https://docs.stg.fedoraproject.org/en-US/fedora/latest/
Deployment in production is waiting for the end of beta freeze (https://pagure.io/fedora-infra/ansible/pull-request/977)
Metadata Update from @darknao: - Issue untagged with: in-progress
Metadata Update from @darknao: - Issue tagged with: stg
Metadata Update from @darknao: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.