Chapter One — Your Shelf
You didn’t choose the website business. It accumulated.
One chapter site became ten. Ten became a hundred. Now a small team keeps the lights on for a whole fleet — run day to day by volunteers, club officers, and chapter presidents who rotate every single year.
Chapter Two — The Rulebook
Nobody signed up to be the website police.
Keep a hundred sites safe on a platform where anyone can install anything, and the rules pile up: allowed plugins, banned plugins, version audits, access reviews. The rulebook gets thicker every year — and enforcing it became somebody’s job. Probably yours.
Plugin review ledger
- page-builder-provulnerable
- classic-contact-formsabandoned
- woocommercebanned
- bulk-mail-blasterbanned
- community-members-plusbanned
- gallery-magic-liteawaiting review
- seo-toolkit-freevulnerable
- event-calendar-classicawaiting review
+ 47 more awaiting review…
Chapter Three — The Trap
Moving hosts moves the servers. The job stays with you.
A new managed host takes the racks off your hands — and mails the rulebook right back. The patching, the policing, the volunteer tickets at nine p.m.: none of that lives in the server room. It lives on your desk.
Still on your desk
- Vet and patch the plugins
- Police the rulebook
- Answer the volunteer tickets
- Audit the admin accounts
- Restore what broke overnight
Chapter Four — The Shift
AI is good at code. So the rules become physics.
Code used to be the expensive option — that’s why everyone settled for page builders. AI flipped it. Sites that live as clean, modern code are now the easiest ones to keep perfect.
01
Nothing to patch
There are no plugins. Not banned — nonexistent. Every site is clean, modern code.
02
Nowhere to leak
No per-site database means a chapter site can’t quietly become a shadow data store. Governance by architecture.
03
No one to police
Editing access is need-to-edit by construction. There’s no admin panel to lock down.
Chapter Five — Tuesday, 9:14 PM
Sarah has one job tonight.
Sarah '09 — Club webmaster, three weeks into her term
Sarah became her club’s webmaster three weeks ago, the way volunteers always do: somebody asked. In the new world she types what she wants. A preview comes back. She approves it. The edit happened in code — made by AI that’s better at code than any page builder is at being a page builder.
Volunteer: Move our spring dinner to the Hilton ballroom and make the RSVP deadline Friday.
Website: Done — here’s a preview of the updated events page. Publish?
Volunteer: Publish. Thank you!
The same Tuesday, in the old world
- 1.Find the login. Reset the password.
- 2.Dismiss three update warnings.
- 3.Fight the page builder for the events block.
- 4.Break the mobile layout. Undo. Retry.
- 5.41 minutes later: it’s almost right.
Chapter Six — The Crossing
Leaving used to be unthinkable. Now it’s a batch job.
Hand-rebuilding a hundred sites is what kept everyone trapped — the cure cost more than the disease. AI rebuilds in waves: from a backup file or a live URL, no server access, no migration plugins. Every site is reviewed and approved before it goes live.
Wave zero — the pilot
A handful of sites, one of each kind. Real volunteers use them for thirty days.
Waves one through n
The rest move in scheduled batches — mapped, rebuilt, and reviewed site by site.
Cutover
Domains switch only when each site is approved. Nothing flips before it’s ready.
Chapter Seven — The Door
Every reader gets their own volume.
We write one of these for every organization we work with — your sites, your plan, your numbers. The next chapter is a conversation.