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

Steps to reproduce

https://docs.nextcloud.com/server/20/admin_manual/installation/harden_server.html#connections-to-remote-servers

Expected behaviour

documentation should also mention connections required for featured apps.
for example

• apps are downloaded from github not from apps.nextcloud.com (github is using cloud storage for some assets)
• weather is connecting to ...?

During the work on merging #1419 I figured out that the basic BUFGMUX example works differently on Arty Board and Nexys Video.

The example uses three LEDs:

• led[2] - blinks with slow frequency
• led[1] - blinks with high frequency
• led[0] - blinks with the same frequency as led[2] or led[1] depending on sw[0] state.

On the Arty Board, the example works as intended. On Nexys Video, when

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