Deskripsi
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/archives
- Gutenberg
- core/rss
- Gutenberg
- core/legacy-widget
- Gutenberg
- core/social-link-
- Gutenberg
- core/categories
- Gutenberg
- core/block
- Gutenberg
- core/latest-comments
- Gutenberg
- core/search
- Gutenberg
- core/shortcode
- Gutenberg
- core/calendar
- Gutenberg
- core/tag-cloud
- Gutenberg
- core/navigation-menu
- Gutenberg
- core/latest-posts
- Gutenberg
PSD (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
Tinjauan
Kontributor & Pengembang
“Gutenberg” adalah perangkat lunak sumber terbuka. Berikut ini mereka yang sudah berkontribusi pada plugin ini.
Para Kontributor“Gutenberg” telah diterjemahkan kedalam 44 lokale. Terima kasih kepada para penerjemah untuk kontribusi-nya.
Terjemahkan “Gutenberg” dalam bahasa Anda.
Tertarik mengembangkan?
Lihat kode, periksa repositori SVN , atau mendaftar ke log pengembangan melalui RSS.
Log Perubahan
Enhancements
- Turn Stack on mobile toggle on by default in the Media & Text block.
- Only show the Inserter help panel in the topbar inserter.
- Use minimum height instead of height for Cover height control label.
- Update the buttons styling to match core.
- Add preview examples for multiple core blocks.
New APIs
- Implement EntityProvider and use it to refactor the meta block attributes.
Experimental
- Introduce the wp_template custom post type to preempt the block content areas work.
- Use the entities store for the widgets screen.
Bugs
- Fix javascript error potentially triggered when using saveEntityRecord action.
- Avoid marking the post as dirty when forcing an undo level (RichText).
- Fix Post Publish Panel overlapping the user profile dropdown menu.
- Fix and align collapsing logic for Save Draft and Saved button states.
- Remove Reusable block name and description from the inserter help panel.
- Fix spacing issues in the inserter panel previews.
- Gallery block: Don’t show the caption gradient overlay unless image is selected or a caption is set.
- Gallery block: Fix custom alignment layouts
- Fix dirtiness detection when server-side saving filters are used.
- Remove wrong i18n domain.
- Fix invalid block warning panel.
- Fix various issues in related to the BlockDirectory inserter.
- Cover block: Show Height control only if an image background is selected.
- Fix RichText composition input issues.
- Fix block placeholders spacing after Core inputs updates.
- Fix checkbox design (color and background) after Core updates.
- Fix radio buttons design after Core updates.
- Remove any existing subscriptions before adding a new save metaboxes sub to prevent multiple saves.
- Clear auto-draft titles on save if not changed explicitly.
- Fix block error boundary.
- Fix select elements design in the sidebar after Core updates.
- Allow using space with modifier keys at the beginning of list items.
- Fix the inputs height after Core updates.
- fix conflict between remote and local autosaves.
Performance
- Request the Image block’s metadata only if the block is selected.
- Improve the performance of the block reordering animation in Safari.
- Remove Autocomplete component wrappers.
Various
- Replace registered social links blocks if already registered in Core.
- More stable List block e2e tests.
- Add e2e tests to validate the date picker UI behavior.
- Add e2e tests to validate the local auto-save behavior.
- Mark the social links block as experimental.
- Update the e2e tests to accommodate the new theme.
- Align the version of lodash with WordPress core.
- Add phpcs rule to detect unused variables.
- Simplify Block Selection Reducer.
- Add has-background classes to pullquote and Media & Text blocks for consistency.
- Tidy up button vertical align styles.
- Update browserslist dependency.
Documentation
- Add scripts/styles dependency management documentation.
- Update docs with the example property used for Inserter previews.
- Typos and tweaks: 1, 2, 3, 4, 5.
Mobile
- Add rounded corners on media placeholder and unsupported blocks.
- Fix link editing when the cursor is at the beginning of a link.