DocumenterVitePress and documentation stability

[lkdvos]

Currently the documentation is rendered by DocumenterVitePress.
While I do like the overall looks, there are quite a number of issues related to this that are not that easy to solve, and it might be worth it to just switch back for now instead of working through them.

See also

• Markdown titles in docstrings not rendering properly in published docs pages #477
• Documentation search can't target html identifiers in the lib page #478
• docs: vendor the VitePress config; serve static assets from public/ #497

[borisdevos]

Could you summarise what these issues are? Most important to me is which we have control over, and which are restrictions of DocumenterVitePress. To give an example, current docs don't render the references properly, but there's an open PR already aimed to fix this.

[lkdvos]

Apart from the ones mentioned by Lander and the references I don't know if there's that many more, but I think I got slightly less enthusiastic about having to maintain things like this ourselves