-
Notifications
You must be signed in to change notification settings - Fork 30
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
Previous Releases link broken for ecosystem projects #235
Comments
Also, since ecosystem documentation is deploying to both |
@1ucian0 suggestions for how we should approach this? |
For the docs at the root path, whether it's |
Hmm... my idea of deploy in /documentation and in /providers seems that is not working. I'll take a look. |
This is not an On On |
To summarize the above discussion: Below are the places where the previous version URL can be clicked from. We need to make sure the URL works from each of these locations. Terra:
Ecosystem, old scheme:
Ecosystem, new scheme:
Right now, we hardcode to #259 will fix for all 3 scenarios the link from home, e.g.
I agree. We can do this via JavaScript looking at |
@1ucian0 now that we have redirects of Are you publishing old builds of the docs under Are we ever publishing anymore to |
I think what you have above still applies. Currently, old versions of Because the CDN redirect,
Depends a lot on the project. Not every project keeps old build. The documentation-ecosysytem change should not change what projects are doing.
That's right. |
Closes #235. As summarized in #235 (comment), we were only handling Terra properly. I used test driven development to ensure I handled all the edge cases. ## Leverages ecosystem redirects We are now successfully redirecting ecosystem projects, e.g. `documentation/experiments/` to `ecosystem/experiments`. That simplifies the edge cases we need to handle: we only need to handle Terra (`documentation/`) and Ecosystem (`ecosystem/<project>`). ## Adds `utils.js` file Having a dedicated JavaScript file for our logic will make it easier to find all our custom logic. It also allows us to test the contents with Jest.
The Qiskit Experiments 0.5 docs have just been published, and the Previous Releases links on the sidebar are broken because they're hard coded to
/documentation/stable/{{ version }}/index.html
:qiskit_sphinx_theme/qiskit_sphinx_theme/pytorch_base/sidebar.html
Line 21 in 29277ce
The Qiskit Experiment stable link is at
/documentation/experiments/stable/{{ version }}/index.html
, so this doesn't work. I would think the easiest solution is adding anotherhtml_context
variable for the path and letting users customize that inconf.py
.The text was updated successfully, but these errors were encountered: