There are two major tools used to make everything you read here: Markdown for the writing, and Caddy for compiling it.
Markdown is a form of markup designed by John Gruber and Aaron Swartz. The advantages of Markdown for writing is that it is a plain text format that makes converting to other formats simple. There are many tools for converting Markdown to HTML and PDF, where the final output can be more easily stylized. And since it is stored in plaintext, it can be created and edited in any number of text editors. Currently, I switch between iA Writer and Sublime Text for all Markdown writing.
All of these Markdown files are then served through Caddy, a new web server written in Go. Caddy has built-in support for rendering Markdown files to HTML using a basic template system. While it is not as powerful as Ghost or Hugo, it fulfills my needs, and I would be using Caddy even without the Markdown support as it supports negotiating SSL certificates through Let's Encrypt automatically.
Every file used for this site is hosted on GitHub. Updates are pushed directly to that repository, which Caddy pulls from to update the website. The only aspect of the site that does not change is the HTML portion of theme. Unfortunately, Caddy must be restarted for this to update, although it is rarely an issue as my theme does not see many changes.
One of my goals is for this site to render as quickly as possible. To test this, I use Yellow Lab Tools to see detailed metrics about my site. When building and updating the theme, I test against the site index to see the minimum downloaded code for each page. My goal is to keep the base CSS and HTML below 8k, allowing my longest articles to have their text downloaded on even the slowest of connections. Other metrics presented by Yellow Lab Tools point out any problems with the theme, whether it is overly complex CSS rules or server configuration issues.