Skip to content

docs: Add versioning to documentation #1533

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

Open
wants to merge 29 commits into
base: main
Choose a base branch
from
Open

docs: Add versioning to documentation #1533

wants to merge 29 commits into from

Conversation

hoxbro
Copy link
Member

@hoxbro hoxbro commented Mar 21, 2025

https://hvplot-test.holoviz.org

TODO:

@maximlt
Copy link
Member

maximlt commented Mar 22, 2025

Nice to see some progress!

I'm very much interested in a doc collecting your process and all the decisions and settings you've made. A big part of this system is going to be in AWS as far as I can see, and I would like to know how complex it is, the easiest way for me being to review this doc, as poking around in AWS isn't going to be effective.
I guess you're done with the exploration/looking around phase since you've started the implementation. I would like to know if you looked into relying on readthedocs? And if you did and decided not to use it, why?

@hoxbro
Copy link
Member Author

hoxbro commented Mar 24, 2025

I'm very much interested in a doc collecting your process and all the decisions and settings you've made

This was also what I had planned to do, but I'm not that familiar with AWS, so I wanted something that worked before I tried to write it up.

I guess you're done with the exploration/looking around phase since you've started the implementation

The exploration examined how other repos did it, mainly Bokeh and pydata-sphinx-theme. The current implementation is done to try out what is needed on AWS side of things.

I would like to know if you looked into relying on readthedocs? And if you did and decided not to use it, why?

I haven't given it much thought, but I chose to rely on something more fundamental. I don't have the time to learn a new tool for this task, and I would likely still need some settings in AWS. If we choose to move to another framework in the future, I don't think it would be that hard.

@maximlt
Copy link
Member

maximlt commented Apr 1, 2025

Ok, thanks for the details.

I don't have the time to learn a new tool for this task, and I would likely still need some settings in AWS.

I might be wrong but in my mind readthedocs is a simpler alternative deployment solution to AWS that doesn't require the user to learn about AWS or another cloud provider. It also has a free tier for community projects. So it'd be good if we could motivate why we decided to pick AWS over readthedocs. I have a vague memory that one limit we'd face with readthedocs was that our docs build time was over their limit?

@hoxbro hoxbro force-pushed the docs_version branch 9 times, most recently from 5ab9416 to a960525 Compare April 9, 2025 09:05
'json_url': 'https://hvplot-test.holoviz.org/switcher.json',
'version_match': switcher_version,
},
'show_version_warning_banner': True,
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will not show anything as the version for the dev build is clean and tested locally with an alpha tag, which shows the warning banner.

Comment on lines +50 to +56
- name: Validate version
if: ${{ inputs.target == 'main' }}
run: |
if [[ -z "$VERSION" || ! "$VERSION" =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
echo "❌ 'version' is required and must match format X.X.X (e.g. 0.11.1) when target is 'main'"
exit 1
fi
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding this here to fail fast.

@hoxbro hoxbro changed the title docs: Docs versioning (WIP) docs: Add versioning to documentation Apr 9, 2025
@hoxbro
Copy link
Member Author

hoxbro commented Apr 9, 2025

I need to update the hvplot-test.holoviz.org to hvplot.holoviz.org and decide on internationalization, but otherwise, it should be somewhat ready for review.

@hoxbro hoxbro marked this pull request as ready for review April 9, 2025 15:58
(github.event_name == 'workflow_dispatch' && github.event.inputs.target == 'main') ||
(github.event_name == 'push' && !(contains(steps.vars.outputs.tag, 'a') || contains(steps.vars.outputs.tag, 'b') || contains(steps.vars.outputs.tag, 'rc')))
uses: peaceiris/actions-gh-pages@v4
- uses: holoviz-dev/holoviz_tasks/docs-publish@docs_publish
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It also needs to be updated when holoviz-dev/holoviz_tasks#44 is merged.

@@ -52,8 +57,13 @@
'icon': 'fa-brands fa-discord',
},
],
'pygment_dark_style': 'material',
'pygments_dark_style': 'material',
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unrelated to docs versioning

@maximlt
Copy link
Member

maximlt commented Apr 30, 2025

These two links don't redirect to latest:

@hoxbro
Copy link
Member Author

hoxbro commented Apr 30, 2025

These two links don't redirect to latest:

Those will now redirect

@hoxbro
Copy link
Member Author

hoxbro commented May 2, 2025

We could also redirect https://hvplot-test.holoviz.org/docs to the latest for even more compact url.

@maximlt
Copy link
Member

maximlt commented May 2, 2025

We could also redirect https://hvplot-test.holoviz.org/docs to the latest for even more compact url.

Yep that'd be nice for /docs and /docs/ (there's no language called docs right? :) ).

@hoxbro
Copy link
Member Author

hoxbro commented May 2, 2025

Those also redirect now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants