some ideas on the structure of documentation
I have three ideas and one question which all need to be brainstormed.
-
How do you feel about incorporating
readthedocs
as an additional or alternative documentation source for the RegiKlim or Nukleus project? Currently both regiklim.readthedocs.io and nukleus.readthedocs.io are free. -
What are your thoughts on focusing of this repo on the entirety of the RegiKlim project, rather than limiting our scope to just the Nukleus documentation?
-
I'm considering migrating our documentation repository using the Hereon cookiecutter template, which is built on cruft. This move aims to standardize our documentation and integrate
readthedocs
and some other pros in Gitlab CI/CD within this repository. What's your opinion on this approach?
@k204230 Additionally, I have a question regarding the RegiKlim project documentation. Could you outline the steps and necessary endpoints for hosting our Regiklim or Nukleus documentation as a sublink on docs.dkrz.de? Is there any documentation for this purpose?