Our current sitemap.xml covers the most basic case. Although, there are users with other needs that require a more customized sitemap.xml.

We should implement the same mechanism that we do for custom 404.html, where we provide the most basic one (Maze found) with the ability to change it by adding your own 404.html to the output generated by Sphinx.

So, we could check first for `sitema

refs: sphinx-doc/sphinx#3585 (comment)

@eric-wieser
Please let me know where you found the similar problem in apidoc.
I'll take a look

Please have a look at this page. The screenshot is way too big.
At least on my machine.

https://docs.nextcloud.com/android/android_app.html#connecting-to-your-nextcloud-server

Vendor tools dram tests were not enabled until #1234 got merged.

With SymbiFlow/symbiflow-arch-defs#1268 I have temporarily disabled the vivado_targets, to let CI go green (as it has been red for too long now).

This issue is to keep track of the problem with DRAM evaluated on vendor tools with fasm2bels.

It would be good to include in the documentation some guidance for users on how to get the most out of MyST; particularly those that haven't used rST before.

Most of the directives are documented at:

• https://docutils.sourceforge.io/docs/ref/rst/directives.html
• https://www.sphinx-doc.org/en/1.8/usage/restructuredtext/directives.html

So at a minimum these links should be provided. It w