Printing since 1440. Development hub for the editor focus in core. Plugin is available from the official WordPress repository.
Switch branches/tags
@wordpress/wordcount@2.0.3 @wordpress/wordcount@2.0.2 @wordpress/wordcount@2.0.1 @wordpress/wordcount@2.0.0 @wordpress/wordcount@1.1.3 @wordpress/wordcount@1.1.2 @wordpress/wordcount@1.1.1 @wordpress/wordcount@1.1.0 @wordpress/viewport@2.0.10 @wordpress/viewport@2.0.9 @wordpress/viewport@2.0.8 @wordpress/viewport@2.0.7 @wordpress/viewport@2.0.6 @wordpress/viewport@2.0.5 @wordpress/viewport@2.0.4 @wordpress/viewport@2.0.3 @wordpress/viewport@2.0.2 @wordpress/viewport@2.0.1 @wordpress/viewport@2.0.0 @wordpress/viewport@1.0.4 @wordpress/viewport@1.0.3 @wordpress/viewport@1.0.2 @wordpress/viewport@1.0.1 @wordpress/viewport@1.0.0 @wordpress/url@2.3.0 @wordpress/url@2.2.0 @wordpress/url@2.1.0 @wordpress/url@2.0.2 @wordpress/url@2.0.1 @wordpress/url@2.0.0 @wordpress/url@1.2.3 @wordpress/url@1.2.2 @wordpress/url@1.2.1 @wordpress/url@1.2.0 @wordpress/token-list@1.0.2 @wordpress/token-list@1.0.1 @wordpress/token-list@1.0.0 @wordpress/shortcode@2.0.2 @wordpress/shortcode@2.0.1 @wordpress/shortcode@2.0.0 @wordpress/shortcode@1.0.3 @wordpress/shortcode@1.0.2 @wordpress/shortcode@1.0.1 @wordpress/shortcode@1.0.0 @wordpress/shortcode@1.0.0-alpha.3 @wordpress/shortcode@1.0.0-alpha.2 @wordpress/scripts@2.4.3 @wordpress/scripts@2.4.2 @wordpress/scripts@2.4.1 @wordpress/scripts@2.4.0 @wordpress/scripts@2.3.1 @wordpress/scripts@2.3.0 @wordpress/scripts@2.2.1 @wordpress/scripts@2.2.0 @wordpress/scripts@2.1.0 @wordpress/scripts@2.0.3 @wordpress/scripts@2.0.2 @wordpress/scripts@2.0.1 @wordpress/scripts@2.0.0 @wordpress/rich-text@2.0.4 @wordpress/rich-text@2.0.3 @wordpress/rich-text@2.0.2 @wordpress/rich-text@2.0.1 @wordpress/rich-text@2.0.0 @wordpress/rich-text@1.0.2 @wordpress/rich-text@1.0.1 @wordpress/rich-text@1.0.0 @wordpress/rich-text@1.0.0-beta.2 @wordpress/rich-text@1.0.0-beta.1 @wordpress/redux-routine@3.0.3 @wordpress/redux-routine@3.0.2 @wordpress/redux-routine@3.0.1 @wordpress/redux-routine@3.0.0 @wordpress/redux-routine@2.0.0 @wordpress/redux-routine@1.0.0 @wordpress/postcss-themes@1.0.4 @wordpress/postcss-themes@1.0.3 @wordpress/postcss-themes@1.0.2 @wordpress/postcss-themes@1.0.1 @wordpress/postcss-themes@1.0.0 @wordpress/postcss-themes@1.0.0-alpha.3 @wordpress/postcss-themes@1.0.0-alpha.2 @wordpress/postcss-themes@1.0.0-alpha.1 @wordpress/postcss-themes@1.0.0-alpha.0 @wordpress/plugins@2.0.8 @wordpress/plugins@2.0.7 @wordpress/plugins@2.0.6 @wordpress/plugins@2.0.5 @wordpress/plugins@2.0.4 @wordpress/plugins@2.0.3 @wordpress/plugins@2.0.2 @wordpress/plugins@2.0.1 @wordpress/plugins@2.0.0 @wordpress/plugins@1.0.4 @wordpress/plugins@1.0.3 @wordpress/plugins@1.0.2 @wordpress/plugins@1.0.1 @wordpress/plugins@1.0.0 @wordpress/plugins@1.0.0-alpha.3 @wordpress/plugins@1.0.0-alpha.2
Nothing to show
Clone or download
Failed to load latest commit information.
.github Delete (#8986) Aug 20, 2018
assets/stylesheets Try: Improve columns block (#11620) Nov 9, 2018
bin Run the E2E tests as a user with the author role (#11359) Nov 7, 2018
docs Copy guidelines formatting tweaks (#8952) Nov 12, 2018
eslint Framework: Remove deprecations slated for 3.7 removal (#9163) Aug 29, 2018
languages Build: Include string extraction in production build (#5308) Mar 2, 2018
lib Parsing: Use full parser in `do_blocks` with nested block support (#1… Nov 10, 2018
packages Fix autocomplete suggestion list positioning, make it the size of the… Nov 14, 2018
phpunit Parsing: Use full parser in `do_blocks` with nested block support (#1… Nov 10, 2018
test PostPublishPanel: return focus to element that opened the panel (#11543) Nov 9, 2018
vendor Install `phpcs` using Composer (#1022) Jun 6, 2017
.browserslistrc Build: using a postcss plugin to generate the admin-schemes styles (#… May 15, 2018
.editorconfig chore: Update `.editorconfig` to match WordPress' upstream Jan 12, 2018
.eslintignore Remove code coverage setup (#11198) Nov 1, 2018
.eslintrc.js DotTip: Rename `id` attribute to `tipId` (#10317) Oct 27, 2018
.gitignore Remove code coverage setup (#11198) Nov 1, 2018
.jshintignore Add .jshintignore to ignore all since eslint is employed May 25, 2017
.npmrc Framework: Configure NPM to save exact versions Aug 25, 2017
.nvmrc Framework: Bump recommended Node version to active LTS Nov 1, 2017
.stylelintrc.json Add stylelint for SCSS linting (#8647) Aug 8, 2018
.travis.yml Run the E2E tests as a user with the author role (#11359) Nov 7, 2018 Adds in a Code of conduct Oct 7, 2017 Docs: Update link text for manifest (#10804) Oct 24, 2018 Add @Luehrsen to (#11731) Nov 11, 2018 Update copyright year to 2018 in (#4511) Jan 16, 2018 Remove code coverage setup (#11198) Nov 1, 2018 Use HTTPS for Hacker One URL (#4655) Jan 24, 2018 Add tests file. Mar 17, 2017
babel.config.js Framework: Update code to work with Babel 7 (#7832) Jul 11, 2018
composer.json Show lint errors when there are lint problems (#9661) Sep 13, 2018
composer.lock Upgrade WPCS to 1.0.0 (#9065) Aug 18, 2018
docker-compose-localdev.yml Allow access to the WordPress installation if DOCKER_ENV=localwpdev (#… Aug 10, 2018
docker-compose.yml Docker: Add user for cli image. (#7450) Sep 14, 2018
gutenberg.php Fix code style issues, which I embarssingly somehow got by the linter ( Nov 14, 2018
jsconfig.json Remove code coverage setup (#11198) Nov 1, 2018
lerna.json Add changelog files back to the ingored changes by Lerna Nov 9, 2018
package-lock.json Update Plugin Version to 4.3.0 (#11762) Nov 12, 2018
package.json Update Plugin Version to 4.3.0 (#11762) Nov 12, 2018
phpcs.xml.dist Move the HTML block into the blocks library package (#10396)(#10397) Oct 9, 2018
phpunit.xml.dist Setup server side unit tests (#617) May 10, 2017
post-content.php Rename cover image to cover; Add video in cover block; (#10659) Oct 18, 2018
webpack.config.js Make cssnano remove all comments (#11754) Nov 12, 2018


Build Status lerna

Printing since 1440.

Gutenberg editing

This is the development hub for the editor focus in core. Gutenberg is the project name. If you want to use the latest release with your WordPress, download Gutenberg from the plugins repository. Conversations and discussions take place in #core-editor on the core WordPress Slack.

Discover more about the project here.

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).

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, 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 removing 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.

Writing in Gutenberg 1.6


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 meta boxes 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.

Get involved

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. A weekly meeting is held in the Slack channel on Wednesdays at 13:00 UTC.


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

How You Can Contribute

Please see

Further Reading

Code is Poetry.