Recently, Search Engine Journal reported on a conflict inside WordPress that spilled out into public view. At the center of it: documentation.
That may not sound like headline news, but if you work in WordPress every day like I do, you know documentation isn’t just notes on the side. It’s the backbone of how we build, maintain, and scale websites. When docs fail, adoption slows, contributors burn out, and trust in the platform takes a hit.
What Happened
WordPress leadership rolled out a new Core Program Team to improve coordination across the project. In theory, it’s a smart move. But almost immediately, long-time documentation contributors raised alarms:
- Decisions were made without their input.
- Transparency felt thin.
- Boundaries between leadership and contributor roles weren’t clear.
The fallout was quick. Jenni McKinnon, a respected documentation contributor, announced she was stepping aside, citing burnout and governance concerns.
This isn’t just one person’s frustration. It’s a symptom of a larger problem: how WordPress views documentation, accountability, and community health.
Why It Matters
For developers, site owners, and businesses relying on WordPress, these internal conflicts don’t stay internal for long. They ripple out.
- Docs aren’t optional. Without them, bugs pile up, plugin conflicts drag on, and developers waste hours reinventing the wheel.
- Burnout is real. When contributors feel excluded, they walk away — and with them goes experience we can’t easily replace.
- Trust drives adoption. If the WordPress ecosystem looks disorganized or dismissive, small businesses and agencies start questioning whether the platform can keep up.
Where We Go From Here
Coverage of the conflict is important — but reporting alone won’t solve it. WordPress needs to commit to some hard changes:
- Define roles clearly. Contributors need to know who makes what decisions, and how.
- Bring documentation to the table. Treat docs as a core component, not an afterthought.
- Protect contributors from burnout. Build in rotation, backups, and real support.
- Make governance transparent. If issues are raised, the process for addressing them should be visible to the community.
Final Thought
WordPress isn’t just software — it’s people. If we keep sidelining documentation and ignoring governance cracks, we risk undermining the very stability that made WordPress the backbone of the web.
The takeaway is simple: treat documentation and governance as central, not optional. Without that shift, these conflicts will keep repeating—and each time, the platform’s foundation gets a little weaker.