Make tech stack update plan

[rogerkuou]

As time goes, the old tech stack of sarxarray needs some updates.
The followng points should be considered. And each point needs to become a spearate issue

• Python dependencies: uv seems to be a much faster and easier option than mamba.
• Documentation: mkdocs has issue with supporting version 2. -> consider go with the classic ReadthDoc + sphinx? Zensical seems to be risky for long-term
• Documentation brokean link catch up -> lychee
• If still using MkDocs, consider autodoc for API documentation?

[weiji14]

Documentation: mkdocs has issue with supporting version 2. -> consider go with the classic ReadthDoc + sphinx? Zensical seems to be risky for long-term

Given that mkdocs-jupyter is being used, I think Zensical wouldn't be suitable short-term either (zensical/backlog#9), even though it is supposed to be the closest replacement for the current Material for mkdocs stack. Unless you want to convert the Jupyter Notebook to markdown 🙂

• If still using MkDocs, consider autodoc for API documentation?

I'll also mention that there are autodoc <-> sphinx integration. E.g. jupyter-book/mystmd#1259 (comment) mentions https://sphinx-autodoc2.readthedocs.io/en/latest/quickstart.html#using-markdown-myst-docstrings.

Either way has its pros and cons, so take your time to decide! Readthedocs is definitely a good site for hosting though, you can see https://docs.readthedocs.com/platform/stable/intro/doctools.html#popular-documentation-tools for how to set up different options.