The best tool is often the one I can understand under pressure. A complicated system may be impressive, but if it fails in a way I cannot debug, it becomes a liability.

For this site, the technical choice is plain Jekyll. Static files are easy to host, easy to back up, and easy to inspect. There is no database to maintain and no heavy client application to ship.

My tool selection checklist:

  • Can I explain how it works?
  • Can I run it locally?
  • Can I recover if it breaks?
  • Does it reduce maintenance instead of adding hidden work?

Simple does not mean weak. Simple means the moving parts are visible enough to trust.