རྩོམ་སྒྲིག་འདུ་གནས།

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:

The block unifies multiple interfaces. If we add that on top of the existing interface, it would add complexity, as opposed to remove it.

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.

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.

Considering the whole interface lays a solid foundation for the next focus, full site customization.

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.

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.

བྱས་རྗེས་འཇོག་མཁན།

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.

གདེང་འཇོག

I don't know why they choose this Plugin as default editor, but when I showed it to the people who should use it they didn't want me to update. Lucky for me I test WordPress updates always on a Local-Test-Server so I just didn't bother with that editor in the live environment.
But when I was playing around with that thing it felt not really intuitive, why fix was was not broken. I've seen this a lot on many projects/websites these days. It's trendy to make things more difficult.
I always though Software should make the life more easy instead of getting you more work?
It should not be rocket since to write something with some basic formatting. I mean when its more easy to write it in plain HTML, then something went really wrong
Now I installed the Disable-Gutenberg Plugin and everything is like before!^-^

For almost 10 years I've been a WordPress evangelist. When someone - anyone - has asked me what system to use for a web property, whether it's an enterprise-level multisite to your mum and dad's travel blog, the answer has been the same. WordPress. If anyone has had reservations about it because, you know, it's 'technical' and they've heard of these things called Wix or Squarespace, I've told them to persevere - and that, in fact, they won't need to persevere for long, because WordPress is intuitive, clever, user-friendly and fun, and they'll 'get it' in no time at all. And to a tee, every client/friend/acquaintance who I've pushed to WordPress has come back with positive feedback.
I will no longer be recommending WordPress. This is their Nokia moment. Forcing this cumbersome, unfriendly, infuriating and opaque layer of content management over a system that was already working perfectly reeks of sheer bloody-mindedness and ignorance.
Don't tell me I fear change. I embrace change, when it has a point. But the manner in which Gutenberg has been force-fed to a global audience of loyal designers, developers and content managers is appalling. I don't care that I can disable it with a plugin; I'm hardly going to recommend that as a future-proof process to clients, nor adopt it myself.
The only good thing to come out of this (and I feel slightly ill as I say it, for I have really, truly loved and defended WordPress for years) is that it's opened me up to a world of new CMSs.
I'll be migrating my personal site to Craft. And while I know my lone voice will mean little to nothing in what seems to be a determined rush to implement Gutenberg come hell or high water, I will never, never revisit WordPress until this shoddy plugin is removed from core.

The UI for the plugin is a nightmare, for instance, I find myself mousing over several areas of the block UI elements to find the block configure/options menu. I have no clue where things are. This plugin component has potential but the UI/UX just needs to trashed and redone, by a different designer.

...other than to frustrate.
The Dashboard admin menu and Appearance > Menus still 'work' almost exactly as on day one, have basically become a UX nightmare, but 'berg' made it to the front of the line. So they tried to implement something that has been done so much better 100+ times over instead of updating core mechanics.
Well, kudos to the authors of all those 'disable' Gutenberg plugins. You are my heroes.

I am not a developer. I am not a coder. I am simply a person who has and maintains their own sites, and on occasion puts up and maintains the sites of others.
As soon as I updated my test site to Gutenberg, I was immediately completely unable to figure out how to manage the site that I have successfully looked after for 10+ years.
Thanks WordPress. Gutenberg Sucks. Big time.
Now I"m dependant on yet another plugin to keep my site functioning. I also have to worry about that plugin developer abandoning their plugin, or deciding to charge for it. Or perhaps it becoming incompatible with another WP update in the future.
I don't know who the mastermind was who came up with this brainchild, but like when NGG was sold years ago, this is an epic fail.
Paint me disillusioned and dissatisfied.