add redirection to docs.epics-controls.org #21
Conversation
|
LGTM! |
all links will now redirect to docs.epics-controls.org in order to centralize the documentation (instead of having a whole dedicated sub-website for how-tos)
|
@minijackson : any comment/suggestion? |
|
Looks fine. |
|
Looks good. I'm wondering though, if these pages are now redirected, we can remove them all? And clearly mark the repository as deprecated. @stephane-cea do you want to do that? Or we can do it in another PR. |
|
I can remove the sub-project on RTD. Just ping me. |
Ho yes that's a good idea, I'll do that now |
…ps://github.com/epics-docs/how-tos)) in order to avoid confusing users/contributors because thoses pages have now migrated to the [epics-docs repo](https://github.com/epics-docs/epics-docs)
especially about the current state of this repo (the [how-tos repo](https://github.com/epics-docs/how-tos)), i.e. it should be now considered deprecated/archived also about the migration of the pages and the redirections of the associated old links to the new location of the pages
done |
|
I can confirm that the redirections are working as intended on https://docs.epics-controls.org/projects/how-tos/en/latest/. Now, they are currently two open PR (#10 and #11): I will ask them to migrate to the epics-docs repository. I think we could archive the project now. It seems that even if archived (read-only public archive), it should still appear on readthedocs. For example, I found this project in an archived state since 2021 that still renders on readthedocs: https://addwiki.readthedocs.io/en/latest/ / https://github.com/addwiki/readthedocs. |
All links will now redirect to docs.epics-controls.org in order to centralize the documentation (instead of having a whole dedicated sub-website for how-tos).
If this pull request is merged, then one might also want to consider archiving this project.
fyi @gabrielfedel