tree d9f29f6f039c859f7cface9ab7d027e306d867d2
parent 87a3a54cd937b037f531fedac243350933dd1eb7
author Richard Levasseur <rlevasseur@google.com> 1703033504 -0800
committer GitHub <noreply@github.com> 1703033504 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlgjqwCRBK7hj4Ov3rIwAAZnYIAEAED/M4jrniY9aYPqOZ0TUA
 +cpaj2EF0Q7SVv+BXnFgzPukJKrxmNnUJZ3GWew2LNWyIoUqn6pVMkRfivuYDuX1
 Hk1gHqfMqLu25nnS/ASBm5/Cf2r6zTqKq+xy2SOwiJUzy+d4vvqihM/jEU4/tIop
 HKdY7VKj4Ifgph9ejPAWzKRw57bxcX6/Bpf5xZIZQEjlkb3bXwdQ6Juo6LgfCred
 vVUZrjCH+Irqx10gGKehbF81k+c/urn8NKDQBK4lr7ovY6fnlgo1tDv7vwGFmnuC
 XBMBi/yE6zOVc+snUpk5vf4tPz0KLwoHN8qC9X31fMZO3JpXOkHwfk1hc64rE+o=
 =/46+
 -----END PGP SIGNATURE-----
 

docs: use stardoc proto output to generate markdown docs (#1629)

The template language Stardoc uses (Velocity) is niche and fairly
esoteric, and requires a lot of experimenting to understand how to
make it produce the desired output. In particular, it largely assumes
whitespace doesn't matter, which makes it a poor fit for generating
Markdown, where whitespace often does matter.

Instead, a small Python program is used to consume the binary proto
output of Stardoc, which converts it to Markdown. This also makes it
easier to customize the overall output and re-use code for the different
types of objects rendered.

The visible changes to the docs are:
  * Module extensions are now documented
  * Repository rules follow the style of the other generated docs
  * Fixed the rendering of pip_repository docs -- it had an h2
    section which broke the section grouping of the API objects.
  * Puts some padding between the border and content for text in
    params/attrs/fields listings.

Other notable changes:
  * Make RTD builds use bzlmod. This is necessary so that the pip
    extension can be documented. It loads
    `@pythons_hub//:interpreters.bzl`, but that repo is only created
    when bzlmod is enabled)

---------

Co-authored-by: Ignas Anikevicius <240938+aignas@users.noreply.github.com>