The project documentation for Hexatomic is built with mdBook. mdBook is built in Rust.
Development, i.e., additions and changes to the project documentation, are
pushed to the src
branch, i.e., the default branch. Travis CI automatically
picks up the changes from this branch, makes the build, and pushes the product
to the
master branch,
from where it is automatically rendered on
hexatomic.github.io via the
GitHub Pages functionality.
GitHub Pages looks for a repository in
a GitHub organization
called {organization}.github.io (e.g.,
hexatomic.github.io), and will try to render the files in the master branch
of this repository.
You do not need to install Rust in order to build the documentation. Instead, mdBook is provided in binaries served from the project's GitHub releases page.
In order to build, you need:
The documentation has been set up by running mdbook init --theme in the
root directory of this repository. This created a skeleton mdBook installation
as well as copied the theme files. In this version of the documentation,
only the Handlebars template file
index.hbs has
been changed (you can compare it with the original file by running
mdbook init --theme in another directory to create a vanilla setup of
mdBook, and then diffing the two index.hbs files).
To build the documentation, run mdbook build in the root of this repository.
To serve the documentation locally, run mdbook serve in the root of this
repository. Without customization, the documentation will be served at
http://localhost:3000/.
The documentation is hosted as a GitHub page on <hexatomic.github.io>.
The deployment is automated via Travis CI continuous
integration, see section deploy in the Travis configuration file
.travis.yml.
The structure of the documentation is configured in
src/SUMMARY.md. Only files that are added to the structure
there appear in the documentation.
To add new sections to the documentation, create a
Markdown file called
{name}.md in a reasonable place in the src directory.
Add a link to your file to src/SUMMARY.md to render it, either in the front or
back matter (as a simple Markdown link [text](relative path)), or in the
nested list of contents (as a Markdown list item - [text](relative path)).
If you want to use images, place them in the same directory as your Markdown
file. Only files that are used globally should go in src/static/img/. This
makes it easier and less verbose to reference files in the Markdown (instead of
 you can simply use ).
mdBook uses the CommonMark specification of Markdown, specifically in its Rust implementation pulldown-cmark.
This is a generic Markdown implementation which is feature-complete and also supports tables in the PHP Markdown Extra syntax.
PDFs, or single page HTML views, of the documentation can be created via the print button in the upper right corner of the documentation. The browser can be used to print to PDF.
The Hexatomic documentation is licensed under a Creative Commons
Attribution-ShareAlike 4.0 International license
.
Copyright (c) 2018ff. The Hexatomic project team