“Gutenberg” is a codename for a whole new paradigm in WordPress site building and publishing, that aims to revolutionize the entire publishing experience as much as Gutenberg did the printed word. Right now, the project is in the first phase of a four-phase process that will touch every piece of WordPress — Editing, Customization, Collaboration, and Multilingual — and is focused on a new editing experience, the block editor.
The block editor introduces a modular approach to pages and posts: each piece of content in the editor, from a paragraph to an image gallery to a headline, is its own block. And just like physical blocks, WordPress blocks can added, arranged, and rearranged, allowing WordPress users to create media-rich pages in a visually intuitive way — and without work-arounds like shortcodes or custom HTML.
The block editor first became available in December 2018, and we’re still hard at work refining the experience, creating more and better blocks, and laying the groundwork for the next three phases of work. The Gutenberg plugin gives you the latest version of the block editor so you can join us in testing bleeding-edge features, start playing with blocks, and maybe get inspired to build your own.
Discover More
-
User Documentation: See the WordPress Editor documentation for detailed docs on using the editor as an author creating posts and pages.
-
Developer Documentation: Extending and customizing is at the heart of the WordPress platform, see the Developer Documentation for extensive tutorials, documentation, and API reference on how to extend the editor.
-
Contributors: Gutenberg is an open-source project and welcomes all contributors from code to design, from documentation to triage. See the Contributor’s Handbook for all the details on how you can help.
The development hub for the Gutenberg project is on Github at: https://github.com/wordpress/gutenberg
Discussion for the project is on Make Blog and the #core-editor channel in Slack, signup information.
這個外掛提供 4 個可供 Gutenberg/區塊編輯器使用的區塊。
- core/social-link-
- Gutenberg
- core/navigation
- Gutenberg
- core/post-comments
- Gutenberg
- core/search
- Gutenberg
- 如何針對程式碼錯誤進行意見反應或取得協助？
-
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.
- What’s Next for the Project?
-
The four phases of the project are Editing, Customization, Collaboration, and Multilingual. You can hear more about the project and phases from Matt in his State of the Word talks for 2019 and 2018. Additionally you can follow updates in the Make WordPress Core blog.
- Where Can I Read More About Gutenberg?
-
Out of the box with no built-in fallback (classic as a plugin doesn't count), this monstrosity turned re-wording an identical section of text on dozens of posts and pages created with other editors into a several hours long nightmare of restorations as other authors and contributors were also accidentally deleting a random amount of existing content with every save and update action. Had I known what the cause was earlier I would have restored a full site backup, but as it was I was just getting reports from end users of missing or broken posts and repairing them as they came in. It didn't click until I started to get reports of things I previously restored being broken again (like after an author recreated his changes and saved again) and finally when the items I had changed were also coming in. Eventually, I had to disable all non-admin accounts to stop the bleeding and restore posts.
I finally tried merely opening and saving an existing item which resulted in random deletions of content from the item. Yes random. I copied the existing body in classic to the clpbrd, opened then saved without making changes. Everything past a random line would just vanish from the post. I then opened the post again in classic, pasted it back, saved, and again opened and saved in Gutenberg. Everything below a different line was deleted, and so on... 1 star is 2 stars too many to give this mangled mass of pain.
They should leave the old functionality as an option (even if not the default). Gutenberg and "blocks" are a shit-show. Dumbing things down for the least common denominator and removing features IS NOT AN UPGRADE.
In reality we would probably give it 4 stars because it still needs some work, but the number of 1-star reviews is ridiculous so we're adding an extra star. Gutenberg has made our blogging experience so much better! The re-usable blocks alone are enough to warrant our loving this update. Looking forward to seeing the technology continue to grow and improve.
No começo me pareceu imprestável, mas depois que aprendi a usar acredito seja muito melhor que os concorrentes no modo gratuito, não usei no modo pago para comparar, mas se fosse usar algum seria esse devido ao fato de já saber usá-lo.
The new Gutenberg editor is potentially very good, let down by a bad user interface/experience (UX) for beginners: which is all of us, when we see it for the first time. For the experienced user, the interface is OK.
Someone who is new Gutenberg MUST have cues and help. There are few of these. Help is hidden in the ⋮ menu, several clicks away. The page is a blank canvass, with no similarity to a document (like the classic editor). Some icons are meaningless, and hovering your cursor over them shows no tooltip.
In my opinion, the editor needs the following:
On-screen help and cues (that can be disabled when the beginning is comfortable), eg. contained in the sidebar, that can be disabled later
The "page" area to have a different colour to the background (eg. white on grey), ideally corresponding to the selected them
To return to the Admin menu, there should be a "X" and not a W icon which hints at viewing pages.
Or better yet, the Gutenberg editor should follow the layout of the familiar Appearance/Customise editor, and let us edit in-place.
The Gutenberg was maybe a great idea but awful execution. Too many bugs one way or another (build in editor in WP has one set of bugs, editor from Gutenberg plugin has another set, and both are impossible to work in comfortably). What is worth now even if I disable Gutenberg I still have troubles becuase some content was created in it and, for example, FooGallery is not visible in visual mode of editor if a page was created in Gutenberg (you can see code for gallery in html mode, but not gallery itself in visual mode).
閱讀全部 3,083 則使用者評論
以下人員參與了開源軟體〈Gutenberg〉的開發相關工作。
參與者
To read the changelog for Gutenberg 8.0.0, please navigate to the release page.
