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
Loving the new editor
Terrible…
Убогая неудобная параша
Great for beginners and simple to switch!
Tem muito a melhorar
Poco usable
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
Latest
Features
- Add a new RSS block and follow-up improvements: 1, 2.
- Add a new Amazon Kindle embed block.
- Add a new FocalPointPicker component and use it to define the focal point of the Cover block background.
Enhancements
- Optimize the re-rendering performance when inserting/removing blocks.
- Improve the Reusable Blocks UX for contributor users.
- Disable embed previews for the smugmug provider.
- Make the fullscreen mode a desktop-only feature.
- Accessibility: Add speak messages when using the FeatureToggle component.
- Accessibility: Change the inserter search result message from assertive to polite.
- Accessibility: Remove duplicate aria label from menu items.
- Remove the “Show Download Button” toggle help text in the File block.
- Render the block switcher as disabled if not available in a multi-selection.
- Use a back arrow icon to clarify the Fullscreen mode exit button.
- Limit the Gallery block columns count to the images count.
- Automatically set a default block style if missing.
- Hide empty categories from the Categories block in the editor.
- Increase the padding of the gallery captions.
- Add left/right alignments to the latest posts block.
- Improve the columns margins.
- Add a help text for the hide teaser toggle in the More block.
- Improve the wording of the embed block messages.
Bug Fixes
- Accessibility: Fix the tab order of the date picker component.
- Support non hierarchical taxonomies in the category selector component.
- Fix blocks marked invalid incorrectly due to special HTML characters.
- Fix the Notice component styling.
- Fix the :root selector in the editor styles.
- Fix duplicate block toolbars.
- Fix warning message when using the DateTimePicker component.
- Fix the File block and Categories block style when applying custom classnames.
- Fix the Gallery block styling in Microsoft Edge.
- Fix the Button block styling when links are visited.
- Fix Block Style preview not dismissed after selection.
- Fix TabPanel buttons incorrectly submitting forms.
- Fix hierarchical dropdown in the Categories block.
- Fix wording for the color picker saturation.
- Fix the save keyboard shortcut while in the code editor mode.
- Fix the Google Docs table pasting.
- Fix jumps when indenting/outdenting list items.
- Fix FontSizePicker max width on mobile.
- Fix PHP 5.2.2 Parser issue.
- Fix plural messages POT generation.
Various
- Add ESnext build setup and commands to the @wordpress/scripts package.
- Add “focus on mount” config to the DropDown component.
- Improve the error handling in the data module resulting in clearer messages displayed in the console.
- Support marking days as invalid in the DatePicker component.
- Support block transforms with inner blocks.
- Improve the styles of the editor notices with actions.
- Replace Polldaddy embed block with Crowdsignal.
- Avoid setting the generic Edit Post Title on load.
- Deprecate window._wpLoadGutenbergEditor.
- Avoid an empty classname when deleting custom classnames.
- Add className prop support to the ServerSideRender component.
Documentation
- Improve the components README files DropdownMenu & RangeControl.
- Add code example of the MediaPlaceholder component.
- Add a accessibility dedicated page.
- Add a Git workflow documentation page.
- Reorganize the contributors guide.
- Mention the dark theme support in the design docs.
- Enhance the compose package documentation.
- Expand the block templates code examples.
- Fix unregisterBlockType code examples.
- Clarify the block styles isDefault property.
- Move the npm packages management documentation to a dedicated page.
- Add a section explaining the links usage in the documentation.
- Add a note about the wp-editor dependency when using RichText.
- Update the isShallowEqual package documentation and tests.
- Refresh the repository management doc.
- Typos: 1, 2, 3, 4, 5, 6, 7.
Chore
- Remove PHP Code maintained in Core and bump minimum WordPress version:
- Block registration.
- REST API Endpoints.
- Markdown support fix.
- Gutenberg body classname and responsive classname.
- Preloading API calls.
- Block detection utilities.
- List screen integration.
- Block content version.
- Block categories hook.
- TinyMCE scripts registration.
- Reusable blocks post type labels and listing page.
- Block Types Initialization.
- PHP Unit tests.
- Compatibility script.
- Meta boxes support.
- Polyfills.
- oEmbed Proxy Endpoint filter.
- Visual Editing Disabling.
- Update browserlist dependency.
- New E2E tests: Date floating for pending posts.
- New ESlint rules:
- Enforce ES6 object shorthand syntax.
- Declare variables only when used.
- Use ES5 eslint config for the is-shallow-equal package.
- Mark the eslint config as a root config.
- Remove the feedback form from the plugin.
- I18n:
- Use a placeholder for the WordPress minimum version.
- Use Sentence case in toolbar tooltips.
- Add the FontAwesome licenses to the GPL 2 compatible licenses.
- Move the generated spec parser to the corresponding package.
- Refactor the nonce apiFetch middleware.
- Refactor the list block indent/outdent buttons.
- Fix watching file changes on Linux.
- Update the question issue template in GitHub to redirect help requests.
- Fix wp-settings permissions in the local development environment.
- Use a filter to populate the demo content.
Mobile
- Improve the hide keyboard button.
- Add the PostTitle component support.
- Support Enter key press in the post title.
- Support native Media Upload.
- Support undo/redo in the post title.
- Make the InspectorControls available for mobile blocks.
- Add failed media upload support and cancel buttons.
- Introduce the BottomSheet component.