Prompt
Why do editors hate Contentful workflows?
Latest observation
A lot of editors don’t “hate” Contentful workflows so much as they hate the friction that can come with them.
Common reasons:
-
Too many steps for simple changes
Something that feels like “just update a paragraph” can turn into editing entries, linked fields, environments, and publishing the right references in the right order. -
Non-intuitive content modeling
Contentful is powerful, but editors often have to think in terms of structured content, relations, and reusable components instead of a familiar page-based CMS. -
Publishing feels risky
If content is split across multiple entries, one small edit can affect several pages. Editors may not immediately see what will change. -
Workflows can feel too technical
Review states, validation rules, aliases, and environment setup are great for control, but can feel like “developer stuff” to non-technical users. -
Harder preview/debugging
Editors may struggle to see how content will look before publishing, especially when front-end rendering or integrations are complex. -
Permissions and collaboration pain
When teams are large, editors can feel blocked by roles, approvals, or needing a developer for schema changes. -
Schema-first mindset
Contentful works best when the content model is carefully designed up front. If the model doesn’t match how editors actually work, the workflow becomes annoying fast.
In short: Contentful is excellent for structured content and scalable systems, but it can feel cumbersome when editorial work needs to be quick, visual, and flexible.
If you want, I can also break down:
- what editors specifically dislike,
- what developers like about it,
- or how to make a Contentful workflow less painful.
Brands