Adding Docker changed the build from running in the Erlang shell, to using the Docker container's interactive shell. The Dockerfile (1.) compiled a small Erlang program to produce a BEAM file that could then be executed on the Erlang VM, and (2.) ran the sequential Erlang program as a common script and then exited.

Docker Compose simplified how the program was launched. Development containers (dev containers) — which can be used with or without VSCode — are another (optional) layer to ensure environmental reproducibility.

In the next version (v0.2.0), Rebar3 — a build tool and package manager for Erlang — was used to auto-generate the application structure (in a subdirectory, subsequently moved into the root). Note: Rebar3 does not replace the OTP file structure, instead it enables building OTP-compliant applications. The 'hello.erl' example was also updated.

The component hierarchy is shown in Figure 1, which illustrates the nesting of the seven component types (eight types, if the ErrorBoundary component is counted).

All of the components are written in pure React (ie. not using Flux or Redux since this is a simple demo), and pass data to one another as shown below:

Full source code for the project is available on GitHub.

A demonstration of the docSkimmer theme is available on its own documentation site, which uses the theme straight out-of-the-box.

Another example of a project documentation site using the docSkimmer theme demonstrates how this theme can easily be customized.

Related projects:

• Check the compatibility of docSkimmer theme and MkDocs versions, without having to install either locally, using docker-for-docskimmer.
• Add (persistent, preferred and/or alternate) external stylesheets to custom MkDocs themes using mkdocs-docstyler-plugin.
• docSkimmer theme has also been ported for Jekyll. See a demo on my GitHub Pages site. Get the latest version of jekyll-docskimmer-theme.

          $ git add .
          $ git commit -am "this is my commit message"
          # or for Trac users:
          $ git commit -am "#123: this is my commit message"
          

          $ git add-msg
          

There is no follow-up cutting-and-pasting of commit hashes to Trac required either, since a comment with a link to the changeset and repository (as well as the commit message itself) is automatically added to the specified Trac ticket. The $ git log information for each commit is added to a plain text changelog file as well — which could be copied or attached to another issue-tracking or ticketing system, if desired.

Features of git-add-msg (version 0.1.1) include:

• Supports multi-line commit messages (note: supported yes, but display is a known issue...);
• Enforces non-blank commit messages;
• Automatically generates link to changeset including repository name in the Trac ticket comment (useful when more than one repo is being used per same Trac environment);
• Enables changing the name of the repository associated with Trac ticket using the -r option;
• Displays an error message if the Trac ticket is not/cannot be updated.

Enjoy!