Gutenberg

Description

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:

  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

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.

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.

FAQ

How can I send feedback or get help with a bug?

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.

How can I contribute?

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

Gutenberg is the future

WordPress has to stay relevant. Gutenberg is the future. I understand that a lot of people do not like change but Gutenberg is moving WordPress to the right direction.

unbelievable crap

Why dont you have zero stars? Because that is what this Gutenberg deserves.

I had no idea about this issue. Just upgraded one of my webs to 5.0 (thank god I did not do on the others) and encountered the disaster.

I tried to add some code, images and change an old page, and it was a complete nightmare.

– Adding images in the middle of the post? Impossible, not even by html. When trying the html view (not even easy to find) found the <p> crap in all the section…just imagine lol
The image would go to the start of the page and because in that page I started with a

  • when I tried to remove it in the code the whole text was converted to “li”….

    – Trying to add html code in that page was impossible without major trouble.

    – Besides the editor screen is way too narrow and totally unfriendly from an editor point of view. I mean TOTALLY UNFRIENDLY

    – Countless bugs and problems

    It seems that WordPress wants us to produce Facebook type of content now…but if I want to post things like facebook I just just Facebook, you know?

    This is totally unfriendly for writers, journalists and developers who need to create big pieces of text and content.

    Why did they force this change? Seems a very strange move. I wonder if it is being forced by above following some sort of agenda because it makes no sense to make it default and forced.

    The market does not like it. I mean, the WordPress market.

    WordPress is not yet the government that can enforce crap like this to us without alternative.

    So you either give back the classic editor or something very similar or at least the possibility to disable “Gutencrap” or many of your old users will end up changing the platform.

    I installed the classic editor plugin, but if this is not sorted will have to look for an alternative.

    In short: what a piece of garbage

  • i like it

    when it was optional i did not like it, now that i’m forced to use it, i like it, very versatile

    Awful

    I’ve registered here just for write about this piece of stupidness.

    Awful, awful, awful. Turn it off immidiately.

    Why not give users the choice?

    Past posts can be edited with the classic editor, which means it’s code is still in there — why not give users the choice for new posts?

    We won’t be rebuilding our editor plugins and hence are now forced to install the Classic Editor plugin.

    Writers, bloggers or journalists doesn´t need this at all…

    Please “keep it simple” just like a golden rule to respect time for users who doesn´t need this at all just for blogging or writing newspapers. If designers or code developers need Gutenberg, please make it a separate plugin or at least not mandatory for all.
    Most people does not have time or does not want to learn a new publishing way or “Blocks” or things like that. Thanks for reconsider.

    Read all 1ቁጥር_ቅርጸት_ሺወች_መስ797 reviews

    Contributors & Developers

    “Gutenberg” is open source software. The following people have contributed to this plugin.

    Contributors

    “Gutenberg” has been translated into 42 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

    • Parser: Make attribute parsing possessive (Fix High CPU usage).