#16 Stable URL for the current version's documentation
Closed: Fixed 2 years ago by darknao. Opened 6 years ago by bex.

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):

  1. Use a redirect on the server. The negative is that this means infra will have to act every time we publish.
  2. Publish the current docs under the "current" label only and then give them an fXX number once they are no longer the latest
  3. Publish the docs twice once as fXX and once as current. This is implementation ugly, but doesn't seem to cause any real problems.

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.

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).

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

2 years ago

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

2 years ago

Metadata Update from @darknao:
- Issue tagged with: stg

2 years ago

Metadata Update from @darknao:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Log in to comment on this ticket.

Metadata
Boards 1
Tooling Status: In Progress