Development workflow Practical
Review on staging, not in screenshots
A screenshot is one moment under ideal conditions. States, edge cases and real content only surface on staging — and staging has conditions of its own.
Technote
Development workflow
Git, .gitignore, CI/CD, WP-CLI and staging — treating a WordPress site like code rather than like a live server you edit.
73 articles· Development workflow
Development workflow Practical
Your own endpoint: namespace, permission callback, schema
permission_callback is not optional. Omit it and the route is public, with a core warning to match. An args schema then keeps validation out of your handler entirely.
Development workflow Practical
Safe search-replace: serialisation, guid and dry runs
Replace a domain with raw SQL and widget and theme settings quietly go blank. Serialised data stores string lengths — and switching tools removes the problem entirely.
Development workflow Practical
Priority wars: whoever speaks last wins
Priority is a queue position, not authority. Raising your number is a move the other side can also make, and jumping behind a translation filter sends the untranslated…
Development workflow Practical
Undrawn states are where the build diverges from the design
A composition that shows only the happy path defines half the screen. The other half — empty, error, overlong title — gets improvised during the build, and the…
Development workflow Intro
Exposing a post type and its meta with show_in_rest
A post type opens with one line. Meta does not: it needs a registered type, an auth_callback governs writing, and reading opens regardless.
Development workflow Intro
Posts and terms from the command line: list before you change
Bulk-edit accidents almost always come from selecting the wrong set. Split selection and action into two commands and you get to see what will change before it changes.
Development workflow Intro
Hook timing: before init, the world is not there yet
The same code on the same hook behaves differently depending on when it runs. Taxonomies, post types and translations all see an incomplete world before init.
Development workflow Intro
What to commit in a WordPress repository, and what to ignore
One rule decides it: did we write this? Credentials and generated content are not source, and once they are in the repository the problem is no longer reversible.
Development workflow Intro
Getting design and code to use one set of names
Different names mean a translation step in every conversation. That translation lives only in people's heads, and it never reaches whoever joins next.
Development workflow Intro
The REST API you already have
You are already using it even if you never go headless — this is how the block editor saves your posts. Knowing the response shape halves your client…
Development workflow Practical
A .gitignore for WordPress on GitHub
The line between what belongs in a WordPress repository and what must never enter it is sharp. The moment wp-config.php lands in a repo, your database password and…