Hi there,
I’m thinking about teaching a small group of web designers how to build simple client sites, without all the ongoing WordPress maintenance.
Nothing’s decided. There are no dates, no price and no format, and it might not happen at all.
Before I build anything, I’d like to hear from you. There’s a short form at the bottom of this letter, but let me tell you where the idea came from first.
How we got here
For years, WordPress plus a page builder was simply how lots of us built websites. Me very much included. I spent the best part of a decade teaching it.
And it made total sense. Page builders let people who didn’t think of themselves as coders build proper sites for proper clients. Plenty of good businesses were built that way, and nobody should feel daft about that. I certainly don’t.
But “no code required” always came with a bit of small print, didn’t it?
You log in to a client site you haven’t touched for a couple of months, and there’s a stack of updates waiting.
You run them, then click round every page to check nothing’s broken.
Sometimes something has.
There’s the security plugin emailing you about login attempts from the other side of the world.
The hosting plan, the builder licence and the add-ons, all renewing every year for a brochure site whose content changes twice a year.
And the clicking. Into a panel, into a tab, hunting for the one setting that changes something you could write in a single line of CSS.
None of that is the work you got into this for.
One subscriber summed it up in an email to me recently:
“Why not build something that is not fragile in the first place?”
Indeed!
What I did instead
When I came back to my business this autumn, I had to rebuild davefoy.com, and I asked myself a question I hadn’t asked in years:
Does this site actually need all that machinery? A twenty-year-old CMS, a database, hosting requirements, plugin updates, security scares?
For a site like mine, the answer was a resounding no.
So I tried something different. Four pieces, basically:
- An AI web developer agent, set up to work the way I work
- A set of design and build conventions, which turned out to matter more than anything else on this list
- Astro, to build the pages, templates and components
- One CMS, picked from several, just for the part of the site I actually edit
No page builder. No plugin updates. No database. For a simple site, there just isn’t much that can break, and the whole thing feels surprisingly calm. 😇
If you want the nerdy details, I’ve written about how I built the site and why I chose Pages CMS for the blog.
Here’s the bit that surprised me most, though. I didn’t use a page builder at all, and I’m not sure I need one anymore. Coming from “the Bricks guy”, I know.
The hardest part wasn’t technical. It was letting go. My friend John Fraskos put it better than I can:
“Without a page builder, you do not sacrifice control. You re-align your workflow around structured context, skills and processes. Then the rest flows naturally. But first, you have to let go.”
Choosing, not switching
And no, I’m not saying WordPress is dead. (I’m as bored of that headline as you are.)
For big content sites, membership sites and ecommerce, it can still be exactly the right fit.
Before page builders came along, I’d build the site and then pick whatever CMS suited the project. Sometimes that meant no CMS at all. I think we can work that way again.
Over to you
If this goes ahead, I’d keep it small. Things like:
- Creating and working with an AI developer while you stay in charge of the decisions
- The best-practice conventions that keep a site consistent and easy to change later
- Choosing the right CMS for each project, or none at all, depending on who needs to edit what
- Handing over a site your client can edit, that doesn’t need propping up
That’s my guess, anyway. Which is exactly why I’m asking.
Whether you’re fed up and ready for a change, or doing perfectly well and just curious, I’d love to know what you build, what bugs you, and what you’d want from something like this.
I’ll read every reply, and if it goes ahead, you’ll hear first.
Thanks for reading.
Dave
P.S. The form’s just below. Put your name down if you’d like to hear first, and tell me what you’d want from this. That’s the bit that’ll shape it.
Interested? Put your name down and help me shape it
If this goes ahead, you’ll hear first. Your name and email are all I need for that.
The questions are optional, but they’re the most useful part. What you tell me will decide whether I run this and what it covers. Even a line or two helps.
Thank you.
That’s landed with me, and I’ll read it properly. There’s a quick note from me on its way to your inbox.