When the block editor arrived in WordPress core it changed how most people write for the web, whether they wanted the change or not. The old editor was a single text box with a toolbar above it, much like a word processor. The block editor replaces that box with a canvas made of blocks: a paragraph is a block, so is a heading, an image, a gallery, a button, a column layout or an embedded video. You assemble a page from those pieces and rearrange them by dragging.
The result sits somewhere between a text editor and a page builder. It is not as elaborate as a full drag-and-drop builder plugin, but it is built into WordPress, it needs no extra software, and it produces markup that stays readable. This article explains what Gutenberg is, how it works day to day, which blocks are worth learning first, and where it still frustrates people.
What the Block Editor Actually Is
Gutenberg is the name of the project that produced the editor now shipped with WordPress. Every piece of content is stored as a block with its own settings, and each block exposes its own controls in a sidebar: alignment, colour, typography, spacing, and whatever else that particular block supports. The same idea has since been extended beyond posts and pages to headers, footers and templates, so that the parts of a site that used to require theme files can be edited in the same interface.
That is the important shift. Under the old editor, layout lived in the theme and content lived in the database, and changing a layout meant editing PHP. Under the block model, structure and content are edited in the same place by the same person. If the vocabulary here is unfamiliar, the WordPress glossary is a useful companion, and our guide to the WordPress CMS covers the underlying platform.
How Gutenberg Works Day to Day
Open a new post and you are given an empty paragraph. Press the plus button, or type a forward slash followed by a block name, and the inserter appears. Choose a block, fill it in, and add the next one. Blocks can be dragged into a new order, grouped together, nested inside columns, and saved as reusable patterns you drop into future pages.
Two habits make the editor far more pleasant. The first is learning the slash command, which is much faster than hunting through the inserter panel. The second is using the list view, a collapsible outline of every block on the page — on a long article it is the only sane way to select a block buried three levels deep inside a group.
Setting It Up
There is nothing to install. The block editor has been part of WordPress core since version 5.0, so any current installation already has it. If you have just built a site — perhaps by following our guide to installing WordPress on VPS hosting — open any page and start adding blocks. Sites that still rely on old shortcode-heavy content can keep the classic editing experience through a plugin, but that is a compatibility measure rather than a long-term plan.
The Blocks Worth Learning First
The library is large and most of it you will never touch. A small set covers the overwhelming majority of real pages.
Text blocks
- Paragraph — the default block, with alignment, colour and typography controls.
- Heading — sets the document outline, so choose levels for structure rather than for size.
- List — ordered and unordered lists, with nesting.
- Quote and pull quote — one for cited passages, one for pulling a line out visually.
- Code and preformatted — for snippets that must keep their spacing.
- Table — simple tabular data without touching HTML.
Media blocks
- Image — with alternative text, sizing, alignment and link controls.
- Gallery — a grid of images with column settings.
- Cover — an image or video background with content layered on top.
- Media and text — the classic two-column image-beside-copy arrangement.
- Audio, video and file — embedded players and download links.
Design and layout blocks
- Columns — the workhorse for anything wider than a single text column.
- Group, row and stack — containers that let you apply background, spacing and alignment to several blocks at once.
- Buttons — styled links with their own colour and radius settings.
- Spacer and separator — vertical rhythm without empty paragraphs.
- More — controls where an excerpt is cut on archive pages.
Alternative text on the image block deserves particular attention. It is what screen readers announce and what search engines read, and writing it well is one of the cheapest accessibility improvements available — the Web Content Accessibility Guidelines explain why.
Where Gutenberg Still Frustrates People
The editor arrived to a divided reception and some of the objections have aged well. Older themes and plugins that assumed the classic editor can behave oddly, and a site heavy with shortcodes may need real work before it feels native. The interface hides settings in several places at once — a block toolbar, a settings sidebar and a styles panel — which takes time to internalise. And complex layouts require patient nesting of groups and columns, where a dedicated builder would offer a single control.
Set against that: no extra plugin, no proprietary shortcodes wrapped around your content, and markup that survives a change of theme. That last point matters more than it sounds. Content built in a third-party builder is often tied to that builder for as long as the site exists. If you are weighing the choice, our comparison of Elementor and Gutenberg goes through it case by case, and the wider page builder roundup covers the rest of the field.
Conclusion
The block editor is now simply how WordPress works, so the practical question is not whether to adopt it but how far to lean on it. For blogs, brochure sites and most small-business pages it is more than capable on its own, and it keeps your content portable. For heavily designed marketing pages a dedicated builder still saves time. Learn the dozen blocks above, get comfortable with list view and reusable patterns, and the editor stops feeling like an obstacle. More tutorials are collected in our blog archive.