Gutenberg

外掛說明

Gutenberg 這個代號是建置及發佈 WordPress 網站的全新標準方式,如同歐洲的古騰堡印刷術革命一般,它能徹底改變內容發佈的使用者體驗。目前這個專案進度為四個階段中的第一階段,影響層面遍及 WordPress 的內容編輯、客製化、協同作業及多語內容,並且首重全新的編輯體驗,也就是區塊編輯器。

區塊編輯器為頁面及文章導入模組化方法:在編輯器中的每一「塊」內容,從段落、圖片庫到標題,都是個別區塊。就像實體區塊一樣,WordPress 的區塊可以進行新增、排列及重新排列,讓 WordPress 使用者得以透過直觀的方式,建立內容豐富的頁面,而不需要採用短代碼或自訂 HTML 程式碼等因應措施。

區塊編輯器首次發佈於 2018 年 12 月,開發團隊始終致力於改進使用者體驗,建立更多更好的區塊,並為接下來的三個階段奠定基礎。Gutenberg 外掛讓使用者能使用最新版本區塊編輯器的早期測試功能,甚至激發使用者靈感,進而建立自己專屬的區塊。

進一步了解

  • 使用者線上說明文件:請參閱〈WordPress 編輯器〉線上文件,以便進一步了解作者如何使用編輯器建立文章及頁面的詳細資料。

  • 開發者線上說明文件:擴充性及客製化是 WordPress 平台的核心,請參閱〈Developer Documentation〉,以便進一步了解擴充編輯器功能的教學課程、說明文件及 API 參照。

  • 參與者:Gutenberg 是開放原始碼專案,並且歡迎全部開發者、設計師、技術文件作者及編審人員參與。請參閱〈Contributor Guide〉以進一步了解能參與哪個部分的詳細資料。

Gutenberg 專案的開發交流中心集中在 GitHub:https://github.com/wordpress/gutenberg

請在 Make WordPress 部落格及 Slack 的 #core-editor 頻道討論這個專案。註冊 Slack 相關資訊

常見問題集

如何針對程式碼錯誤進行意見反應或取得協助?

開發團隊非常樂意使用者回報程式碼錯誤、提出功能建議及意見反應。請前往 GitHub 的〈Issues〉頁面,搜尋現有的的問題回報或提交新的問題。我們會試著在外掛論壇將這裡問題回報進行分級、將全部討論集中在 GitHub 存放庫,以便讓使用者儘速獲得回應,並減少重複工作。

這個專案的下一個階段為何?

這個專案的四個階段分別為內容編輯、客製化、協同作業及多語內容,大家應該聽過 Matt 在 2019 年2018 年的 State of the Word 演說,提及這個專案及各個階段的資訊。此外,大家也可以追蹤 Make WordPress Core 官方部落格的相關更新資訊。

如何進一步了解 Gutenberg 相關資訊?

何處可獲得各個 WordPress 核心程式發佈版本所納入的 Gutenberg 外掛版本資訊?

請參閱這份文件,便能從文件表格展示的資料,獲得在各個 WordPress 核心程式發佈版本所納入的 Gutenberg 外掛版本資訊。

使用者評論

2021 年 7 月 29 日
All this 'plugin' or 'site builder' has done is both sadden and anger me. For years i've built websites where the content is added through the classic editor/advanced custom fields 'flexible content block'. This 'flexible content' would offer a user options simular to what gutenberg does like 'images' or 'gallery' which could be inserted after the classic editor content. A major downside being the lack of a preview, which due to how 'limited' the options in these 'acf blocks' are - really hasn't been a issue. Gutenberg should have been ideal for this. A live preview, cleaner ui, blocks and what looked like >optional< extra options. Exept when it launched the way it functioned made it a giant headache, not worth using. I've found after more than 2 years the exact same issues we had are still present. This thing is a NIGHTMARE to scale back towards something usable for someone who isn't a "designer". I can only assume i am ignorant of some solutions, at this point i've just given up. I find the documentation is a pain to read through, unclear about so many things that seem so unnecessarily complex. I faceplanted into so many dissapointments/walls: Why can't i disable some options!! it's like welded down, i don't need my client to stretch a 100x100px image over the entire page The ui still so clunky and the lack of focus on things, you get lost while editing and i'm not even one of our clients who just wish to say "hello we sell tasty fish" [pictures of some fish]. All of this seems so overly catered to a designer or highly experienced user. How the blocks are puked out on the page, how little control i have over anything inside of them or how they're often broken from the start. The non functional preview device switch which does NOTHING for websites that use media queries, it's just a narrower container that in some cases show a broken version of a theme The creation of a simple block, I MUST be misunderstanding something?!! the documentation seems so incredibly unclear, maybe even incomplete.. i'm continuously staring at giant parchment's written by some priest from the 1400's, 100s of lines of code for just a simple new block.The obscene output and options of some blocks like the default 'gallery' block. Why allow link opening to a useless 'media file' or even worse 'source link' behind /block?!! i can't disable this either?! It's exhausting to try and develop something in this thing that tries to conform it to more specific needs or a smaller scope initially. I'm sure this thing will develop into something you can "build a website" with eventually. But this falls back on the same argument i've seen repeated so many times. A huge chunk of wordpress's users aren't going to be the designers Gutenberg seems to want them to be. Gutenberg may push towards more and more expansive sets of options and features. But as long as a developer who is used to accessing any and all the stuff wordpress outputs, isn't able to - this thing will be rejected until the end of time.
2021 年 7 月 26 日
I see most people dont like Gutenberg, they are may be form the old years, always think the world is stable and not be change. I like Gutenberg!
2021 年 7 月 25 日
A horrible page builder, to avoid. Install Classic Editor plugin as an alternative, or other page builders available in the market (check its reviews to find out what users think of Gutenberg...)
2021 年 7 月 25 日
Thanks to the Gutenberg my website (which includes my WEB SHOP!) is completely useless since I can't even UPDATE or SAVE changes in my widgets! Also, all the widgets are EMPTY after the latest update. I've wasted hours on researching and trying to find a solution but with no luck! I've even tried to bypass the plugin by disabling it but again with no luck! I hope developers are reading this and will find a solution ASAP!
2021 年 7 月 24 日
I can't stand this editor. It is clunky, ugly, unintuitive and hard to use. My clients can't stand it either. And now, this HORRIBLE editor is part of the widgets area!!! This is the worst thing to EVER happen to WordPress and will likely be its ultimate downfall. I am already looking for alternative platforms. Sad to say, after making websites with WordPress for over 10 years... it's time to find something new. Gutenburg is the end of WP 🙁
閱讀全部 3,387 則使用者評論

參與者及開發者

以下人員參與了開源軟體〈Gutenberg〉的開發相關工作。

參與者

Gutenberg 外掛目前已有 51 個本地化語言版本。 感謝全部譯者為這個外掛做出的貢獻。

將 Gutenberg 外掛本地化為台灣繁體中文版

對開發相關資訊感興趣?

任何人均可瀏覽程式碼、查看 SVN 存放庫,或透過 RSS 訂閱開發記錄

變更記錄

如需進一步了解 Gutenberg 11.1.0 的變更記錄,請參閱 GitHub 上的〈Release〉頁面。