Dependencies must be included in the introspection data.

Related libraries are part of the project configuration.

Use the appropriate meta elements for the OpenGraph and Twitter, and
avoid duplication.

Put the site URL elements behind a configuration switch.

We're using broken links or plain headers.

* Bad licenses:
* Deprecated licenses:
* Licenses without file extension:
* Missing licenses:
* Unused licenses:
* Used licenses: Apache-2.0, CC0-1.0, GPL-3.0-or-later, OFL-1.1
* Read errors: 0
* Files with copyright information: 90 / 90
* Files with license information: 90 / 90

Congratulations! Your project is compliant with version 3.0 of the REUSE
Specification :-)

The sections should have the same order.

Instead of the index of functions twice.

Sadly, function macros are not matched to a type, so they all reside in
the global namespace. They also lack types for arguments, so they aren't
as nicely integrated as actual functions.

Fixes: #45

And add the library version while we're at it.

The `show_index_summary` configuration option can be used by the
template to show the summary of each top-level symbol in the namespace
index.

This just uses the value that we find in the config file.
For build integration, it might be nicer to feed that value
in from the commandline as meson.project_version().

The "record" name is part of the GIR data, but there's no reason to
expose it.

We want to use the metadata in the content files directly, and remove it
from the project's toml file. This allows us to keep content away from
project configuration.

And use a macro, to avoid repeating ourselves over and over again.

The namespace landing page should not have empty sections in the
sidebar.

Expose stability, availability, and possible deprecation notices.

We also expose the free-form annotations; in the future we might want to
use them to influence the documentation's output as well.

We use the same template for aliases, records, and unions, to cut down
on the proliferation of HTML templates. In order to do that, we use a
type-specific c_decl property.

Add collapsible sections, and make it a bit more nice.

We're doing a ton of string concatenation in a pre-processed
environment, where whitespace matters, so we cannot really use the
Jinja template conditionals inside a <pre> tag.

Generate an API reference for a given project using a template and the
introspection data for that project.

The basic template is still a work in progress.