New posts
A short note when a post is up: what it covers, why I wrote it, and who it is for. Recent ones cover website basics, the WordPress MCP Adapter, and my AI workflow.
What you get
A few a month. Unsubscribe from any email.
Sign upWordPress newsletter
A WordPress newsletter from a working developer: new posts, what to test before a release, and the checklists I use on real sites. Never daily. Unsubscribe from the link in any email.
Sign up
One field is required: your email. First name is optional. I use it to say hello at the top of a note, nothing else. The form sends to Hostinger Reach, the service that delivers the notes.
Your address goes to Hostinger Reach and nowhere else. Details are in the privacy policy and in Hostinger’s privacy policy.
What you get
Three kinds of note, and never more than a few a month. Each one is short enough to read on a phone, and each one has one thing you can do with it the same day.
A short note when a post is up: what it covers, why I wrote it, and who it is for. Recent ones cover website basics, the WordPress MCP Adapter, and my AI workflow.
What changed in WordPress and what to test before you update a client site. I read the WordPress.org release posts and the dev notes so you can skim the part that affects you.
The lists I run on real projects, free when you are on the list. The handoff checklist comes with the welcome note. The release prep checklist goes out before each major version.
Three to five short paragraphs, one link, and one thing to try this week. A real reply address, because I answer. No tracking pixels that I control, nothing sold, and nothing I would not forward to a shop as-is.
Who it is for
Most WordPress newsletters pick one reader. This one has three, because that is who writes to me. Each note says near the top who it is for, so you can skip the ones that are not.
You own a site and want to understand it. The notes explain what an update changes, what a plugin does, and when to call someone. Plain words, no jargon. Start with Website basics.
You ship client sites and need to know what breaks before the client does. Release notes, test plans, and the checklists I hand to project managers. Overflow work is on the hire page.
You want the code and the reasons. Sage, Blade, Tailwind, the block editor, and the AI tools that help without taking over. The repos are on the code section, and the posts link to them.
How it works
Email, and a first name if you like. The form above takes a few seconds.
If the first email asks you to confirm, press the button. That keeps the list honest and the notes out of Spam.
The welcome note links the handoff checklist and three posts to start with.
Every reply lands in my inbox. Questions become posts more often than you would think.
The best test for a note is simple. Would I forward it to a client with no edits? If not, it waits.
How I decide what goes out
Questions
When I have something worth reading. Most months that is one or two notes. Around a major WordPress release it can be three. It is never daily.
Yes. Every email has an unsubscribe link, and it works on the first click. You land on a page that says so, with a form in case you change your mind later.
No. It stays in Hostinger Reach, the service that sends the notes, and is used only for this list. I do not sell it, rent it, or add it to anything else.
Yes. Every post is in the RSS feed, and new posts also go out on Bluesky and LinkedIn. The links are in the footer.
Reply to any note from the old address and tell me the new one, or unsubscribe the old one and sign up again here. Either way takes a minute.
Sometimes, with your permission and without your name unless you want it there. Reader questions are where half the posts come from.
Already on the list?
Every reply lands in my inbox. If you would rather write first, the contact page is open, and the journal has the long versions of everything the notes mention.