What Gutenberg Changed in WordPress 5.0
WordPress 5.0 introduced a fundamental shift in how content is created and managed on the platform. The classic TinyMCE editor, which had been the standard for over a decade, was replaced by Gutenberg, a block-based editing system that treats every piece of content as a discrete, configurable component. This change affects how content authors work, how developers structure themes and plugins, and how site managers maintain their WordPress installations going forward.
Understanding the Block-Based Approach
The old classic editor treated a post as a single stream of text. Formatting was applied through a toolbar, with authors selecting text and clicking buttons to bold, italicise, or link content. Anyone who needed more control would edit the HTML directly in a Text tab. This model worked well enough, but it had limitations for complex layouts and made it difficult for non-technical users to create structured content.
Gutenberg replaces this model entirely. Every element on a page is a block. A paragraph is a block. An image is a block. A heading, a pull quote, a list, a button, an embedded video: all blocks. Each block handles its own content and formatting independently, and blocks can be moved, styled, and configured without touching HTML code.
This shift matters for practical reasons. Building a two-column layout no longer requires understanding CSS or writing custom HTML. You insert a Columns block and place other blocks inside each column. The structure is visible directly in the editor, which makes the editing process more intuitive and reduces the likelihood of broken markup.
Finding Your Way Around the Block Editor
When you create a new post or page in WordPress 5.0 or later, the block editor opens by default. You will see a clean editing area where you can start typing immediately. The first block is usually a Paragraph block, which handles body text. Press Enter to start a new paragraph, which creates a new Paragraph block automatically.
To add a new block above or below your current position, click the plus icon that appears between blocks or at the top-left of the editor. This opens the block inserter, which shows all available block types organised by category. Use the search field to find a specific block quickly.
Each block has a toolbar that appears when you click into it. The toolbar provides common formatting options for that block type. You can also access additional settings through the three-dot menu on the right side of the toolbar, or through the block sidebar that appears when you click the Settings icon in the top-right corner.
Moving, Editing, and Removing Blocks
To move a block to a different position, click and hold the six-dot drag handle on the left side of the block. Drag it up or down to the desired position and release. Alternatively, click into the block to show the toolbar, then use the up and down arrow buttons in the toolbar to move the block one position at a time.
Editing block content is usually straightforward: click into the block and type, paste, or select text to apply formatting. The formatting options available depend on the block type. Paragraph blocks offer bold, italic, links, and inline code. Heading blocks let you set the heading level directly from the toolbar.
To remove a block, click into it and either press Backspace or Delete on your keyboard, or open the three-dot menu in the block toolbar and select Remove Block. If you make a mistake, use Ctrl+Z or Cmd+Z to undo. You can undo multiple steps to recover previous content.
The Most Useful Block Types to Know
The Paragraph block is the workhorse of most posts. It handles body text and supports basic formatting like bold, italic, strikethrough, inline code, and links. When you type directly in the editor without inserting a specific block, WordPress creates a Paragraph block automatically.
Heading blocks create proper semantic headings from H2 through H6. Use the toolbar to select the heading level. The first heading in a post is typically H2, which represents the main section heading. Reserve H1 for the post title, which WordPress handles separately from the block content. Maintaining a logical heading hierarchy helps both readers and search engines understand your content structure.
The Image block handles standalone images with a clean interface. You can upload images directly by dragging them from your computer onto the editor, or click the Upload button to select a file. Once inserted, click the image to access alignment options, alt text settings, and size controls. Writing descriptive alt text for every image is important for accessibility and contributes to image search visibility.
The Quote block creates styled blockquotes with a distinctive left border. This is useful for highlighting important statements, testimonials, or referenced content. The Classic block embeds the old TinyMCE editor inside the block editor, which is useful when you need to preserve content from the classic editor or when certain workflows require the old interface.
Reusable Blocks and How They Work
If you have content that appears across multiple posts or pages, such as a disclaimer, an author bio, a contact section, or a standard call-to-action, reusable blocks can save significant time. Select the block or blocks you want to make reusable, click the three-dot menu in the block toolbar, and choose Add to Reusable Blocks. Give the block a descriptive name and it will be saved to your reusable blocks library.
Reusable blocks appear in the block inserter under the Reusable tab. When you insert a reusable block into a post, it acts as a linked copy. Editing the original reusable block updates every instance where it is used across your site. This is powerful for maintaining consistent content, but it requires awareness: changes propagate automatically to all posts using that block.
If you need a reusable block to be different in a specific context, you can convert it back to regular blocks. Open the three-dot menu on the block and select Convert to Blocks. This breaks the link to the reusable master and turns the block into independent content that you can edit separately.
Block Patterns and Pre-Built Layouts
Block Patterns are pre-designed layouts that come with WordPress or are provided by your theme and plugins. They give you a head start on common page structures without needing to build everything from individual blocks. A pattern might include an alternating image-and-text layout, a services section with icons and descriptions, or a team member grid.
To access block patterns, click the plus icon to open the block inserter, then select Browse All. The Patterns tab shows available layouts grouped by category. Click a pattern to insert it into your post. You can then modify any of the blocks within the pattern to suit your specific content.
Block patterns are particularly valuable for non-technical authors who need professionally designed layouts. Rather than assembling columns, images, and text blocks manually, you can start with a pattern and adjust the content. This bridges the gap between what the block editor can do and what most users have time to build by hand.
Creating Multi-Column Layouts
The Columns block provides a straightforward way to create multi-column content directly in the editor. Insert the Columns block, choose a layout option like two columns or three columns, and then add other blocks inside each column. The blocks inside columns behave normally and can be edited, moved, or removed independently.
This approach is far simpler than the old method of using HTML tables or custom CSS. The visual editor shows you exactly how the columns look as you build them, which makes it easier to create balanced, readable layouts. Columns work well for side-by-side comparisons, feature lists, or placing images alongside text descriptions.
Block Alignment and Theme Compatibility
Many blocks support alignment options for Wide Width and Full Width content. These options appear in the block toolbar and allow selected blocks to extend beyond the normal content column. Wide width expands the block slightly beyond the column without reaching the edges of the screen. Full width stretches the block to fill the entire viewport.
These alignment options only work if your current theme supports them. Themes that are built to work with Gutenberg typically include styles for wide and full-width blocks. If your theme does not support these features, the alignment buttons may not appear in the toolbar, or selecting them may have no visible effect. When choosing or updating a theme, check whether it has been tested with the block editor and supports these layout options.
Block Templates and Pre-Defined Structures
For sites that follow consistent content patterns, block templates define a starting layout for new posts or pages. This is primarily a developer feature, but it affects what authors experience when they create new content. Theme and plugin developers can define templates in code that specify which blocks appear automatically and in what order.
A business site might define that every new Service page starts with a Cover block, a Description heading, a Features list, and a Contact section. Authors then fill in their content rather than building the page structure from scratch each time. This is useful for maintaining consistency across large sites where multiple authors contribute content.
If you notice that new posts in your WordPress installation already contain certain blocks when you start editing, that structure is defined by a template in your theme or a plugin. The template controls the starting layout, but you can add, remove, or rearrange blocks once the post is open. Understanding this helps explain why some post types look different from others.
How Gutenberg Affects SEO and Content Structure
When Gutenberg was first released, some site owners worried that the block editor might harm their search rankings. In practice, search engines read HTML content regardless of the tool used to create it. Gutenberg produces clean, semantic HTML output that search engines can crawl and index effectively.
The block editor actually makes it easier to maintain good content structure. Heading blocks are clearly labelled as H2, H3, or other levels, which reduces the risk of accidentally skipping heading levels or using the wrong hierarchy. In the classic editor, it was easy to break heading structure without noticing until you viewed the page in the frontend.
Images inserted through the Image block have prominent alt text fields that encourage proper completion. Better alt text improves accessibility and can contribute to image search visibility. The overall markup from Gutenberg is cleaner than what the classic editor often produced, particularly when content was copied and pasted from word processors.
Working with Content from the Classic Editor
When you open a post that was created in the classic editor, WordPress attempts to convert it to blocks automatically. This conversion is generally reliable, but complex HTML or non-standard formatting can sometimes produce unexpected results. Always preview the converted post before publishing to make sure the content looks correct.
If the conversion produces problems or if you prefer the classic workflow, you can install the Classic Editor plugin. This plugin restores the old editor interface and is maintained for the foreseeable future. It is a practical option for sites where certain plugins have not updated to work properly with the block editor, or where authors have established workflows that the block editor would disrupt.
Shortcodes in the Block Editor
Shortcodes that were inserted directly in the classic editor appear as Shortcode blocks when you open those posts in Gutenberg. The Shortcode block displays the shortcode text in the editor and renders the output when the post is viewed on the frontend.
Many plugins have updated their shortcodes to provide dedicated blocks with visual configuration interfaces. If a plugin offers a block for its functionality, using that block is usually easier than remembering shortcode syntax. The block provides fields and options that guide you through the setup, which reduces errors and makes the configuration more visible to site managers.
Security Considerations When Using the Block Editor
Using the block editor does not change the fundamental security requirements for a WordPress site. Keeping WordPress core, themes, and plugins updated remains essential. User accounts should use strong, unique passwords, and you should review who has access to your WordPress admin area regularly.
Two-factor authentication adds an important layer of protection for admin accounts. If you manage a WordPress site and have not set up two-factor authentication, it is worth reviewing your options. Many security plugins provide this functionality, and it can significantly reduce the risk of unauthorised access even if a password is compromised.
Reusable blocks and block patterns from third-party themes or plugins can contain hidden or unwanted content. Review any blocks or patterns before using them on a live site, particularly if they come from sources you do not fully trust. As with any theme or plugin, it is worth understanding what you are adding to your site.
Getting Comfortable with the Block Editor
The transition from the classic editor to Gutenberg takes some adjustment, but the investment in learning the block editor pays off over time. The interface is consistent across different sites once you understand it, which makes it easier to work with WordPress installations that you manage for clients or your own projects.
Practical tips that help with the transition include: use keyboard shortcuts where they make sense, learn the block inserter search function so you can find blocks quickly, and explore the block settings sidebar for options that are not immediately visible in the toolbar. Autosave runs continuously in the background, so you do not need to save manually as frequently as in the past, though saving drafts before making major changes is still sensible practice.
If you are responsible for a WordPress site that involves multiple authors or regular content updates, taking time to document your block editor workflow can help everyone work more consistently. Good documentation reduces confusion and helps new authors get up to speed faster.