The Gutenberg team has a proposal out for a problem I have been living with for over a decade: editorial drift. Hand a finished site to a client and two weeks later the brand voice is gone, buried under inconsistent formatting and some very creative image choices. The WordPress Content Guidelines experiment is an attempt to bake those rules into the core editing experience instead of leaving them to willpower.
The end of the “hidden PDF” era
Content standards have always lived somewhere nobody looks: a PDF in a shared drive, or a private wiki that gets opened once. Authors guess at the tone, and developers end up writing custom validation or block filters to enforce whatever they can catch. This experiment gives voice, tone and structural rules a real home in the WordPress admin.
I wrote earlier about why this experiment is huge for long-term site stability. The settings page is the least interesting part of it. What matters is that it defines a kind of site-level configuration with no clear legacy equivalent in WordPress, and that future AI features will have something concrete to follow rather than a vibe.
Why your AI needs content guidelines
AI drafts read like every other blog post on the internet because the model has no idea where it is writing. Point it at a stored set of guidelines and it can pull the site’s own standards, including preferred terminology, accessibility requirements and structural constraints, then produce something that sounds like the site instead of the training set.
The storage side is where this gets interesting for developers. The schema is meant to be machine-readable, so any tool, human-driven or agentic, can query it reliably. That moves your WordPress AI workflows off ad-hoc prompting and onto something shared and portable, which is the only way an agent writes on behalf of a brand without a person checking every comma.
What is in PR #75164
The first implementation is already moving in PR #75164, tracked alongside issue #75171. The current scope is capturing and retrieving guidelines with a basic revision history. Roughly, the shape an agent would read looks like this:
{
"voice_tone": "Professional yet approachable, avoid jargon.",
"formatting": {
"headings": "Sentence case",
"links": "Always open in new tab for external"
},
"accessibility": {
"images": "Must include descriptive alt text reflecting the narrative context"
}
}Generation is only half of it. The same data can be enforced: a Gutenberg Filter that reads the guidelines before publish and flags a post that skipped a required structural rule, in the editor rather than three days later in review.
If this kind of setup is eating your dev hours, I can take it on. I have been building on WordPress since the 4.x days.
Worth getting involved early
It is still an experiment, which is the useful part. The team is asking for feedback on schemas, fields and the workflows around drafting, translation and review. If you have ever watched a project go sideways because the content went off the rails, that war story is worth posting to the discussion. Whatever gets decided now is how brand identity ends up being managed once humans and AI are both writing in the same editor.
