1.  Copy `make_ref_pages.py` from graphing-library-docs repository to
    create `bin/make_ref_pages.py` and then refactor to generate
    Markdown stubs for documentation pages.

1.  Write `bin/gen.py` to generate HTML pages from the Markdown stubs
    using the Jinja templates in the `theme` directory for debugging.

1.  Convert Jekyll templates from graphing-library-docs repository to
    Jinja and store in `theme` directory.

1.  Write `requirements.txt` file to install required Python packages.
    -   `beautifulsoup4`: for HTML manipulation
    -   `html5validator`: to validate generated HTML
    -   `jinja2`: for manual template expansion
    -   `mkdocs`: for website generation
    -   `mkdocs-exclude`: to exclude `.jinja` files from generation
    -   `python-frontmatter`: for manual template expansion
    -   `ruff`: for checking `bin` scripts

1.  Write `Makefile` to automate build and test.

1.  Modify documentation comments in some JavaScript files to remove
    stray backticks.

Notes:

1.  As of the time of this commit, the `mkdocs_data_loader` plugin
    must be installed directly from a `.whl` file or similar. It will
    be added to `requirements.txt` once the plugin is on PyPI.

1.  Jinja does not expand directives in Markdown files; it only
    expands those it finds in template `.jinja` files. Because of
    this, the Markdown stubs generated by `bin/make_ref_pages.py` have
    YAML headers but no bodies.

1.  The logic to set the `details` variable in `theme/main.jinja` is
    copied from the original Jekyll templates and modified by trial
    and error to produce (what appears to be) the right answer.  If
    pages contain extra information, or if information is missing, the
    most likely cause is an error here.

1.  At the time of this commit, no styling is applied to the generated
    pages and they do not contain headers, footers, or navigation.
    All of this should be added once a general site theme is developed.

1.  `bin/gen.py` defines a `backtick` filter to convert backtick'd
    pieces of text to `<code>` blocks. This is currently *not* used in
    the Jinja templates because (a) the existing documentation
    includes the backticks as-is and (b) I couldn't be bothered to
    figure out how to add it to MkDocs.

1.  Move configuration `mkdocs.yml` to `mkdocs-vanilla.yml`.
1.  Move logic to set `details` from `theme/main.jinja` to `theme/attribute.jinja`
    where it is actually used.
1.  Create new `mkdocs-material.yml` configuration file with mkdocs-material settings.
1.  Change configuration to load overrides from `overrides` directory.
1.  Copy template files *without* `main.jinja` to `overrides` directory.
1.  Modify `Makefile` to build `mkdocs-vanilla` (our own) or `mkdocs-material`.