Description
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:
- The block unifies multiple interfaces. If we add that on top of the existing interface, it would add complexity, as opposed to remove it.
- 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.
- 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.
- Considering the whole interface lays a solid foundation for the next focus, full site customization.
- 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
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.
Compatibility
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.
Contributors
Gutenberg is built by many contributors and volunteers. Please see the full list in CONTRIBUTORS.md.
Blocks
This plugin provides 13 blocks.
- core/latest-posts
- Gutenberg
- core/shortcode
- Gutenberg
- core/rss
- Gutenberg
- core/categories
- Gutenberg
- core/legacy-widget
- Gutenberg
- core/search
- Gutenberg
- core/latest-comments
- Gutenberg
- core/social-link-
- Gutenberg
- core/calendar
- Gutenberg
- core/block
- Gutenberg
- core/navigation-menu
- Gutenberg
- core/tag-cloud
- Gutenberg
- core/archives
- Gutenberg
FAQ
- 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 CONTRIBUTING.md.
- Where can I read more about Gutenberg?
-
- Gutenberg, or the Ship of Theseus, with examples of what Gutenberg might do in the future
- Editor Technical Overview
- Design Principles and block design best practices
- WP Post Grammar Parser
- Development updates on make.wordpress.org
- Documentation: Creating Blocks, Reference, and Guidelines
- Additional frequently asked questions
Reviews
Contributors & Developers
“Gutenberg” is open source software. The following people have contributed to this plugin.
Contributors“Gutenberg” has been translated into 44 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.
Changelog
Features
- Add a new Social links block.
- Support border radius changes in the Button block.
- Support adding a caption to the Gallery block.
- Support local autosaves.
Enhancements
- Disable the click-through behavior in desktop.
- Update the labels width to fit their content.
- Avoid displaying console warnings when blocks are upgraded using deprecated versions.
- Reduce the padding around the in-between block inserter.
- Improve the design of the block movers.
- Align the Gallery block image controls with the block movers design.
- Remove child blocks from the block manager.
- Remove duplicated “Enable” label from the options panel.
- Use sentence case for all tooltips.
- Remove the forced gray scale from the category icons.
- Move the alignment controls to toolbar of the Heading block.
- Use the featured image frame in the Media modal.
Bug Fixes
- Update the Post Schedule label to correctly reflect the date and time display settings.
- Clean up the block toolbar position for wide full blocks.
- Fix the cropped focus indicator in the block inserter.
- Browser incompatibilities:
- Fallback to setTimeout in RichText if no requestIdleCallback is not supported.
- Block toolbar fixes for IE11.
- Fix Backspace usage in RichText for IE11.
- Prevent clicking the next/previous month in the Post Schedule popover from closing it.
- Prevent the private posts from triggering the unsaved changes warnings after saving.
- Fix the usage of the useReducedMotion hook in Node.js context.
- A11y:
- Use darker form field borders.
- Fix the modal escape key propagation.
- Move focus back from the Modal to the More Menu when it was used to open the Modal.
- Trim leading and trailing whitespaces when inserting links.
- Prevent using the paragraph block when pasting unformatted text into RichText.
- Fix styling of classic block’s block controls.
- Fix the showing/hiding logic of the Group menu item in the block settings menu.
- Fix invalid HTML nesting of buttons.
- Fix React warning when using withFocusReturn Higher-order component.
- Fix lengthy content cuts in the Cover block.
- Disable multi-selection when resizing.
- Fix the permalink UI in RTL languages.
- Fix multiple issues related to the reusable blocks editing/previewing UI.
- Remove filter that unsets auto-draft titles.
- Fix the Move to trash button redirection.
- Prevent undo/redo history cleaning on autosaves.
- Add i18n support for title Content Blocks string.
- Add missing extra classnames to the Column block.
- Fix JavaScript error triggered when using a multi-line RichText.
- Fix RichText focus related issues.
- Fix undo levels inconsistencies.
- Fix multiple post meta fields edits.
- Fix selecting custom colors in RTL languages.
Experiments
- Add one-click search and install blocks from the block directory to the inserter.
- Refactor the Navigation block to be a dynamic block.
- Add a block navigator to the Navigation block.
- Only show the customizer block based widgets if the experimental widget screen is enabled.
APIs
- Add a disableDropZone prop for MediaPlaceholder component.
- Add post autosave locking.
- PluginPrePublishPanel and PluginPostPublishPanel support icon prop and inherits from registerPlugin.
- Allow disabling the Post Status settings panel.
- Restore the keepPlaceholderOnFocus RichText prop.
Various
- Upgrade React and React DOM to 16.9.0.
- Add TypeScript JSDoc linting to the @wordpress/url package.
- Run npm audit to fix the reported vulnerabilities.
- Switch the local environment to an environment based on the Core setup.
- Set a constant namespace for module sourcemaps.
- Refactor the loading animation to rely on the Animate component.
- Code improvements to block PHP files.
- Enable the duplicate style property linting rule.
- Update Husky & Lint-staged to the latest versions.
- Restore the usage of the latest npm version in CI.
- Add ESLint as peer dependency to eslint-plugin.
- Conditionally include the block styles functionality to avoid conflicts with Core.
- Add missing deprecated setFocusedElement prop to the RichText component.
- Support generating assets in PHP format in the webpack dependency extraction plugin.
Documentation
- Update the reviews and merging documentation.
- Fix type docs for the Notices package.
- Add a link to the fixtures tests document in the Testing Overview.
- Adds documentation for the onClose prop of MediaUpload.
- Tweaks and typos: 1, 2, 3, 4, 5, 6, 7, 8.


