How this website works
This post explains how this website (jonathandupre.com) works. You can use it as an example when you need to describe one of your own systems.
I bought jonathandupre.com in 2012, but the current iteration started in January 2019.
$ whois jonathandupre.com | grep "Creation Date" Creation Date: 2012-05-24T02:26:50Z
Blog posts are written in Markdown, with YAML front matter.
The build script is mostly made up of a bunch of parsers: markdown, pug (html), and stylus (css). It recursively reads templates and content directories. It then builds HTML pages, a CSS file, and RSS/Atom feeds. It also copies over static assets like images and text files.
The watch script is just a wrapper around budo, a Node.js dev server. budo watches the filesystem and calls the build script when something changes.
One is the Fathom Analytics bundle. It counts visitors and views in a way that preserves privacy. I pay US$ 14 a month for this service.
The other one is from ConvertKit and it makes the email list subscription box work. I pay US$ 9 a month for this service.
The code is hosted on GitHub. I use two branch, the main branch and a development branch.
Netlify hosts the website. They integrate with GitHub. Everytime I merge my changes into the main branch, Netlify runs my build script and deploys the new assets so that they can be served by their web servers.
The DNS records are hosted for free with Namecheap. There's a CNAME at
www. that points to the A record, which points to Netlify's load balancers.
The domain name costs me around CA$ 15 a year. That brings the total to about CA$ 30 a month, or CA$ 360 a year.
The website takes under 2 seconds to build. Updates are live under 2 minutes.
And that's about it! I hope this gave you a good example of how you can describe one of your systems.
I hope you found this valuable
I send out an e-mail whenever I publish new content. It's free. No spam. Unsubscribe whenever you want.