The WordPress Block Editor: A Publisher's Deep Dive
The WordPress block editor — introduced in 2018 as the Gutenberg project and now simply the default editing experience — has matured into a genuinely capable publishing tool. It was controversial at launch and the criticism was fair: it was slow, unstable, and a poor replacement for the Classic Editor many publishers had built workflows around. Several years and dozens of releases later, it is a different product.
For publishers either still avoiding it or using it without fully understanding its capabilities, this is a practical walkthrough of what it can actually do.
The Core Concept
Everything in the block editor is a block — a discrete content element that can be independently configured, moved, and styled. Paragraphs, headings, images, quotes, lists, tables, video embeds, code snippets, buttons, columns, separators — each is its own block with its own settings.
This is a meaningful shift from the Classic Editor’s single rich text field. Content is structured rather than monolithic, which creates both opportunities (reordering sections by dragging blocks, applying different styling to different elements) and constraints (content is stored as block markup rather than plain HTML, which can complicate migrations).
Navigating the Interface
The block editor toolbar runs across the top of the screen. The main editing area is the document canvas. A sidebar panel on the right switches between Document settings (status, visibility, publish date, featured image, categories, tags, excerpt) and Block settings (specific to whichever block is selected).
Open the block inserter with the + button in the top-left or by clicking the + that appears between blocks when you hover. Type a slash / anywhere in the canvas to open an inline block search — /image, /heading, /quote — which is faster than the inserter for keyboard-oriented editors.
Blocks Publishers Use Most
Paragraph — the default block for body text. Nothing special but note the Typography settings in the sidebar allow per-block font size, line height, and letter spacing adjustments.
Heading — configurable H2 through H6 with anchor ID generation for deep linking.
Image — upload, select from media library, or enter a URL. Supports alt text, captions, links, and alignment options. The Duotone filter in the block toolbar applies color effects without editing the source image.
Gallery — displays multiple images in a grid. Column count and image cropping are configurable in the sidebar.
Quote and Pullquote — Quote is a standard blockquote; Pullquote is a styled feature quote intended for visual emphasis mid-article.
Table — creates HTML tables without touching markup. Supports header and footer rows, fixed-width layouts, and a striped style.
Columns — splits content into a two-, three-, or four-column layout. Each column is its own block container that can hold any other blocks. Useful for side-by-side comparisons, author bios, and feature callouts.
Group and Row — Group wraps multiple blocks into a container with shared background color, border, and padding settings. Row arranges blocks horizontally in a flex container. These are the primary layout tools for structured content design.
Cover — an image or video block with overlaid text. Common for article heroes and section headers.
Embed — handles YouTube, Vimeo, Twitter/X, Instagram, Spotify, SoundCloud, and dozens of other embeds through a single URL input. Paste the URL and the editor resolves it to the correct embed format.
Custom HTML — drops raw HTML directly into the content. Useful for embed codes that the Embed block does not handle, custom widgets, and legacy content.
Shortcode — executes a WordPress shortcode within the content. Bridges the gap with plugin functionality not yet block-native.
Reusable Blocks and Patterns
Reusable blocks are blocks or block groups saved and shared across posts. Create a standard author bio block, a newsletter signup call-to-action, or a standard disclaimer once, save it as reusable, and insert it anywhere. Edit the reusable block once and the change propagates to all instances.
Access reusable blocks through the block inserter under the star icon, or search for them by name.
Block patterns are pre-composed arrangements of blocks — a hero layout, a three-column feature grid, a quote with image — that you insert as a starting template and then customize. WordPress ships with a pattern library; themes add their own; the Pattern Directory at wordpress.org provides community-contributed options.
The Document Settings Sidebar
Publishers spend as much time in the Document sidebar as in the canvas itself. Key settings:
Status and Visibility — Public, Private, or Password Protected. Schedule publication with the Publish date field.
Revisions — click to browse all saved versions of the post with a diff view. Restore any previous version. The block editor saves frequently during editing.
Featured Image — set the post’s featured image, which themes typically display in archive listings and at the top of single posts.
Excerpt — the custom excerpt field. If empty, WordPress generates an automatic excerpt from the post content. Write a custom excerpt for archive pages and social sharing where you want controlled summary text.
Discussion — toggle comments and pingbacks per post.
Keyboard Shortcuts
The block editor has a full keyboard shortcut set that significantly speeds up editing for regular users.
Ctrl/Cmd + K— add a linkCtrl/Cmd + Shift + K— remove a link/— open inline block searchCtrl/Cmd + Z/Ctrl/Cmd + Shift + Z— undo / redoCtrl/Cmd + S— save draftCtrl/Cmd + Shift + ,— open editor settingsEscape— clear block selection- Arrow keys — navigate between blocks when a block is selected but not being edited
Full Site Editing
WordPress has extended the block editor beyond post content to the entire site through Full Site Editing (FSE). With a block-based theme (Twenty Twenty-Four and Twenty Twenty-Five are the default block themes), the Site Editor under Appearance → Editor allows editing headers, footers, sidebars, archive templates, and single post templates using the same block interface.
FSE is powerful but represents a significant change to the WordPress theming model. Publishers with heavily customized classic themes should evaluate FSE carefully before migrating — the two theme architectures are not compatible without a rebuild.
When Classic Editor Is Still Justified
The Classic Editor plugin remains available and WordPress has committed to supporting it through at least 2024, with the community likely maintaining it beyond that. Publishers with valid reasons to stay on Classic Editor — legacy plugin dependencies, editorial team retraining cost, complex TinyMCE customizations — can do so without significant operational risk for the near term.
For new sites and for publishers willing to invest in the transition, the block editor in its current state is a capable tool that rewards learning its patterns.