Content Guidelines for people and agents in CMSes

The biggest risk to your company right now isn’t AI. It’s how you coordinate your AI with your people.

You can’t just promise to keep a “human in the loop.” Writing a policy document isn’t enough. This needs to be part of your content factory, part of the machine that runs your business.

If you can ignore it, it isn’t a policy. It’s a suggestion. It’s a wish.

The teams I’ve seen struggle are the ones who put governance rules in a Google Doc that’s never opened again after it’s written.

The good news is that enterprise procurement teams are aware of this. They want a guarantee that policies will be enforceable.

Even on a micro level like for authoring, I thought WordPress VIP was going to have to build the missing guidelines for our big customers. We did a hackathon project at a team meetup in Berlin a few months ago where we worked on a guidelines plugin. But that same week, Content Guidelines was introduced as an experiment in WordPress core — not just for the biggest websites, but for all WordPress sites. It’s a way to define editorial guidelines in code so your content “stays on-brand and consistent” whether it’s worked on by people or agents.

How do you make sure your people and agents follow the same rules?

Let me know on LinkedIn.

Published by Brian Alvey

I build software that makes creative people more powerful.