Gutenberg is more than an editor. While the editor is the focus right now, the project will ultimately impact the entire publishing experience including customization (the next focus area).

Discover more about the project.

Editing focus

The editor will create a new page- and post-building experience that makes writing rich posts effortless, and has “blocks” to make it easy what today might take shortcodes, custom HTML, or “mystery meat” embed discovery. — Matt Mullenweg

One thing that sets WordPress apart from other systems is that it allows you to create as rich a post layout as you can imagine — but only if you know HTML and CSS and build your own custom theme. By thinking of the editor as a tool to let you write rich posts and create beautiful layouts, we can transform WordPress into something users love WordPress, as opposed something they pick it because it’s what everyone else uses.

Gutenberg looks at the editor as more than a content field, revisiting a layout that has been largely unchanged for almost a decade.This allows us to holistically design a modern editing experience and build a foundation for things to come.

Here’s why we’re looking at the whole editing screen, as opposed to just the content field:

  1. The block unifies multiple interfaces. If we add that on top of the existing interface, it would add complexity, as opposed to remove it.
  2. By revisiting the interface, we can modernize the writing, editing, and publishing experience, with usability and simplicity in mind, benefitting both new and casual users.
  3. When singular block interface takes center stage, it demonstrates a clear path forward for developers to create premium blocks, superior to both shortcodes and widgets.
  4. Considering the whole interface lays a solid foundation for the next focus, full site customization.
  5. Looking at the full editor screen also gives us the opportunity to drastically modernize the foundation, and take steps towards a more fluid and JavaScript powered future that fully leverages the WordPress REST API.


Blocks are the unifying evolution of what is now covered, in different ways, by shortcodes, embeds, widgets, post formats, custom post types, theme options, meta-boxes, and other formatting elements. They embrace the breadth of functionality WordPress is capable of, with the clarity of a consistent user experience.

Imagine a custom “employee” block that a client can drag to an About page to automatically display a picture, name, and bio. A whole universe of plugins that all extend WordPress in the same way. Simplified menus and widgets. Users who can instantly understand and use WordPress — and 90% of plugins. This will allow you to easily compose beautiful posts like this example.

Check out the FAQ for answers to the most common questions about the project.


Posts are backwards compatible, and shortcodes will still work. We are continuously exploring how highly-tailored metaboxes can be accommodated, and are looking at solutions ranging from a plugin to disable Gutenberg to automatically detecting whether to load Gutenberg or not. While we want to make sure the new editing experience from writing to publishing is user-friendly, we’re committed to finding a good solution for highly-tailored existing sites.

The stages of Gutenberg

Gutenberg has three planned stages. The first, aimed for inclusion in WordPress 5.0, focuses on the post editing experience and the implementation of blocks. This initial phase focuses on a content-first approach. The use of blocks, as detailed above, allows you to focus on how your content will look without the distraction of other configuration options. This ultimately will help all users present their content in a way that is engaging, direct, and visual.

These foundational elements will pave the way for stages two and three, planned for the next year, to go beyond the post into page templates and ultimately, full site customization.

Gutenberg is a big change, and there will be ways to ensure that existing functionality (like shortcodes and meta-boxes) continue to work while allowing developers the time and paths to transition effectively. Ultimately, it will open new opportunities for plugin and theme developers to better serve users through a more engaging and visual experience that takes advantage of a toolset supported by core.


Gutenberg is built by many contributors and volunteers. Please see the full list in


How can I send feedback or get help with a bug?

We’d love to hear your bug reports, feature suggestions and any other feedback! Please head over to the GitHub issues page to search for existing issues or open a new one. While we’ll try to triage issues reported here on the plugin forum, you’ll get a faster response (and reduce duplication of effort) by keeping everything centralized in the GitHub repository.

How can I contribute?

We’re calling this editor project “Gutenberg” because it’s a big undertaking. We are working on it every day in GitHub, and we’d love your help building it.You’re also welcome to give feedback, the easiest is to join us in our Slack channel, #core-editor.

See also

Where can I read more about Gutenberg?


I cried

Why does this have to be so NOT intuitive! I want to edit an old post and add an image in the middle of the post – can’t do it with Gutenberg. I had to go to the Library and grab the image url and then add the image with code. It’s going to take me HOURS to do anything in this. Not to mention that it is jumpy. Like as I move my mouse around on the screen, it is all jumpy and twitchy. Now my eye is twitchy.

My entire workflow is going to have to change. I write, then I add all the images. Now I have to write one paragraph at a time and add the image between each paragraph? This sounds like it is MORE clunky that before.

I’m sure some things are better but I have not found those traits yet.

Here’s what sucks:
– screen twitches when you move the mouse
– no way to add a photo in the middle of a paragraph (stop making basic stuff hard!)
– if you mouse the cursor too far to the left by accident and click, it takes you to the top of the post. Then you gotta scrollllllll all the way back
– it’s hella narrow … I have a wide screen so I can write a lot and see it all at once. Gutenberg only takes up 1/4 of my screen width so I feel like I can see nothing.
– It adds in span and other crap code when I am in the visual editor then I have to go back into the code editor and remove that stuff so I can put H2 etc. Why?!
– you can’t highlight in visual and then see that highlighted in the code editor – so now I have to cherrypick through 2000 word articles to find links that need to be marked no follow?! ARGHHH!!

Why would you do this?

Hyperlink Option – No Page Dropdown

In the WordPress visual editor, when you highlight some text and click the hyperlink icon (to turn it into a hyperlink), a list of all your pages and stuff used to appear so you could just click on it and that would become the destination URL.

Now, I have to go and get the page url manually, which isn’t ideal as you have to Update the page you are working on, go to Pages/All Pages, then copy the URL you want and go back to the page you were working on.

Surely an easy fix. Tx.

No NO No

Installed, tried and deactivated. Do not go forward with this. Horrible to use.

WordPress editor needs tweaking, not an overhaul

I like the “newish” editor. I do *not* like Gutenberg. I tried to. It was an interesting attempt to look like a few WP themes that use “blocks” for placement of sections like titles, images, videos, and text.

But. When I tried to insert a video or a featured image, the video url kept reverting to text and the featured image wouldn’t take.

Please, WordPress, don’t “fix” what isn’t broken. I understand this need to stay on the cutting edge of blogging, but this Gutenberg idea isn’t for bloggers and website owners. It’s for people on the back end who like messing about while creating themes. Please Start Over.

This is no longer ‘WORD’Press

If the focus of this development is moving to page layout or design, why not just make this a forward thinking no-backward compatibility ‘fork’ of WordPress and call it ‘DESIGN’Press 1.0?

WordPress to me isn’t in any competition with other solutions out there. I became comfortable with building websites thanks to WordPress about ten years ago, otherwise I’d be in a totally different line of business. And I’m not even a full-fledged developer, yet so comfortable.
I gladly and effortlessly dropped other options I used to try out and am not even following up on other solutions… that might change if this becomes a core thingy.
I assure that I will always have it disabled anyways.

I’ve worked in media houses which I championed their migration to WordPress. I now freelance and use nothing but WordPress. My clients are getting the hang of it pretty well.
But with this???

With the size and dominance of WordPress today, it wouldn’t be hard to offer a fork called something like DESIGN-Press targeted specifically to a section of her already existing audience whose focus is on page design.

I wonder if there’s any other plugin with as many passionately negative reviews. I see there are people who hardly make reviews coming out just to express their grievances with this.
Those giving positive reviews can gladly be served with your DESIGNPress or whatever it might’ve been called. IF.
And in that case, I’d even make some sites specifically with DESIGNPress. THEN it would be fun.

This won’t be a nice change for me. Sigh!

Need lots of improvements

I liked the concept, but the editor needs lots of improvements. Adding a link to a text adds the link to all the text in all of the blocks. Selecting text sometimes select all the blocks. There are other problems which should be fixed.

Lasīt 1  017 atsauksmes

Contributors & Developers

“Gutenberg” is open source software. The following people have contributed to this plugin.


“Gutenberg” has been translated into 34 locales. Thank you to the translators for their contributions.

Translate “Gutenberg” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Izmaiņu žurnāls


  • Restore min-width to popover.
  • Fix wide toolbar regression
  • Add e2e test for publishing a page
  • Fix typo for removing excerpt block stripping


  • Fixed an issue that caused page publishing to fail.
  • Fixed an issue with the block options menu appearing too narrow.


  • Updated block inserter and library with new icons for all core blocks.
  • Allow showing the sidebar and inspector controls when editing a block in HTML mode.
  • Add new block keyboard shortcuts and consolidate their display in menus:
    • Insert Before / After block.
    • Duplicating block.
    • Toggling the inspector.
    • Remove block keyboard shortcut.
  • Updated block inserter and library with new icons for all core blocks.
  • Allow showing the sidebar and inspector controls when editing a block in HTML mode.
  • Add new block keyboard shortcuts and consolidate their display in menus:
  • Insert Before / After block.
  • Duplicating block.
  • Toggling the inspector.
  • Remove block keyboard shortcut.
  • Add new keyboard shortcuts help modal documenting available shortcuts.
  • Hide keyboard shortcuts on mobile screens.
  • Open new window if prior preview window has been closed.
  • Bring the preview tab to the front when clicking the preview button.
  • Avoid changing the label of the “publish” button if an auto-save is being performed.
  • Update the Block Inserter to allow searching for terms that contain diacritics.
  • Take into account children blocks when handling disabled blocks.
  • Offer chance to add and revise Tags and Post Format during pre-publish flow.
  • Let menus grow based on the length of its elements.
  • Add visual padding to menus.
  • Avoid scrollbars on Audio block when shown full-width.
  • Improve permalink UI and make it responsive.
  • Change color of links in gallery block caption.
  • Simplify the styling of the “Toggle publish panel” aria-region to avoid content jumps.
  • Make active pill button look pressed.
  • Make sure Latest Posts alignment class behaviour is consistent.
  • Show drop-zone background when file is dragged.
  • Reset active sidebar tab on initial load.
  • Apply new checkbox CSS to radio buttons and fix border radius.
  • Add a couple new dashicons for insert before / after block.
  • Add styles for Spinner component (was relying on core before).
  • Add styles for Notice component.
  • Refactor template select field to use SelectControl.
  • Correctly handle per_page=-1 in the queried data state.
  • Create dummy context components for type switch.
  • Add RegistryConsumer export to data module.
  • Add has_blocks function to the repertoire.
  • Add has_block function and unit tests.
  • Add has_block function and unit tests for it.
  • Introduce strip_dynamic_blocks() for excerpts.
  • Fix issue with default appender placeholder on IE11.
  • Fix issue with shortcode block UI on IE11.
  • Fix tag input interface on IE11.
  • Fix issue with custom element serializer on IE11.
  • Fix issue with meta boxes overlapping the content on IE11.
  • Fix invalidation case of custom block classes.
  • Fix unhandled error dialog styling issue.
  • Fix paragraph splits on react native implementation.
  • Fix code block style regression.
  • Fix issue with code font-size on heading contexts.
  • Fix case where crashed block would overlap with surrounding blocks.
  • Fix issue with block styles on IE11.
  • Fix the heading level buttons on IE11.
  • Fix issues with drag and drop over text.
  • Fix small bug with recent blocks hover style.
  • Use argument swapping instead of named arguments for string placeholders.
  • Pass the the search result object to props.onChange on UrlInput.
  • Add localization context to occurrences of “More” string.
  • Add a Heading block implementation for mobile app.
  • Add the react-native entrypoint to all runtime packages.
  • Move MoreMenu specific styling away from Popover CSS.
  • Ensure meta box functions are available in editor context.
  • Ensure the full content integration test is run.
  • Remove client-side document title updates.
  • Remove TinyMCE shim that was removed in WP 4.9.7.
  • Remove the workaround for intermittent multiple-tab preview test failure.
  • Remove Promise.resolve call that’s already handled by the JS runtime.
  • Remove redundant event handlers from default block appender.
  • Deprecate withContext HOC and remove its usage.
  • Some localization & spelling fixes.
  • Update docs for templateLock’s insert option.
  • Extract Core Blocks to a block-library npm package.
  • Add a license checker script.
  • Allow access to the WordPress installation if DOCKER_ENV=localwpdev.
  • Bring the handbook design up to date.