Skip to content
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

Create an "older versions" page and link to it #6130

Closed
1 task done
dbeatty10 opened this issue Sep 24, 2024 · 2 comments
Closed
1 task done

Create an "older versions" page and link to it #6130

dbeatty10 opened this issue Sep 24, 2024 · 2 comments
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear

Comments

@dbeatty10
Copy link
Contributor

Contributions

  • I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates

https://docs.getdbt.com/docs/dbt-versions/core-upgrade

What part(s) of the page would you like to see updated?

Clicking on the "Older versions" tile should go to a stand-alone page that has a listing of the older versions:

image

As it currently stands, it links to this page instead, which was unexpected.

The only way to get to a specific older version is to use the navigation menu on the left:

image

Additional information

No response

@dbeatty10 dbeatty10 added content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear labels Sep 24, 2024
@mirnawong1
Copy link
Contributor

hey @dbeatty10 , thanks for raising this! I've spent a couple of days looking at this and it looks like if we add an autogenerated index config, docusaurus duplicates the 'older versions' subfolder. They have an open git issue but we're not sure how to exclude a specific file/directory from being included when using the auto-generated sidebar. also, in terms of viewership - in the past 6 months we've seen ~ 2,009 distinct users view the older versions guides.

i think based on the workload needed and numbers, the best course of action is to close this issue out and come back to it if we get more people viewing them or a solution pops up. does that work @dbeatty10 ?

@mirnawong1
Copy link
Contributor

Screenshot 2024-11-05 at 14 35 43

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear
Projects
None yet
Development

No branches or pull requests

2 participants