The Website Maintenance Pipeline

A small-business client texts or emails a change: new hours, a new price, a photo of the new sign. It becomes an issue in their repository. You add one label. An AI agent reads the site's rules, edits the content, and opens a pull request with a preview link and a reply drafted in the client's language. You check the preview on your phone and merge. That's the whole job: one label, one merge.This guide is that system, written from the one that actually runs two client sites: The architecture, and why each piece beat the alternative Every setup step as the exact prompt used, with full manual instructions underneath if your agent does something different The daily routine once it's running A catalog of every way it has broken so far, dated, with the fix A capacity model with the real measurements and sample sizes, so you can plug in your own numbers Who it's for: someone comfortable in a terminal who can read a YAML file. You don't need to be a working developer.What it isn't: a course on finding clients or selling care plans. You bring the clients.What you get: Lifetime access to the online guide, which keeps getting updated An offline copy (zip) that opens in any browser The starter code (zip), MIT licensed