Blog
Forms, deliverability, accessibility, operations: plain English, useful before you know what to ask for.
New articles by email
One confirmation email first. Nothing sends until you click it. Or subscribe via RSS.
Check your inbox. A confirmation is on its way. Nothing else sends until you click it.
Nothing matches. Clear the search or pick another topic.
The media library is not a private folder, in WordPress or anywhere else. What that means for the drafts and packets that get uploaded to grab a link, why switching the API off is the wrong fix, and how to mark a file private without breaking anything.
The series finale: where a submission actually goes. The record before the notification, the email path that rots silently, the confirmation with substance, and the monitoring that notices the week your form goes quiet.
CAPTCHAs tax the humans and barely slow the professionals. The quiet alternative: a honeypot, a clock, a rate limit, and a content check that flags instead of blocking, all on the server where the visitor never sees any of it.
Every native form control is painted by two hands: your stylesheet and the visitor's browser. On a dark background the browser's half keeps painting for a light page. The invisible dropdown arrow, the blinding calendar, the autofill flood, and the one line of CSS that fixes most of it.
RSS is the web's oldest, quietest subscription mechanism: no account, no algorithm, no inbox. What it is, how to pick a reader, and how to follow any site that offers a feed, this one included.
Fingertips are not cursors. Target sizes, tappable labels, and the field settings that decide which keyboard appears: the mobile details that quietly determine whether your form gets finished.
A form's error messages are the only conversation it ever has. What a useful error says, where it belongs on the page, when it should speak up, and who has to be able to perceive it.
In-page submission done honestly: the four states a submit button owes the visitor, why typed work must survive every failure, and how to make success audible as well as visible.
If it keeps coming up for your team, it's probably worth writing about. New pieces go out by email (one confirmation first, one-click unsubscribe on every send) or over RSS if you'd rather use your own reader. Either way, nothing in your inbox we didn't earn.
Got it, thank you. If it's a problem we can write about usefully, it'll turn up here.