sphinx

I saw there are repositories that have too many branches/tags failing when we try to re-sync their versions. An example of it is jupyterlab which has 61k versions:

▶ git ls-remote https://github.com/jupyterlab/jupyterlab.git | wc -l
61290

It fails on our side because we truncate the output of the command if it's too big: 'Output is too big. Truncated at 4718592 bytes.'. We cou

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

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

• The icon picture for uploading https://raw.githubusercontent.com/nextcloud/documentation/master/user_manual/images/contact_picture.png in the user_manual/pim/contacts.rst a picture for contacts should be as follows:
  

• This image is also out of date: https://raw.githubusercontent.

Context

Currently our footer is quite minimal, and auto-populated with some Sphinx flags to show things like the copyright etc.
However, many sites use the footer to provide contextual information for readers that scroll to the bottom, things like social media links, site navigation, etc.

Proposal

Our footer should be composable with components, similarly to how our header navbar

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