We are fans of the humble colophon. By far our favorite Colophon was from three volume masterpiece, Plan of St Gall:
A long time ago... the last link in the chain of parts was christened "Colophon." The name seemed appropriate for a traditional sign-off: wording terse, content brief, usually limited to identification of type or types used in printing the work, possibly the paper on which it was printed, sometimes with a laconic reference to the printer -- all matters nearly disposed of in a slender paragraph.
This taciturn and habitual practice certainly seems restrictive in circumstances where so many have done so much to advance this work as it evolved from conception to realization. This not is thus intended as a supplement to the Acknowledgements, in order to include a few remarks concerning persons whose assistence has gone beyond routine courtesy in bringing these volumes to a superior level of printing design, craftsmanship and artisanship.
In a two large format pages at the end of The Plan of St Gall Born provided a detailed account of the making of the book, including enlisting the help of Beatrice Ward who had recently retired from Monotype, to alter "e" in the Monotype Italian Old Style font to make it more suitible for use in a modern scholarly work.
Modern Colophons, especially from the early days of Wired Magazine and the Whole Earth Catalog included not only information on fonts, paper and the printing process, but also included information on the types of computers, software and workflow that was used to produce these works.
Such colophons are a window into the art of the writer, editor, book designer and printer. They help to understand the tool chain used to create books, and sometimes even the workflow behind how it is done.
We hope to carry on this practice in the hope that others will do the same.
Diagrams are sometimes created using GraphViz by embedded code in the org-mode source files which generate the diagrams when exporting to html.
The content for the site is written using Org-Mode in Gnu Emacs, and then exported to HTML. The site is then generated using jekyll/, which is part of a Git repository, using Emacs Magit which is then pushed to the server whenever it is updated.