Website: Links on snapshot versions of /docs/home/ point to current version of docs

Created on 8 Oct 2019  路  14Comments  路  Source: kubernetes/website

All links on the "Home" tab of archived versions of the documentation, point to the current documentation:

Links on other tabs (e.g. "Setup", "Concepts" etc.) point to pages within the selected version of the docs, which is what I would expect browsing documentation for a specific Kubernetes version.

areweb-development kinbug lifecyclrotten prioritimportant-longterm

Most helpful comment

To save time on discovery: the Home page behavior may be a function of how paths work in the docsportal_home layout, which /content/en/docs/home/_index.md applies.

All 14 comments

/kind bug

Thanks @abstrask for bringing this to our attention!

I also noticed that the "latest version" link in the "Kubernetes v1.13 documentation is no longer actively maintained. The version you are currently viewing is a static snapshot. For up-to-date documentation, see the latest version." message doesn't point to the latest version.

To save time on discovery: the Home page behavior may be a function of how paths work in the docsportal_home layout, which /content/en/docs/home/_index.md applies.

I also noticed that the "latest version" link in the "Kubernetes v1.13 documentation is no longer actively maintained. The version you are currently viewing is a static snapshot. For up-to-date documentation, see the latest version." message doesn't point to the latest version.

Yes, and I think this is covered by #16066.

/priority important-longterm
(I think)

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

/area web-development

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Was this page helpful?
0 / 5 - 0 ratings