What needs to be done?
This is a large effort (epic/project level) rather than a simple task.
Right now, our documentation relies on mkdocs. The way it works is that we store the documentation in the everest-doc repo across various branches. Then, in the openeverest.github.io repo, we run a hackish script that builds the docs and dumps plain HTML files into the website's openeverest.io/documentation folder.
This setup is too complex and prone to errors.
Ideally, we want to rework the documentation to use something more modern, like Docusaurus. We'd like to serve it directly from GitHub Pages and have a proper version picker in place.
Additional suggestions or changes to the overall documentation structure are also welcome.
Why is this needed?
No response
What needs to be done?
This is a large effort (epic/project level) rather than a simple task.
Right now, our documentation relies on
mkdocs. The way it works is that we store the documentation in theeverest-docrepo across various branches. Then, in theopeneverest.github.iorepo, we run a hackish script that builds the docs and dumps plain HTML files into the website'sopeneverest.io/documentationfolder.This setup is too complex and prone to errors.
Ideally, we want to rework the documentation to use something more modern, like Docusaurus. We'd like to serve it directly from GitHub Pages and have a proper version picker in place.
Additional suggestions or changes to the overall documentation structure are also welcome.
Why is this needed?
No response