The documentation on hackage for gdk_rgba_parse reads

A hexadecimal value in the form “rrggbb”, “rrrrggggbbbb”

On developer.gnome.org, it's:

A hexadecimal value in the form “#rgb”, “#rrggbb”, “#rrrgggbbb” or ”#rrr

rustdoc has the doc_alias feature that you can see in action here (the two first items are aliases).

Considering that most examples for GNOME libraries are in C, I assumed that users could be looking for the C function in our doc. By adding aliases on our items, we would also return the rust one.

this section of the readme has an example of subclassing a widget. Its quite common to want to add a composite widget template for a custom widget.

The c documentation says you need to do the following:

• Call gtk_widget_init_template in your _init function

Currently code blocks just get left as is, it would be nice to have them parse properly. An example is this:

|[<!-- language="C" --> enum {

PROP_0,
PROP_FOO,
PROP_LAST

}; ]|

It should be possible to get the parser to recognize these blocks and swap them out for proper markdown blocks.

There really shouldn't be two doc directories. The reason, why we currently have to rely on them is stated in docs/README:

My Git host automatically publishes html files in the 'docs'
directory to a website.

Perhaps this can be reconfigured on a per-project basis, so that we can build doc/guile-gi.html from Automake without needing a local rule. Perhaps this has to be configured f

Generate documentation automatically for the GI lib bindings generated

• find an xml parser
• in the Loader use the xml parser in order to get documentation string and add it in the mli files.