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.
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
Truly bad
Improvements
Hilariously awful
Disaster
It broke my site
I’m with everyone else – but you can’t give no stars
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
For 5.5.0.
Features
- Add a new Group block.
- Add vertical alignment support to the Media & Text block.
- Add the image fill option to the Media & Text block.
Enhancements
- Improvements to the Image Block flows.
- Automatically add
mailto:
to email addresses when linking. - Add visual handles for side resizers for various blocks.
- Improve the performance of the annotations by avoiding excessive memoization.
- Announce the color accessibility issues to screen readers.
- Add enum block attributes validation to browser block parser.
- Use a consistent grey background in the Shortcode block.
- Improve accessibility of video block select poster image.
- Respect prefers-reduced-motion for fixed backgrounds in Cover block.
- Prevent ArrowLeft key press in multi-line selection from prematurely triggering multi-selection.
Bug Fixes
- Avoid keeping the RichText value in cache indefinitely.
- Fix the post title input borders in the code editor.
- Fix the block restrictions to insert, replace or move blocks.
- Select gallery images on focus.
- Fix removing gallery images on delete/backspace key press.
- Fix small visual regression in the block autocompete popover.
- Fix the data module resolver resolution status.
- Avoid saving metaboxes when previewing changes.
- Fix selecting the separator block.
- Fix displaying the color palette tooltips on hover.
- Fix Firefox/NVDA bug not announcing the toggle settings button.
- Fix arrow navigation in paragraph blocks with backgrounds.
- Fix the columns block click to select.
- Fix post dirtiness after fetching reusable blocks.
- Fix the hover and focus styles for buttons with the isBusy prop.
- Remove the box shadow from the side inserter button.
- Changing the region navigation shortcuts to avoid conflicts.
- Fix space insertion in the Button block in Firefox.
- Prevent the link popover from animating constantly as we type.
- Fix the warning triggered by clearing the height of the spacer block.
- Fix undo behavior after fresh post loading.
Documentation
- Add design documentation to the Modal component.
- Clarify the CSS naming coding guidelines.
- Add InspectorControls usage example.
- Tweaks and typos: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13.
Various
- Bootstrap the design of the new widgets screen (non functional yet).
- Reorganization of the block-library code base:
- Use a babel plugin to load block.json files.
- Introduce block.json metadata for all client side blocks.
- Move the edit functions and the icons to separate files.
- Move the transforms and save functions to separate files.
- Add forwardRef support to the PlainText component.
- Support Button Block Appender in the InnerBlocks component.
- Unset the focal point attributes from the Cover block if not needed.
- Consistently return promises from the data module action calls.
- Remove obsolete CSS currentColor usage.
- Improve the e2e test CLI arguments and docs.
- Improve the e2e test login stability on MacOS.
- Remove is-plain-obj package dependency.
- Remove invalid urls and ids from media test fixtures.
- Remove the deprecated Gutenberg plugin functions slated for 5.4 and 5.5.
- remove or rename undocumented RichText package functions and constants.
- Adjust paragraph block spacing to use standardised variables.
- Allow spaces in file paths for package build process.
- Update pre-commit to check modified files only.
- Improve the performance of the webpack build configuration.
- Update dependencies with known vulnerabilities.
- Fix typo in variable names.
Mobile
- Accessibility improvements to the Button component.
- Enhance the unsupported block type.
- Fix image upload progress not being displayed consistently.
- Support copy/pasting images.
- Add the list block.
- Visual refinements for the native nextpage block.
- Fix importing the column block.
- Remove DOM logic from the list block toolbar.
- Put the caret at the end of the text field after merging blocks.
- Fix caret position after inline paste.