설명
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 11 blocks.
- core/archives
- core/rss
- core/legacy-widget
- core/categories
- core/block
- core/latest-comments
- core/search
- core/shortcode
- core/calendar
- core/tag-cloud
- core/latest-posts
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
후기
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.
변경이력
Features
- Add the option to select the style that is automatically applied.
- Add the option to resize Cover Block .
- Allow directly setting a solid background color on Cover block.
- Add list start, reversed settings.
- Add a help panel to the inserter available in all blocks.
- Typewriter experience.
- Add circle-crop variation to Image block.
Enhancements
- Add overflow support inside block switcher.
- Update GitHub action exit codes.
- Core Data: return updated record in saveEntityRecord.
- Latest Posts Block: (no title) instead of (Untitled) for a post without a title.
- Remove borders around inserter items for blocks with children blocks.
- Add disabled block count in the block manager.
- Writing Flow:
Experiments
- Widgets Screen:
New APIs
- Add callbacks to ServerSideRenderer to handle failures with custom renderers.
- Add the block example API and use it for inserter and switcher previews.
- Enable an optional namespace parameter for hasAction & hasFilter .
Bug Fixes
- The duplicate button appears even if the block is not allowed.
- Double scrollbar appearing in full-screen mode.
- RichText: ignore selection changes during composition
- Missing default functions as props in BlockEditorProvider.
- Button block does not center on the editor.
- Guard block component against zombie state bug.
- Add truthy check for the Popover component onClose prop before calling it.
- Make InnerBlocks only force the template on directly set lockings.
- Check to ensure focus has intentionally left the wrapped component in withFocusOutside HOC.
- Correctly transform images with external sources into a gallery.
- Block toolbar appears above sidebar on medium viewports.
- Basecontrol name undefined triggring eslint-plugin TypeError.
- Image flickering & focus lose on resizing.
- Add get_item_schema function to WP_REST_Widget_Areas_Controller .
- Empty Classic Editor inside innerBlock fatal error.
- Changing month in post publish date closes the popover.
Various
- Update re-resizable dependency
- Use mixins in button styles instead of media queries.
- Fix performance tests with the introduction of the navigation mode
- RichText code improvements: #16905, #16962.
- Scripts:
- Improve the way test files are discovered.
- Improve recommended settings included in the package.
- Use the SCSS shared stylelint-config-wordpress config.
- Ignore the WordPress directory in stylelint.
- Fix: edit post sets some default block appender styles.
- Build: remove global install of latest npm.
- Project automation:
- Rewrite actions using JavaScript.
- Fix: Add first-time contributor label.
- Fix: Add milestone.
- Remove unused CSS from ColorPalette component.
Documentation
- Add examples for the lockPostSaving and unlockPostSavingactions.
- Add guidance for adding/proposing/suggesting new components to the wordpress/components npm package.
- Add section about updating package after new releases.
- Add ESNext examples to format API tutorial.
- Document server-side functions that allow registering block styles.


