“Gutenberg” is a codename for a whole new paradigm for creating with WordPress, that aims to revolutionize the entire publishing experience as much as Gutenberg did the printed word. The project is following a four-phase process that will touch major pieces of WordPress — Editing, Customization, Collaboration, and Multilingual.
區塊編輯器為網站的全部組件導入模組化方法:在編輯器中的每一「塊」內容,從段落、圖片庫到標題,都是個別區塊。就像實體區塊一樣,WordPress 的區塊可以進行新增、排列及重新排列,讓 WordPress 使用者得以透過直觀的方式,建立圖文並茂的內容,而不需要採用短代碼或自訂 HTML 程式碼等因應措施。
The block editor first became available in December 2018. We’re always hard at work refining the experience, creating more and better blocks, and laying the groundwork for the future phases of work. Each WordPress release comes ready to go with the stable features from multiple versions of the Gutenberg plugin, so you don’t need to use the plugin to benefit from the work being done here. However, if you’re more adventurous and tech-savvy, the Gutenberg plugin gives you the latest and greatest, so you can join us in testing bleeding-edge features, start playing with blocks, and maybe get inspired to build your own.
進一步了解
-
使用者線上說明文件:請參閱〈WordPress 編輯器〉線上文件,以便進一步了解作者如何使用編輯器建立文章、頁面及各種內容的詳細指示。
-
Developer Documentation: Explore the Developer Documentation for extensive tutorials, documentation, and API references on how to extend the editor.
-
參與者:Gutenberg 是開放原始碼專案,並且歡迎全部開發者、設計師、技術文件作者及編審人員參與。請參閱〈Contributor Guide〉以進一步了解能參與哪個部分的詳細資料。
The development hub for the Gutenberg project can be found at https://github.com/wordpress/gutenberg. Discussions for the project are on the Make Core Blog and in the #core-editor channel in Slack, including weekly meetings. If you don’t have a slack account, you can sign up here.
-
如何針對程式碼錯誤進行意見反應或取得協助?
-
開發團隊非常樂意使用者回報程式碼錯誤、提出功能建議及意見反應。請前往 GitHub 的〈Issues〉頁面,搜尋現有的的問題回報或提交新的問題。我們會試著在外掛論壇將這裡問題回報進行分級、將全部討論集中在 GitHub 存放庫,以便讓使用者儘速獲得回應,並減少重複工作。
-
Do I have to use the Gutenberg plugin to get access to these features?
-
It depends on the feature you want to use! Keep in mind that each version of WordPress after 5.0 comes with bundled versions of the Gutenberg plugin, automatically containing new features and changes. If you want the cutting edge features, including more experimental items, you will need to use the plugin. You can read more here about whether using the plugin is right for you.
-
何處可獲得各個 WordPress 核心程式發佈版本所納入的 Gutenberg 外掛版本資訊?
-
請參閱〈WordPress 整合的 Gutenberg 版本〉,便能從文件表格展示的資料,獲得在各個 WordPress 核心程式發佈版本所納入的 Gutenberg 外掛版本資訊。
-
這個專案的下一個階段為何?
-
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 2020, 2019, and 2018. Additionally, you can follow the biweekly release notes and monthly project plan updates on the Make WordPress Core blog for more up to date information about what’s happening now.
-
如何進一步了解 Gutenberg 相關資訊?
-
This plugin and subsequently the core show the third evolution of WordPress, broadly speaking. What started as a blogging platform shifted to become a CMS and is shifting again to become a site builder.
That isn't necessarily a bad thing, but for those looking for a CMS (separation of concerns, keeping content separate from presentation, etc) this shift in direction will meet my needs less.
Gutenberg is buggy, slow, resource intensive, and unpredictable. I've built several themes based on Gutenberg blocks and gave it a good go... If you are looking for a full site editor this is the future. If you're looking for a CMS this isn't the direction you want to go.
Gutenberg has by far the worst UI and thus UX I've ever seen and I know of a few other CMSs. It's been in development as long as Elementor, but the two are worlds apart.
I could certainly make a video pointing out at least 100 places where it lacks usability and logic. But first, you're not allowed to put URLs here, and second (more importantly), that wouldn't change anything.
It would be wasted lifetime. It might interest a few people here, but it would never change anything about the development itself. I've created tickets on Github often enough and they are either still open or have been closed.
Example? In the beginning you could permanently disable the fullscreen view. At some point that was changed and as soon as you clear cookies you have to disable it again. Just an example of a ticket about lack of usability created about 2 years ago
I ran a website for over 2 years with the sole purpose of providing up-to-date instructions for the new block editor (in German language). Three times a year I had to revise it completely. That I had to create over 300 new screenshots for an update for this was not a rarity, rather normal. And why? Because the dev team decided to use new icons. Or because they reordered or added something or moved it from a list to a sublist (and that per block). Or because they moved from the toolbar to the sidebar or vice versa, etc. etc.
The devs don't seem to care that new things need up-to-date guides, videos, tutorials, books, etc., because it's simply impossible to keep them up-to-date all the time. So I resigned, no more tickets, no more tutorials.
I've been developing websites for over 20 years and I love new techniques, I've seen the developments from pure table layout (CSS 2) with browser fixes (IE 5 and up) to CSS Grid, Flexbox etc. and have always been happy and excited to learn. This is also true for CMSs. I have worked with some.
I'm excited about new techniques and always like to learn new things. I'm only writing this because so often you can read here "people don't like change or they just haven't explored Gutenberg enough or they are inexperienced users". NO! That is not true in this case. And this argument "You have to be thankful because there are people who develop this voluntarily" ... first, there are a lot of Automattic paid devs among them, and second, I don't thank any construction company for putting a skyscraper right outside my window that blocks my view, even if I get anything inside for free.
I respect the work, but I don't have to like it and criticism can be quite positive. Dear devs, what I see is a development that is in love with details and features that can excite programmers, but the regular users are not considered at all. And these are the people for whom I create websites and to whom I have to explain something that could look and work differently tomorrow.
I could write so much more, but now I've wasted enough of my lifetime.
Worst editor ever.
Have the will to compete with Elementor or Divi, but have zero efficiency. The BO UI is terrible, 10 years old and make it unattractive to use. Terrible experience.
Terrible editor, con fallas, desorganizado, las funciones mas necesarias estas ocultas y se pierde tiempo en encontrarlas, tratan de imitar a elementor pero lo hacen desastrozamente, en definitiva desactivar este plugin es lo primero que hago en instalaciones nuevas
This editor is very difficult to use. I wasted at least 2 and half hour making simple design. Unable to manage costume width and height. Even a simple table I was unable to handle properly. I was forced to use old classic editor to make tabular data which has the property of Colspan.
Who the h... puts a confirmation notice on a save button that looks exactly like the button you just pressed? there is no indication whatsoever that there is an notice telling you to check your changes before saving, so now you have to press publish twice to get your page or post published, guess who lost a full nigth of work because of that? seriously thanks Guttemberg thanks.
閱讀全部 3,500 則使用者評論
以下人員參與了開源軟體〈Gutenberg〉的開發相關工作。
參與者
如需進一步了解 Gutenberg 12.4.1 的變更記錄,請參閱 GitHub 上的〈Release〉頁面。