The choice to build A.I. Kung Fu on Blogger is deliberate and requires explaining, because the instinctive developer reaction is to reach for a static site generator, a headless CMS, or at minimum WordPress.
The Infrastructure Argument
Blogger is Google infrastructure. It does not go down. It does not require a server, a hosting bill, an SSL renewal, or a deployment pipeline. It scales to any traffic level without configuration. For a tool archive targeting under-resourced institutions across East Africa, the operational overhead of maintaining a self-hosted platform compounds over time into a site that stops being updated because the maintainer is doing something more important.
The best infrastructure is the infrastructure you never think about. Google has been running Blogger since 2003. The probability that it is running in 2031 is higher than the probability that any self-hosted platform I deploy today will still be operational and updated. Reliability at zero marginal cost is a serious value proposition for a project whose resources should go into tools, not uptime monitoring.
The Publishing Pipeline
The publishing pipeline runs through Google Apps Script — a scheduler that creates scheduled posts via the Blogger REST API, with full HTML content embedded, publishing on a monthly cadence. Zero manual intervention. The editorial work happens in Python and plain text. The deployment is automated. The tools in the sidebar are what matter. The site is the delivery mechanism. The delivery mechanism should be invisible.
Responses