توضیحات
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.
سؤالات متداول را برای پاسخ به رایجترین سؤالاتی که درباره این پروژه مطرح است، بررسی کنید.
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.
سوالات متداول
- چطوری می توانم نظر یا گزارش خرابی بدم؟
-
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.
- چطور می توانم مشارکت کنم؟
-
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
- اصول طراحی و بهترین شیوه طراحی بلاکها
- WP Post Grammar Parser
- Development updates on make.wordpress.org
- مستندات: ایجاد بلاکها، مرجع و دستورالعملها
- سوالات متداول اضافی
بررسیها
Half Baked
One of the best developments for WordPress (german)
Please Staaph! If It Ain’t Broken…
Not too excited about it
Terrible
A waste of time.
توسعه دهندگان و همکاران
“گوتنبرگ” نرم افزار متن باز است. افراد زیر در این افزونه مشارکت کردهاند.
مشارکت کنندگان“گوتنبرگ” has been translated into 44 locales. Thank you to the translators for their contributions.
علاقه مند به توسعه هستید؟
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
تغییرات
For 5.3.0.
Features
- Add the block management modal: Ability to hide/show blocks in the inserter.
- Support nested blocks for the Cover Block.
- Add an experimental Legacy Widget Block (enabled only in the plugin for the moment).
Enhancements
- Update the block outlines for the hover and selected states.
- Allow undoing automatic pattern block transformations.
- Add a RichText collapsed format toolbar for code, inline image and strikethrough formats.
- Allow collapsing inserter panels when searching.
- Add ability to transform video shortcodes to video blocks.
- Add ability to transform audio shortcodes to audio blocks.
- Add new @wordpress/data actions to invalidate the resolvers cache.
- Support custom classNames in the ToggleControl component.
- Clarify the button to exit the post lock modal.
- Improve the block validation error message.
- Automatically use the WordPress babel config when using @wordpress/scripts CLI.
- Add keyboard shortcuts to indent/outdent list items.
- Use links instead of buttons in the document outline.
- Use
<s>
for strikethrough, not<del>
. - Center the tooltips content.
- Update wording of the block switcher tooltip.
- Add support for the reduced motion browser mode.
Bug Fixes
- Always show the current month in the Calendar block for All CPTs but post.
- In the Latest posts block, avoid full line clickable titles.
- Avoid relying on DOM nodes to add the empty line in RichText component. This fixes a number of lingering empty lines.
- Fix the MediaPlaceholder icon color on dark backgrounds.
- Fix the Classic block toolbar in RTL languages.
- Fix the more tag in the Classic block.
- Fix the quote to heading block transformation.
- Fix “null” appearing when merging empty headings and paragraphs.
- Fix the block insertion restrictions in the global inserter.
- Fix the prepareEditableTree custom RichText Format API.
- Changes to the internal RichText format representation to separate objects (inline image..) from formats (bold…). This fixes a number of RichText issues.
- Fix the Spinner component styling in RTL languages.
- Fix focus loss when using the Set Featured Image buttons.
- Fix template lock not being taken into consideration.
- Fix composed characters at the beginning of RichText.
- Fix several block multi-selection bugs.
- Allow using a float number as a step when using the RangeControl component.
- Fix error when pasting a caption shortcode without an image tag.
- Fix focus loss when combining sidebars and modals (or popovers).
- Escape the greater than character when serializing the blocks content into HTML.
- Fix pasting links into the classic block.
- Include missing CSS in the classic block.
Documentation
- Enhance the i18n process documentation with a complete example.
- Add design guidelines to several components:
- The Button component
- The CheckboxControl component
- The MenuItemsChoice component.
- The MenuGroup component.
- Update the JavaScript setup tutorial to rely on the @wordpress/scripts package.
- Lowercase block editor and classic editor terms to conform to the copy guidelines.
- Use a central script to generate the JavaScript API documentation and run in parallel.
- Update the packages release process.
- Update the plugin release docs to rely on a lighter SVN checkout.
- Add automatic generation of JavaScript API documentation for:
- @wordpress/element
- @wordpress/escape-html
- @wordpress/html-entities
- @wordpress/keycodes
- @wordpress/a11y
- @wordpress/blob
- @wordpress/block-library
- @wordpress/compose
- @wordpress/dom
- @wordpress/i18n
- @wordpress/autop
- @wordpress/dom-ready
- @wordpress/block-editor
- @wordpress/rich-text
- @wordpress/blocks
- @wordpress/deprecated
- @wordpress/priority-queue
- @wordpress/shortcode
- @wordpress/viewport
- @wordpress/url
- @wordpress/redux-routine
- @wordpress/date
- @wordpress/block-serialization-default-parser
- @wordpress/plugins
- @wordpress/wordcount
- @wordpress/edit-post
- Link to the editor user documentation and remove the user documentation markdown file.
- Typos and tweaks: 1, 2, 3, 4, 5.
Various
- Upgrade to React 16.8.4 (React Hooks).
- Fix the dependencies of the e2e-tests and the e2e-test-utils npm packages.
- Avoid disabling regeneratorRuntime in the babel config to avoid globals in npm packages.
- Work on various e2e tests stability improvements.
- Regenerate RSS/Search block test fixtures.
- Move to travis.com as a CI server.
- Add clickBlockToolbarButton e2e test utility.
- Add e2e tests:
- to check the keyboard navigation through blocks.
- to verify that the default block is selected after removing all the blocks.
- to check the InnerBlocks allowed blocks restrictions.
- Add unit tests for the isKeyboardEvent utility.
- Remove CC-BY-3.0 from the GPLv2 compatible licenses.
- Polish the @wordpress/block-editor module:
- Move the block specific components to the package.
- Update the classnames to follow the CSS guidelines.
- Update eslint rules npm packages.
- Simplify the hierarchical term selector strings.
- Update the Latest comments block to use the “align support config” instead of a custom implementation.
- Remove the block snapshots tests.
- Remove post install scripts and only run these in CI to improve test performance.
- Tweak the plugin build zip script to avoid prompting when the build environment is clean.
- Add withRegistry higher-order component to the @wordpress/data module.
- Add missing module entry point to the notices package.json.
- Remove the Gutenberg 5.3 deprecated functions.
- Ensure sourcemaps published to npm contain safe relative paths.
- Remove the replace_block filter usage and extend core editor settings instead.
- Improve handling of transpiled packages in unit tests.
- Add CLI arguments to launch e2e tests in interactive mode more easily.
- Select a unique radio input in a group when using the tabbables utility.