Leadership wants to publish news on Friday without a dev ticket. Engineering wants zero PHP in production and a €5 hosting bill. Static or WordPress — the debate pits perf and security against editorial autonomy.
The right question: who publishes, how often, and do you accept a developer in the loop for every change?
Static: ops freedom, editorial constraint
HTML/Markdown files generated at build, served by CDN.
Editors. Autonomous only with Git CMS, headless with preview, or CloudCannon-style platform.
Ops. Small attack surface, CDN scale, low cost.
Friction. Typos = rebuild or pipeline; WYSIWYG preview less natural than WP admin.
WordPress: editorial freedom, maintenance load
Familiar admin, roles, media, SEO plugins.
Editors. Highly autonomous — the main strength.
Ops. Core/plugin updates, security, perf (cache), tested backups.
Friction. Plugin debt, slowness if misconfigured, hungrier hosting.
| Criterion | Static | WordPress |
|---|---|---|
| Editor autonomy | Low to medium* | High |
| Hosting cost | Very low | Low to medium |
| Security surface | Low | Medium to high |
| Time-to-publish | Minutes to hours | Minutes |
*With suitable CMS, medium to high.
Decisive scenarios
Corporate blog, 2 posts/month, marketing alone. Managed WordPress or WP + cache — autonomy wins.
Technical docs, dev authors. Static + Git — ops wins.
10-page site/year, agency maintains. Static or WP depending on who pays future changes.
The peak: editors pay for invisible stack
Decide and move forward without blind spots
- Time a test publish in both workflows.
- Count who maintains updates, plugins, CI build.
- Set hosting + maintenance budget over 3 years.
- Consider WP headless → static if perf critical and editors trained.
WordPress and static hosts: directory, compare.
Frequently asked questions
Static for non-technical users?
With Git CMS/headless yes; otherwise every publish needs dev.
WordPress still relevant?
Yes for autonomous marketing and shared cost — if maintained.
More secure?
Static smaller surface; hardened WP still sensitive if neglected.
WP editing + static prod?
Yes — WP source, deployed static build.
Editor freedom is counted in publishes without dev tickets — pick the stack that truly grants it, not the one that shines in technical meetings.