Build your own theme instead of buying one
A purchased theme or a page builder is now the expensive option.
Not filmed yet
The lesson is written out below. The video comes after.
Buying a theme used to be obviously correct. You were not buying design, you were buying the thousand hours of work you could not do yourself. That calculation has changed.
What you get with a purchased theme is somebody else’s assumptions, a settings panel that covers eighty percent of what you want, and a permanent fight with the last twenty. What you get when you build is exactly what you asked for and nothing you did not.
The migration is not a rip-and-replace, which is the part that scares people off. Start a child theme, rebuild one template, and that template wins. The parent keeps running everything else. Repeat until the parent is doing nothing, then flip the switch and notice that nothing broke β because nothing changed on that final day except which file was in charge.
This site is the proof, incidentally. It is a custom theme, no framework and no builder, built entirely this way.
The one thing to keep
A child theme lets the parent do less and less until it does nothing.
More in WordPress + Claude Code
Next to this one
The wp_options bomb
The table WordPress loads in full on every page view, quietly stuffed with megabytes of junk from plugins you deleted years ago.
WordPress + Claude CodeThe four ways to give AI access to your WordPress site
Application passwords, SFTP, SSH with WP-CLI, and Git. What each one unlocks, and how to revoke any of them.