Security Intro
Update order: core, then plugins, then theme
Updating everything at once is quick, but when it breaks you cannot tell what did it. An order with checks in between is not slower — it keeps…
Technote
WordPress guides for Site operators
For the people who keep the site running: update procedures, backups, incident response and monitoring.
8 articles· Site operators
Servers & infrastructure Intro
Watching only the home page misses outages
Plenty of sites have uptime monitoring and still miss outages. The cause is usually the same: the page being checked never touches the database.
Development workflow Intro
The pre-migration inventory: what you forget lives outside the site
Files and databases are hard to forget. What breaks on cutover day is the thing you registered somewhere else years ago and never looked at again.
Security Intro
Hardening starts by counting your administrators
However many doors you close in configuration, eight people holding keys means eight things to protect. A role audit comes before every other hardening step.
Servers & infrastructure Intro
The first five minutes: scope before cause
Hunting for the cause first costs you time. Establish the scope and the log you need is already decided, with half the candidates gone.
Security Intro
What to back up: code, database and uploads are not alike
Manage it as one lump called "the full backup" and an incident leaves you no options. The three parts change at different rates and restore along different paths.
Themes & plugins Intro
Why updates break — and why it is rarely core
If you are postponing because the last update broke something, it is worth asking what actually broke. Naming the cause correctly changes how you prepare for the next…
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…