Why it shows up in your week
Marketing asks for a new section on the pricing page. In a healthy Gutenberg setup they open the editor, insert a pattern, swap copy, and publish. Clear patterns let marketing complete that work directly. Developers handle changes that require code.
In plain language
Each block has its own settings (alignment, colours within theme rules, spacing). Patterns group blocks into reusable sections such as hero, logo row, pricing, or FAQ.
Synced patterns update in one place and reflect everywhere they are used. That is how you keep legal footers or CTA bands consistent without hunting twenty pages.
Gutenberg is both the editing UI and the block API developers use to register custom blocks that match your design system.
Classic Editor is a plugin that restores the old experience. Many legacy sites still depend on it. Migrating content to blocks is a project, not a toggle.
If your theme never exposed patterns, editors will invent one-off layouts. The editor is only as disciplined as the theme and training around it.
Facts worth keeping
- Shipped in core
- WordPress 5.0, December 2018
- Replaced
- Classic content field as the default editing model
- Building units
- Blocks, patterns, template parts (with block themes)
- Not included
- Elementor, Divi, WPBakery (separate commercial plugins)
- Editor location
- Posts, pages, and (with block themes) Site Editor templates
Not the same as
- Elementor / Divi / WPBakerySeparate page builder plugins with their own UI and storage. They are not Gutenberg. Running both without a migration plan creates double systems.
- The Site EditorSite Editor edits global templates and theme parts on block themes. Gutenberg in a page edits that page's content. Related, not identical.
- ACF field groups aloneAdvanced Custom Fields can power structured content. Blocks can wrap ACF. Fields without a clear editor UX still leave marketers stuck.
Where it bites
Gutenberg hurts when the theme still assumes the classic editor, or when two editing systems share the same templates without a migration plan.
Editors then invent one-off layouts that break on update, and every campaign becomes a developer ticket again.
What to check
- Are key templates built from blocks and patterns the brand actually uses?
- Is a third-party page builder still required for routine landing pages?
- Do custom blocks have documentation and a fallback if a plugin is disabled?
- Can editors change a CTA band once and see it update everywhere it is synced?
- Did anyone train editors on patterns, or only on "click the plus button"?
Common questions
What is Gutenberg in WordPress?
Gutenberg is the block-based editor and framework in WordPress since 5.0. Content and layouts are assembled from blocks instead of one classic editor field.
Is Gutenberg the same as a page builder?
No. Gutenberg is core WordPress. Page builders such as Elementor are separate plugins with their own data model and lock-in profile.
Should we remove our page builder?
Often yes for new B2B builds, if the design system is expressed as blocks and patterns. Migration cost is real. Plan it; do not flip a switch on a live campaign site.
What are block patterns?
Prebuilt groups of blocks for common sections. They speed editing and keep spacing and hierarchy on-brand when the theme ships a good library.
What should you check first for Gutenberg?
Patterns that match real pages, no conflicting page builder for routine work, and custom blocks that editors understand without a developer sitting next to them.