Gutenberg(古腾堡)

Description

Gutenberg 不仅仅是一个编辑器。虽然编辑器现在是焦点,但项目最终将影响整个发布体验,包括定制(下一个焦点区域)。

发现更多关于这个项目

编辑重点

「编辑器将创建一个新的页面、文章建设经验,使写丰富的文章毫不费力。为了编辑经验变得更简单,“区块”将会取代当今的短代码,自定义 HTML 或“神秘肉”嵌入模式。」
—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:

  1. The block unifies multiple interfaces. If we add that on top of the existing interface, it would add complexity, as opposed to remove it.
  2. 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.
  3. 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.
  4. Considering the whole interface lays a solid foundation for the next focus, full site customization.
  5. 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 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.

兼容性

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.

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.

贡献者

Gutenberg 由许多贡献者和志愿者构建。 请在 CONTRIBUTORS.md 中查看完整的名单。

注意:这个插件主要以英文撰写,并由贡献者翻译成中文。如果您觉得此插件的翻译可以进一步改进,或者您想提供翻译,请在 translate.wordpress.org 上提交您的翻译。

FAQ

我如何发送反馈或获得帮助来处理错误?

我们很想听听您的错误报告,功能建议和任何其他反馈!请在 GitHub 问题页面搜索或打开一个新的存在的问题(已英语为主)。虽然我们会尽量分流问题的报道在插件论坛,但是在 GitHub 库保持一切都集中您会得到一个更快的响应(还帮助我们减少重复劳动)。

我该如何贡献?

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?

Reviews

Why? Leave it as optional plugin

I don’t really understand what they’ve done and I don’t want to say more than what has already been said.

The real question is: the creators of Gutenberg Project are really working with this garbage???

Please at least add a button that allow users to switch between classic and this.

FIRE SOMEONE!

It is not enough to say this is pure garbage.
Someone responsible, or a whole board of directors needs to be replaced and put out to pasture.
Why take a beautiful, fully functioning platforms, used by 10s of millions and utterly destroy it? Just ego? A really study in psychology, but one which hurts so very many people.

Complex and cumbersome

Block-based design is just way too complex: we only need something that works like a word processor: make text editing and layout easy, straightforward.

I mean with this editor, just having a text editing area that is wide, scrolls properly, allows reorganizing text with simple cut’n paste wide editing has become… hard to impossible.

This thing was designed for content publishers, not blog writers.

Just terrible

Looks nice… but thats as far as it goes.

I have been developing with wordpress for 10 years and this new editor is just terrible. Not only is it full of bugs, its tricky to use and im finding it a pain for custom layouts.

Being generous, Gutenberg has been released WAY to early, but it should be an optional plugin at best. This should absolutely not be the default editor. 5 minutes of user testing tells you how bad this really is.

I love WordPress, I love that its open source.. but come on guys, someone has dropped the ball big time.

Had To Give Feedback

I’m good with change. Change happens and that’s that. It’s part of life. But this “Gutenberg Project” as you call it is not good at all. Please do the WordPress community a favor and ditch this thing immediately. I plead with you on behalf of the folks that have used this tool for a long time and the people that have stayed loyal to this software. We cannot see any value in the changes. The one-star reviews should be a big hint. I never feel the need to leave feedback. That said, I had to make my voice be heard tonight.

Read all 1,987 reviews

Contributors & Developers

“Gutenberg(古腾堡)” is open source software. The following people have contributed to this plugin.

Contributors

“Gutenberg(古腾堡)” has been translated into 43 locales. Thank you to the translators for their contributions.

Translate “Gutenberg(古腾堡)” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

Latest

Performance improvements

  • Optimize isViewportMatch
  • Performance: BlockListAppender: 1.7x increase on key press
  • Date: Optimize the usage of moment-timezone to save some kilobytes
  • RichText: selectionChange: bind on focus, unbind on blur
  • RichText: only replace range and nodes if different
  • Cache createBlock call in isUnmodifiedDefaultBlock
  • Edit Post: Select blocks only once multiple verified
  • RichText: Do not run valueToEditableHTML on every render
  • RichText: Reuse DOM document across calls to createEmpty
  • Only initialise TinyMCE once per instance
  • Optimize the insertion point component
  • Avoid rerending the current block if the previous block change
  • Avoid getBlock in block-list/block
  • Pass the registry argument to withDispatch to allow selectors to be used

Bug fixes

  • Annotations: Apply annotation className as string
  • RichText: Ensure instance is selected before setting back selection
  • Meta Boxes: Don’t hide disabled meta boxes by modifying DOM
  • Fix: Problems on Media & Text block resizing; Load wp-block-library styles before wp-edit-blocks
  • When a post is saved, check for tinymce and save any editors.
  • Fix: Undoing Image Selection from Media Library in Image Block breaks it
  • Add an end-to-end test for the HTML block
  • Fix regression when copying or cutting content in the editor
  • Fix issue where default appender has icons overlaying the text
  • Set document title for preview loading interstitial
  • Fix: Upload permissions error on end-to-end inline tokens test
  • Ensure classic block caret is in correct position after blur
  • Fix tab navigation sometimes skipping block UI
  • Improve font size picker accessibility: Use a menuitemradio role and better labels
  • Don’t show trashed reusable blocks in the editor or frontend
  • Rename functions, removing gutenberg_ prefix
  • Add block switcher end-to-end tests
  • Allow links in plugin group in the editor more menu
  • Introduce searching of block categories from slash inserter
  • Convert HTML formatting whitespace to spaces
  • Label link format with selected text, not full text
  • Ensure permalink panel is only displayed when a permalink is allowed
  • Allow the user to convert unembeddable URLs to links and try embedding again
  • Improve the top bar tools interaction and consistency
  • Fix overflowing content in the facebook embed preview screen
  • Add an action to set a category icon and correct block categories documentation
  • Fix: pasting a tag that is part of a transform and not matched ignores the content.
  • Packages: Extract Eslint config package
  • Add end-to-end test to catch revert of title during a preview after saving a draft
  • Avoid react warnings when merging two adjacent paragraphs
  • Avoid PHP notice in the recent comments block