-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add a header for legacy version docs that they are not for current version #1389
Comments
I agree this would be helpful for users, especially if they're unaware they aren't on the latest version. We could try adding an announcement bar (see below), with text like: "You are on the Pomerium <vX.XX> docs website. This documentation is outdated. To view the latest documentation, please go to https://pomerium.com/docs." export default {
themeConfig: {
announcementBar: {
id: 'old_version',
content:
'You are on the **Pomerium <vX.XX>** docs website. This documentation is outdated. To view the latest documentation, please go to https://pomerium.com/docs.'
backgroundColor: '#fafbfc',
textColor: '#091E42',
isCloseable: false,
},
},
}; |
great idea. +1 |
@desimone, do you have any context on how the older docs sites are hosted? Would we need to restore some of the Git history for the docs site deleted in pomerium/pomerium#3420 in order to make updates to v0.10 through v0.17? |
@kenjenkins and @desimone I went ahead and started implementing this, but to Ken's point, the available branches in |
Implemented. |
What's incorrect or missing
The user may not necessarily notice that these are not current docs.
We've got users citing legacy version documentation every week, even if they're just starting with pomerium.
What's the resolution?
Add a header that documentation is not for current version, and link to current.
The text was updated successfully, but these errors were encountered: