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/block
- Gutenberg
- core/social-link-
- Gutenberg
- core/latest-posts
- Gutenberg
- core/shortcode
- Gutenberg
- core/legacy-widget
- Gutenberg
- core/tag-cloud
- Gutenberg
- core/categories
- Gutenberg
- core/navigation-menu
- Gutenberg
- core/latest-comments
- Gutenberg
- core/calendar
- Gutenberg
- core/archives
- Gutenberg
- core/search
- Gutenberg
- core/rss
- Gutenberg
FAQ
- Hoe kan ek terugvoering gee of help met ‘n fout?
-
Ons sal graag van jou wil hoor van enige foute, funksie voorstelle en enige ander terugvoering! Gaan asseblief na die GitHub
kwessies bladsy om te soek vir huidig kwessies of laat weet ons van ‘n nuwe een. Terwyl ons probeer om probleme wat hier deur die Plugin geraporteer word op te los, sal jy vinniger reaksie (en die moeite van duplisering te verminder) deur alles in die GitHub-bewaarplek te sentraliseer. - Hoe kan ek bydra?
-
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 gradient backgrounds support to the Button block.
Bug Fixes
- i18n : Include the plural version of the “remove block” string.
- Update dropdown menu items to match hover style in other places.
- Smoothly reposition Popovers on scroll.
- Fix margin styles for Gallery and Social links blocks.
- Fix popovers hidden on mobile.
- Ensure sidebar plugins do not get auto-closed when opened on small screens.
- Fix the design of the Checkbox component in IE11.
- Add has-text-color classname to heading block.
- Prevent figure margin reset CSS from being included in the frontend.
- Fix the scaling of the pinned plugins menu icons.
- Fix Heading and paragraph colors not applied inside the cover block.
- Close Nux tips when clicking outside the tip.
- Fix meta attribute source for post types other than post.
- Fix ”Open in New Tab” not being persisted.
- Fix redo behavior and expand test coverage.
- I18n: Fix missing translation for the “All content copied” string.
- Fix the block preview padding in themes with custom backgrounds.
- Fix merging list blocks with indented list items.
- Fix inline image controls display condition.
- Fix clicking the redirect element focuses the inserted paragraph.
- Fix editing meta attributes with multiple set to true.
- Add No Preview Available text to the inserter preview panel.
- Prevent block controls from disappearing when switching the List block type.
- Avoid trailing space at the end of a translatable string.
- Fix left aligned nested blocks.
- Fix the top margin of the RadioControl help text.
- Fix invalid HTML used in the Featured Image panel.
- Make sure that all edits after saving are considered persistent by default.
- Ensure that sidebar is closed on the first visit on small screens.
- Update the columns block example to avoid overlapping issues.
- Remove unnecessary default styles for H2 heading inside Cover blocks.
- Fix Media & Text block alignment in IE11.
- Remove unnecessary padding in the Columns block.
- Fix the Columns block height in IE11.
- Correctly update RichText value after undo.
- Prevent the snackbar link components from hiding on focus.
- Fix block toolbar position in IE11.
- Retry uploading images on failures.
Performance
- Avoid continuously reset browser selection (improve typing performance in iOS).
Enhancements
- Polish FontSize Picker design.
- Use body color for the post publish panel.
- Limit the width and height of the pinnable plugins icons.
- Add a max width to the Search block input.
Experiments
- Menu Navigation block:
- Implement initial state containing top level pages.
- Fix menu alignment.
- Fix the classname in frontend.
- Block Directory
- Change the relative time string.
- Widgets Screen
- Fix the styling of the inspector panel.
Documentation
- Fix @wordpress/data-controls examples.
- Typos and tweaks: 1, 2.
Various
- Introduce the @wordpress/env package, A zero-config, self-contained local WordPress environment for development and testing.
- Add Storybook to develop and showcase UI components:
- Add ButtonGroup component.
- Add ScrollLock component.
- Add Animate component.
- Add Icon and IconButton components.
- Add ClipboardButton component.
- Add ColorIndicator component.
- Remove RichText wrapper and use Popover for the inline toolbar.
- Improve the way the lock file handles local dependencies.
- Refactor ColorPalette by extracting its design.
- Improve E2E test reliability by consuming synchronous data and bailing on save failure.
- Replace the isDismissable prop with isDismissible in the Modal component.
- Add eslint-plugin-jest to the default @wordpress/scripts linting config.
- Update @wordpress/scripts to use the latest version of webpack for build and start commands.
- Cleanup Dashicon component.
- Update the Excerpt help link.
- Release tool: fix wrong package.json used when bumping the stable released version.
- Fix several typos in code and files.
- Update E2E tests to accommodate WP 5.3 Beta 3 changes.
- Define the “sideEffects” property for @wordpress packages.
- Add nested embed e2e test.
- I18N: Always return the translation file prefixed with
gutenberg-. - Use wp.org CDN for images used in block preview.


