WordPress 5.0 replaces the TinyMCE editor that's been the content editing interface since 2005 with a new block-based system called Gutenberg. Here's an honest breakdown of what changes, what stays the same, and what you should do.
Since WordPress 2.0 in 2005, the standard content editor has been based on TinyMCE — a rich text editor that works similarly to a word processor. You type in a text area, use a toolbar to format text, and insert images by clicking an "Add Media" button. It's familiar, it works, and it's been the interface for hundreds of millions of posts and pages.
Gutenberg replaces this with a fundamentally different model. Instead of one continuous text area, content is composed of discrete "blocks" — a paragraph is a block, a heading is a block, an image is a block, a button is a block. You add blocks, reorder them, and configure each one individually.
The stated goals of the Gutenberg project were to make publishing more intuitive for non-technical users and to provide the foundation for broader changes to how WordPress sites are built — extending blocks beyond just content editing to page layout and eventually site-wide design. The long-term vision is significant; the immediate result is a new editor that takes adjustment.
There's also a competitive context. Page builders like Elementor, Beaver Builder, and Divi had become extremely popular by giving non-developers visual layout control. Gutenberg is partly WordPress's response to that ecosystem growing up around the limitations of the classic editor.
Existing posts and pages don't change. When you open old content in the new editor, it appears as a single "Classic Block" — essentially the old editor interface embedded inside Gutenberg. Your content is not altered; it just opens in a compatibility mode.
New content written in Gutenberg stores block markup comments in the post content. If you ever switch back to the classic editor, this markup is visible as HTML comments but doesn't affect the rendered output.
This is where existing sites need attention. Plugins that add custom fields, meta boxes, or custom editor integrations may behave differently in Gutenberg. Most major plugin authors have been working on Gutenberg compatibility, but less actively maintained plugins may have issues.
Themes that rely heavily on the Classic Editor's styling may look different with Gutenberg's block markup. Block-specific styling isn't automatically handled by themes built before Gutenberg.
WordPress released the Classic Editor plugin simultaneously with WordPress 5.0. It restores the TinyMCE editor and disables Gutenberg entirely. Automattic has committed to officially supporting it until at least 2022.
For sites where Gutenberg causes compatibility issues, or for users who simply prefer the familiar interface, Classic Editor is a completely legitimate choice. There's no urgency to migrate to Gutenberg immediately.
At DownUnder WP, WordPress core and plugin updates are applied from your dashboard when you're ready. You control the timing — no automatic major version updates without your action.
Australian WordPress hosting from $5/month
Your own containerised environment on Australian NVMe servers. Simple, fast, and genuinely cheap.