Web Development

WordPress block editor and site editing for a business website

8 min readBy Davinder Kumar Meen

Hands arranging wooden and coloured tiles in a grid beside a laptop

The WordPress block editor (the project still called Gutenberg) builds every page from blocks, and with a block theme the same editor now controls the whole site: header, footer, templates, colours and fonts, through the Site Editor. For a business website this means staff can edit layouts without a developer, which is useful only if the site is set up with a small set of patterns, theme.json rules and locked areas. Set it up well and editing is safe and consistent; leave it open and every page slowly drifts from the brand.

Key takeaways

  • The block editor arrived in WordPress 5.0; full site editing and the first default block theme (Twenty Twenty-Two) arrived in WordPress 5.9 in January 2022.
  • As of October 2026 the current branch is WordPress 7.1 (released 19 August 2026, latest point release 7.1.4 on 28 October 2026). WordPress 7.0 (May 2026) and 7.1 added responsive controls, block-level custom CSS, notes for editorial review and new blocks.
  • A block theme stores its design rules in theme.json; that file is where you limit colours, fonts and spacing to your brand.
  • Patterns (synced and unsynced) and block locking are the tools that keep staff edits on-brand.
  • Classic themes and the Classic Editor plugin still work, but new features land in the block and site editors.

What changed since this post was first written?

This post was first published in 2019, when Gutenberg 7.1 was a plugin release and the news was cryptographically signed updates and the Site Health screen. Those features are now simply part of WordPress: Site Health still lives under Tools, and the sodium_compat library still ships with core. The bigger change since then is that the block editor grew from a post editor into a site editor.

The milestones that matter for a business site:

Release Date What it added for site owners
WordPress 5.0 December 2018 The block editor for posts and pages
WordPress 5.9 January 2022 Full site editing, the Styles interface and the first default block theme
WordPress 6.3 August 2023 Reusable blocks renamed to patterns, with a "synced" option
WordPress 7.0 May 2026 Responsive show or hide controls per device, custom CSS on individual blocks, patterns that can be detached, a redesigned dashboard and a command palette, an AI client and Connectors screen in core
WordPress 7.1 August 2026 Responsive styles per screen size in Global Styles, hover and focus styles for buttons, notes attached to any text with @mentions, Tabs and Playlist blocks, a new media editor with AVIF and HEIC support

Real-time co-editing was planned for 7.0 but was pulled before release and is still being tested in the Gutenberg plugin, so do not plan a workflow around it yet.

What is the difference between the block editor and the Site Editor?

The block editor is where you write a single post or page. The Site Editor is where you edit the parts that every page shares: templates (for example the layout of all blog posts), template parts (header and footer), navigation and global styles. The Site Editor is available only with a block theme.

WordPress's own theme handbook describes block themes as "the modern method of building WordPress themes": their templates are HTML files made of block markup that can be edited in the Site Editor. Classic themes use PHP templates and the older Customizer. Hybrid themes are classic themes that adopt some block features, such as block template parts.

For a business this decision matters more than any single feature:

Theme type Who edits the layout Good fit
Block theme Trained staff, in the Site Editor Marketing sites that change often and want fewer developer tickets
Classic theme Developers, in code Sites with heavy custom logic or an existing classic theme that works
Hybrid Developers, with some block parts for staff A gradual move from classic to blocks

How do you keep staff edits on-brand?

You give editors fewer choices, not more training. WordPress's guide to curating the editor experience lists the tools: block locking, patterns, theme.json, filters and hooks, and switching off editor features you do not need. In practice:

  1. Define the brand in theme.json. Set the colour palette, font families and sizes, and spacing scale there, and switch off custom colours and custom font sizes. Editors then pick from your palette instead of a colour wheel.
  2. Build patterns for the sections you repeat. A hero, a service card row, a testimonial strip, a call to action. A synced pattern updates everywhere it is used, so a phone number or offer changes once. An unsynced pattern is a starting layout that each page can change.
  3. Lock what should not move. A block can be locked from its Options menu (against moving, removal or both), and a theme can lock template areas. Lock the header, footer and legal text; leave the content area open.
  4. Restrict the block list. A business site rarely needs every core block. Hiding the ones you do not use makes the inserter easier and stops one-off layouts.
  5. Use the new review tools. Since 7.1, notes can be attached to a specific piece of text, with @mentions that notify a colleague, which suits a simple draft, review and publish routine.

Does the block editor make a site slower?

Not by itself. Sites usually get slow from page builders layered on top, too many plugins, unoptimised images and heavy third-party scripts. If speed is your concern, start with our WordPress speed and Core Web Vitals guide, which covers the fixes that actually move LCP and INP.

Two 7.x changes are worth knowing for performance and media work: image processing for the new media editor moves into the browser, and AVIF and HEIC uploads are supported from 7.1.

Should you move an existing site to a block theme?

Move when you are already redesigning, or when your staff file regular tickets for small layout changes. Do not move a stable classic site just to be current: WordPress still supports classic themes, and the Classic Editor plugin (more than 8 million active installs) says it will be maintained "as long as is necessary".

A sensible order for a move:

  1. Audit which page layouts you really use and turn each into a template or pattern.
  2. Write theme.json from the brand guide before anyone builds pages.
  3. Rebuild the header, footer and two or three key templates; check them on a phone.
  4. Migrate content in batches and check old shortcodes and page-builder markup, which do not convert cleanly.
  5. Train editors on patterns and the locked areas, not on every block.

Before the switch, check the hosting stack: WordPress recommends PHP 8.3 or newer and MySQL 8.0 or MariaDB 10.11 or newer.

How does this fit with security and updates?

The block editor does not change the basics. Sucuri's 2017 hacked website report found that most infections came through vulnerable extensions such as plugins and themes, not through the CMS core, and that pattern is why plugin hygiene matters. Keep core, themes and plugins updated (auto-updates for plugins and themes have been available per plugin since WordPress 5.5), remove what you do not use, and keep backups you have tested. Our WordPress security guide covers the habits that prevent most problems.

When is WordPress not the right tool?

If your content needs to feed a mobile app, several sites or other channels, or if you want a static site with almost nothing to patch, a headless or static setup can fit better. We compared those routes in Headless, static or WordPress: choosing a CMS in 2026; we moved our own site from WordPress to Astro on AWS in October 2026 for those reasons. For most marketing sites with a non-technical team, a well-configured block theme is still a practical choice. Our WordPress development team and our CMS development services cover both routes.

FAQ

Is Gutenberg the same as the block editor?

Gutenberg is the project name and the plugin where new editor features are tested first. The block editor and Site Editor in WordPress core are the result of that project; features move from the plugin into core releases.

Do I need a block theme to use the block editor?

No. The block editor works for posts and pages with classic themes too. You need a block theme only for the Site Editor, which edits templates, headers, footers and global styles.

What is theme.json?

It is a configuration file in a block theme that sets global settings and styles: colour palette, typography, spacing and which design controls editors can use. It is the main place to enforce a brand.

What is the difference between a synced and an unsynced pattern?

A synced pattern is one shared item: edit it once and every page that uses it updates. An unsynced pattern is a starting layout that is copied into the page and can then be changed on that page only.

Can several people edit the same page at once?

Not in core as of October 2026. Real-time collaboration was removed from WordPress 7.0 before release and is still being tested in the Gutenberg plugin. Notes for review and comments are in core.

Is the Classic Editor going away?

There is no announced end date. The Classic Editor plugin says it will be supported as long as necessary, but new editing features are built for the block editor.

Sources (13 links)
Share this article