Gutenberg Editor Review: Please Don’t Include This in WordPress Core

Much of my time on here generally focuses around reviewing and comparing a handful of WordPress themes or plugins against one another. In today’s post, however, I want to take a closer look at one new WordPress plugin: the Gutenberg editor plugin.

Some of you may be wondering what makes this plugin so special that it gets its very own post. Well, there are a number of reasons for that. Although it was just released in June of 2017, WordPress promises that it will simplify the process of creating rich block content (what that means exactly will be explained below). Here is an example page the developers have created:

An example page the Gutenberg development team has put together demonstrating how the plugin works on the front-end.

One of the more compelling reasons to check out this plugin right now, however, is that it isn’t going to be a plugin for very long. The team behind it has been hard at work trying to get the editor ready to merge in the next WordPress update. Currently, they’re aiming to complete it and have it ready for launch for 4.9, for which a release date it yet to be set.

While the development team works on fixing the noted bugs and issues discovered within the new editor, I wanted to take some time to download the plugin they’ve been kind enough to share with us in beta and give it a test drive. If you’re as curious as I am about what it’s going to be like to create content in the new Gutenberg editor, hop into the passenger seat as I take this bad boy for a ride.

A Review of the Gutenberg Editor

It really feels as though the Gutenberg team has something really special here, something that will greatly improve the text creation and editing process within WordPress. Considering the number of plugins we use to expand the WYSIWYG and to simplify the process of switching between composing and previewing, this plugin seems well-intentioned.

So far, here is what I’ve been able to uncover:

It Hasn’t Been Well-Reviewed

Granted, the Gutenberg plugin is still in beta – they even warn you about that in the description in the WordPress Theme Directory – but the ratings on it so far aren’t great.

While there are currently only 15 reviews for the plugin, it looks like users have had a very strong reaction to it on both ends of the spectrum. Having now tested the plugin for myself, I’m actually surprised that anyone would have anything positive to say about it. I’ll explain more on that below.

Here is a taste of some of the negative reviews, all of which I happen to agree with:

“Clients like WP because of its simple UI. Force this on people and you may as well use Drupal.”

“Sorry, but this looks and feels bad, and is a productivity drain. Hiding UI elements until you click on things is terribly confusing for some new people (the opposite of your goal.) You’ve just doubled the number of clicks I need to accomplish the exact same thing.”

“No thanks.”

Yeah, it’s not good, folks.

It’s an Attempt at Distraction-Free Writing

This is what Gutenberg looks like in the visual editor:

This is what it looks like in the text editor:

If you click on the Post Settings button in the top-right corner of the page or on the “X” in the corner of the Post Settings widget, you can close that module for a truly distraction-free writing experience:

In addition, most of the text block and formatting options are now tucked away into the Insert tab at the top of the page. The rest only appear when you hover over each created block.

If I had to give one positive word about the Gutenberg editor, it would be about this. For people who enjoy working with a distraction-free interface, this is a nice touch… though, at the same time, it’s not totally distraction-free as the rest of the WordPress platform is visible all around. So, perhaps it’s more accurate to call this a minimal writing interface?

It’s Basically a Visual Builder

The Gutenberg editor is basically going to convert the visual and text editors we currently work with in WordPress and turn them into visual builder tools. There are a number of problems with this.

Literally every new paragraph, header, image, video embed, pull quote, bulleted list, and so on needs to reside in its own block:

All I wanted to do here was change three lines into an indented, bulleted list, but the Gutenberg editor forces the style upon the entire block:

The only way that I can see getting around this is if you somehow discover that the “Classic Text” formatting option under Insert allows you to circumnavigate the block building style of Gutenberg.

But how in the heck are you supposed to know this unless you spend time clicking through each of the insert options? Not exactly intuitive. No one has time for that. This new editor should take what we’re comfortable with and simplify it even further.

Part of the concern I have here is the inconvenience factor. Unless you’re building a homepage with small blocks of text that require different font types, styles, and sizes, there is absolutely no point in forcing users to create a new block every time they want to write a new paragraph or add a header to a section of paragraphs in WordPress. Absolutely. No. Point.

Another concern is the control of spacing. With this new blocked method of adding copy to a page, how will spacing between related items (say, a paragraph in one block and a bulleted list that belongs with it in another) work? Currently, I cannot answer that question for you as the preview functionality in Gutenberg doesn’t work.

Say Goodbye to Copy-and-Paste

As someone who likes to write her content outside of WordPress and then paste it in when I know it’s 100% ready to go, this is probably one of the more devastating parts about Gutenberg. When trying to paste text from Word into the new editor, all formatting is lost. So, unless I’m willing to write all my content with HTML coding built in and then paste it into the Text tab, I’m going to have to start following a completely new copywriting process.

Image Editing Is Limited

Now, I get that the developers’ goal is to simplify content creation in WordPress. Trust me, I get that and I respect that. But I think they’re going about it the wrong way. Case in point: When you try to upload or select an image in the Images block, you’ll see that there are no longer options for sizing, alignment, or hyperlinking. Once you have selected a photo and entered the metadata, it is inserted into the page, but automatically centers and scales to the full-width:

If you want to size it differently, all you can do is select one of the text wrapping options and then it’ll shrink to about half the size and move over for text to wrap around it:

While you can probably customize the size within the code in the Text editor, that defeats the whole point in using these blocks in the first place.

And while we’re on the subject of images, let’s talk about the gallery tool. You’re likely using a gallery plugin to accomplish this right now. If you’re not, I’d strongly advise that you do so going forward as the new gallery functionality doesn’t work very well. It took a couple tries to select multiple images for the gallery and I don’t think the end result displays properly:

Again, I can’t actually verify the on-page results as previewing on the front-end is disabled, so perhaps this is more an issue with the Gutenberg display than with the end result.

Video Embedding Isn’t That Great Either

Let’s talk about the insert options at the top of the Gutenberg editor. While I can see why they’d want to put the most popular blocks and formatting options up there, I don’t really see why they had to break out 35 different website embedding options.

Embedding used to be so simple. Just grab the embed code for the video, slideshow, infographic, or whatever, and then paste it into the text editor. See:

Now I don’t think you can even do that anymore.

See how there’s a YouTube iframe embedded in the top of my blog post? Well, the second after I took this screenshot, the new code completely disappeared. I thought maybe it shifted somewhere else on the page or that somehow I had undone my change, so I tried again. Five. More. Times. The iframe disappeared every single time until I finally gave up, switched back to the visual editor, and used the embed tool. In all honesty, I don’t think it looks very good:

Sigh. “Why do you [guys] have to go and make things so complicated?”

There’s a Lot That Just Doesn’t Make Any Sense

Okay, I know this section is going to seem like a mishmash of a lot of different things and that’s because it is. I’ve poked around in all the different settings and customization options and, quite frankly, I just don’t get the purpose for most of it. It’s like they wanted to simplify something that didn’t need simplification and, in doing so, just way, way overcomplicated it.

Here are some of the remaining questions I had as I worked my way through here:

How often will we need to use the drop cap function in our blocks of text?

The reason I ask this is because when you click on a block of text in the Visual tab, the only Post Settings “setting” you can change on the right-hand sidebar is to create a drop cap. If I were a new user to WordPress, I’d be truly confused and wondering where the rest of my options were… and if I were in the minority of people not making full use of drop caps in my writing.

What is the point of the gear in the top-right corner of every block?

The second you click on any blocked element in Gutenberg, the available settings open in the left-hand pop-up, so I’m not sure of the purpose of the gear icon. When the settings are open and you click on the gear, the pop-up doesn’t close. And when the settings are closed, the only thing it opens is the alignment choices. In order to see the other settings options, you have to actually click on the block to reveal them. So why have the gear there?

What’s up with the button?

As of right now, you can add call-to-action buttons to your posts and pages with the visual editor. It’s not a great tool, but it’s there if you want it. That being said, the ones in the visual editor now actually look like buttons. What we get with Gutenberg is, well…

It looks like something you’d see in one of those Buzzfeed articles about awkward, drunken texts you get from your mom.

Why did they bother with the Latest Posts widget?

There’s another new addition to the visual editor Insert options called “Latest Posts.” It’s basically an attempt at replacing related posts plugins. Under no circumstances should anyone use this and I’ll give you five reasons:

  • There are no images or design elements to help draw attention to this callout.
  • It’s just a bulleted list of links to the last five blogs on your site.
  • The bullets don’t align with the rest of the text on the page.
  • You have no control over which blog posts appear, in which order they appear, or how they appear.
  • Oh, and most of the punctuation reverts back to the HTML code.

It looks terrible. Please don’t use this.

Wrapping Up

While the developers working on the Gutenberg editor plugin have obviously put a lot of work into creating the plugin and I commend them on their efforts so far, the truth is, this plugin is nowhere near ready to be included in WordPress and needs a lot more work, in particular, UX work.

The WordPress.org Gutenberg page states: “The goal of the block editor is to make adding rich content to WordPress simple and enjoyable.”

Unfortunately, the plugin as it currently functions is a long, long way from achieving this goal.

As one of the reviewers on WordPress.org says:

“Please don’t add this to next core. Leave it as a plugin and let us the choice to use or not.”

I’m in total agreement with this statement. Even if they do work out all the issues and make it a completely streamlined and simplified visual builder tool we appreciate more than what they’ve given us now to experiment with, I don’t think it should be forced.

Brenda Barron
Over to you: Do you think the current text editor in WordPress even needs an upgrade? If so, what changes do you actually want to see made to it?

46 Responses

  • New Recruit

    Completely agree with your assessment of the state of the plugin.

    Except for in the post that you link to referring to 4.9 that Matt Mullenweg wrote, he specifically states that he’d like to push Gutenberg back to the 5.0 release to give the plugin more development time.

    So the core plea of the article is kind of moot.

  • New Recruit

    I would agree with this article. What’s the point? I’ve been using wordpress to make sites for my clients for many years now and the editor is finally at a point where it works really well and properly across browsers, and just when it’s going so well they want to completely change the whole thing? I agree there could be some improvements made but this is not the right direction and will only serve to confuse those who are not tech-savy developers. Don’t try to fix what isn’t broken people!

  • Mr. LetsFixTheWorld

    It’s unfortunate that they call this a Beta. That gives people the impression that it’s almost a Pre-Release candidate, when it’s not near that stage.

    I see a lot of questions in this and other reviews – as though a topic stops with the question and there are no answers. I suggest an interview with Gutenberg developers, perhaps Matt himself, and get answers to all of those questions and concerns. Post that as a follow-up blog. WHY did they make it work like this? What is the use case for those specific inconveniences? How might they respond with changes to common concerns?

    Because this new editor adds much more complexity, I’m wondering why it’s not being pitched as an *optional* “Pro-like” alternative to the default editor or other plugins, where from Settings>General or a button click in the page/post editor we can toggle this editor and use it as-desired. Not ready for prime time? No prob, just disable it until 5.1, .2, .3…

    So rather than pitching this like it’s a done deal, like there’s nothing anyone can do, like we’re all going to be forced to do something no one likes (based on the wealth of 15, now 16 reviews) … how about going a little further to get this blog in front of a LOT of eyes with a post titled “WordPress Responds to Gutenberg Reviews”?

  • Mr. LetsFixTheWorld

    From one of the reviews: “Hiding UI elements until you click on things is terribly confusing for some new people (the opposite of your goal.)” This is exactly one of the things that turned me off from Upfront.

    And I noted with humor: “The Gutenberg editor is basically going to convert the visual and text editors we currently work with in WordPress and turn them into visual builder tools (kind of like Upfront). There are a number of problems with this.”

    … Uh, yeah, there are indeed a number of problems with the Upfront visual builder approach. I’m not saying the effort is unworthy or that Upfront itself is unusable (obviously). I’m saying the implementations for both Upfront and Gutenberg may be too radical for the problems they’re trying solve. They are simply creating new problems in the name of being different. We don’t need new problems, we need solutions to old problems. That’s often lost in the quest for New, Different, Evolution, and Revolution.

    So while this article is rather critical, with a “Please Don’t Include This” header and summary, I’ve been as concerned about Upfront for many of the same reasons cited here. And I’m having a chuckle at the irony of the implication that “our software continues to be good for all the same reasons that this other software is bad”. It’s just something for Upfront roapmap planners and developers to think about.

  • Jan
    New Recruit

    Wow, sure it has rough edges but this is the future.
    It might not make sense if you are a one-man-does-everything website but if you have a larger organisation with multiple roles, this perfectly makes sense.

    I work for a media company that just built their custom CMS used by 4000 journalists and about 2000 editors with every possible publishing channel (website, mobile app, print papers, magazines, …). Guess what: our editor is not that different from this one: block based.

    Why would you want to do this? Well, I’ll let the guys from The Guardian explain it as they also did this and they explain it quite well:
    https://www.youtube.com/watch?v=31EpyxcmBeU
    You can find the deck here if that works better for you:
    https://speakerdeck.com/oliverjash/building-a-cms-for-the-responsive-web

    Sure it still needs a lot of work but I this gets me excited!

    • Design Lord, Child of Thor

      Did you follow the speakerdeck that you linked to?
      The solution that is is presenting has little to do with using a block based content editor for any form of presentation…. in fact it is the opposite.

      From the presentation, the CMS and editors should not be responsible for presentation.

      It’s great that the Guardian felt they ‘needed’ to build their own CMS, but that’s really not true. Everything that they wish to do, from the editor and CMS level could quite easily and quickly be achived using WordPress and Custom Post Types and Custom Fields… very easily and very quickly…

      Their solution falls back to JSON endpoints… how exactly is their custom built solution better and a more efficient use of Guardian resources, than building out a Decoupled WordPress solution and using the REST API and Angular2/React/Vue/WhateverJSFrameWorkYouLike for front end presentation?

      What am I missing?

  • New Recruit

    Gutenberg Editor is stupid! The current editor works just fine and my clients understand it easily. I tell my clients, “if you can do Microsoft Word you can do WordPress”. In other words, do your work in Word then just simply copy and paste. They get that. And they find inserting images is easy too, and can resize on the fly.

    I’m very concerned if the Gutenberg Editor becomes the default and it’s implemented via WordPress’ auto-update. I can see it now, my clients calling me asking why they can’t do some simple task.

    So, what’s that saying? If it’s not broken there’s no need to fix it. The current editor works just fine.

  • Dan
    New Recruit

    I personally am of the opinion it’s going to be nowhere near ready for 4.9, but even beyond that I have a bigger issue: Matt pushes things Matt likes, and everyone just nods.

    I remember how hard he fought against including WP-API in core, all the hilariously high benchmarks he set before it would even be considered, mostly because he didn’t like it. Now there’s something he likes that’s not even built yet, and it has no such hurdles.

    Don’t get me wrong: Matt came up with the idea of WordPress, and built some of the earliest iterations. He is not, however, infallible, nor even Steve Jobs, and he should be not be treated as such.

  • Site Builder, Child of Zeus

    As with most thing WordPress, if we wanted better functionality – or different – we would download it based on the needs of the project, the experience of the client, and what we have planned for the site in the future. Forcing us to accept a block editor when we don’t need one spells trouble. And how is this going to play nicely with the visual editors we may already have in place like the Avia builder within Enfold, or Divi, or Beaver Builder?

  • New Recruit

    This seems to me like a potential push to make all of WordPress more like WordPress.com. Jetpack’s development history and shifting pricing model gives me the same sort of big brother vibe. I’ll refrain from judgment until I’ve worked with it and see how it impacts my clients, but I’m in agreement that the simplicity of the editor is its greatest strength. Most of my clients don’t want to drag n’ drop their way through posting content on a CONTENT Management System. They just want it simple, and predictable. It’s likely the future, sure, and will probably mean a lot of us are busier as fewer of our clients will be able to completely manage their own sites.

  • Design Lord, Child of Thor

    Why on earth!? Let’s keep the good old editor. I like to be able to switch between a simple editor and a page builder like Visual Composer. I hope that they just make it optional to install Gutenberg editor. If Gutenberg ends up having all the same features as page builders in the editor it will be total overkill for blogging.

  • Design Lord, Child of Thor

    The poster who said this smells of WP.org becoming WP.com is exactly right. That’s pretty much the plan from what I’m hearing. I, too, question what’s going to become of the existing page builders once Gutenberg becomes the default WP editor. There had better be a way to replace Gutenberg with one’s page builder of choice or there will be a huge uproar in the community not only from those who are used to using their chosen page builder, but those who build said page builders and make a living selling them.

    I am not a huge fan of the WP editor as it exists today. Adding TinyMCE Advanced helps, but the easiest and simplest way to use it is to compose in Word and paste the result into the editor in Visual Mode so that much of the formatting is retained. There’s a line to be walked between making the editor “user friendly”, i.e. suited for non-technical people, and “easy to use” for those of us who want to get things done quickly and not have to click and drag everything which takes forever. Even AWeber provides the options of using their drag-and-drop editor, HTML editor or basic text editor so that it’s not a one-size-frustrates-all situation that appears to be the direction WP is heading.

    Most definitely keep Gutenberg as a plugin and out of the WP core!

    • New Recruit

      As a homeschooling father/grand-father who has raised 6 children and who has been involved in the homeschooling community for over 30 years, I disagree. We have always been pleased and amazed at how children can grasp complex concepts and processes when they have not become accustomed to what we call “the dumbing-down effect” that we witness in public schools. The evidence is readily seen in the latest two generations of voters in this country – it is quite disturbing. If we continue to make things EASY ON OURSELVES, and not expect much out of our children, we will continue this spiral downward. You coders out there know what I mean!
      As far as the article goes: Agree, agree, agree!

  • Flash Drive

    It’s a serious case of WP schizophrenia or dual personality disease, IMO.

    If the goal of WP is to convert people who are using Medium to WP (not really going to happen for so many reasons that have nothing to do with this editor or that editor), then perhaps we should have some sort of plugin that simply converts the backend to that structure.
    If we are meant to be expanding the reach of WP for actual, usable, CMS based sites that are not blog-centric, then this is a terrible way to go about it. It’s almost like Matt, etc have seen the success and popularity of Divi, Beaver Builder, Upfront, etc and are attempting to replicate that without actually understanding why and how people use the builders to generate sites, not blogs per se.

    This goal of making XX% of the web run on WP is likely something that could be revisited. Maybe instead of trying to blanket the web with WP, we should spend more time and effort making the WP users we have more satisfied; this should help the spread of the platform via happy referrals. Trying to compete with Wix, Weebly, Squarespace – at the same time that we’re trying to compete with Medium – is probably not the best use of time and efforts.

    • Site Builder, Child of Zeus

      “Working with TinyMCE is a pain if you’re a theme or plugin developer.”

      It’s really not, or at least not WP’s implementation. It’s limited to doing one particular task well, for sure. Enter a page-builder if you want to do more elaborate layouts quick and dirty, or roll your own set of block editors with CMB2 if you prefer to not let your client break things.

      I definitely think there’s room for innovation (or stabilisation) in the page builder economy. Some are getting very good (Elementor and Tailor get honourable mentions from me, while I agree with someone else here that Upfront causes more problems than it solves), but many still not as intuitive, lightweight, or controllable as they could be. So if Gutenberg wanted to model a “WordPress way” for page builders to behave, that would make it a great project.

      But it really, really needs to remain a plugin, and one with options to choose it or the current editor depending on the context you’re working in.

  • New Recruit

    Agree. This reminds me of the change Microsoft did when they moved from Windows 7 structure and GUI, which was the interface we knew and loved, to the nightmare that became windows 8-10. Yes, the graphics and design people liked it since they designed it. To the rest of us, it became our daily nightmare. I solved it by now doing most work on a Chromebook, not a PC. Let’s hope wordpress doesn’t pander to designers and let us bloggers and developers stick with what we like and love about wordpress.

  • Tim
    New Recruit

    As a dedicated user of the Avada theme, I like its built-in Fusion Builder wysiwyg editor. And I want to always have the option to alternate between that one and a very simple WordPress editor like the current default WP editor.

    Give us the choice to use that–or not. Don’t force a solution on us that independent plugin publishers have already created and done so very nicely!

    I am a geek myself, but I have a real issue with the kind of geeks who are always trying to figure out how to improve something that doesn’t need improving. Are these guys trying to emulate Microsoft?

    How many clients have asked for this, and how much user-testing have you done before bringing the damn thing to market?

  • New Recruit

    As an aside, WordPress Multisite has always removed iframes (as well as JavaScript and a bunch of other potentially unsafe code) from the editor when switching back and forth between text & visual or when saving a post. You’ve possibly never noticed it before because you are either an administrator, you’re not using multisite, or you’re using a plugin to allow unfiltered HTML.

    Why on earth would you try to paste the YouTube iframe code instead of just using the oembed functionality that’s baked into WordPress?

  • WPMU DEV Initiate

    “If I wanted fries with that, I would have ordered fries with that! ”

    That’s my favourite line at MacDonalds. It’s annoying enough that they ask that every time, BUT – if they automatically added a serving of fries to my order without me wanting it, I wouldn’t be a MacDonalds customer for long!

    By incorporating this into the core, they’re forcing me to have a serving of fries with my order – AND forcing me to eat them as well!

    Leave it as a plugin. I certainly won’t update my WP installations if they incorporate this into the core. This will generate a lot of negative publicity for WP, which is a real shame.

  • New Recruit

    Over the past few years I had to tell and convince people that WordPress is more and more becoming a decent CMS instead of just being a blog editor.

    The sites I build for clients are sites that need a content management solution, and I more than often choose WordPress for that. I’ll take this some steps further by completely disabling the visual part of the standard editor, and create custom post types for all of the content they need, and present that with well-structured content-blocks to be filled in(I do a lot of Advanced Custom Fields work here).
    Building sites, and more importantly, a back-end that makes sure things don’t get messed up, has benefitted me and my clients for a long time.

    I never, ever, use a Visual Editor of any kind because I want clean, understandable and predictable (HTML) code that follows the site’s guidelines as specified in CSS.
    Why on earth would I give my clients the opportunity to change the properties (font, size, color etc.) of, say, a H2 element?

    WordPress is a remarkable and flexible CMS (and that is what Matt wants it to be) and if used in that manner, we don’t need or even want any fancy visual builder, ever.

  • Dragon Rider

    Completely Agree.
    After reading this I uploaded it to our test bed and played at creating a few pages and posts.
    After about 45 minutes I was ready to throw my keyboard at something.
    Please DO NOT include this in WP core is all I can say.
    Old saying applies here “If it ain’t broke, don’t fix it”

    Jaxom

  • Site Builder, Child of Zeus

    I’ve not even looked at Gutenberg yet and this review has made me even less inclined to try it out. The WP Core people need to remember that not everyone is running a publishing empire on their blog, a lot of its uses are NOT professionals and don’t use things like drop capitals or complex layouts… throwing this sort of complex editor at them is going to confuse them – its like telling people to use a Desktop Publishing tool to write a letter….

    How is this “plug-in which will become core” interact with other plug-ins that interact with the existing editor? Unless they make an easy set of endpoints and interactions I can see this plug-in breaking a good number of plug-ins

    It used to be that the WP core was slick and thin and people bolted on plugins to add the functionality they needed for their site… now WP core just seems to be getting more and more bloated and cluttered with things that might be needed by some people but not by everyone.

  • HummingBird

    I totally agree 100% since I was the one making that comment,
    “Please don’t add this to next core. Leave it as a plugin and let us the choice to use or not.”
    A plugin would make everyone happy you want it install it. You don’t want it Don’t install it.
    I too have installed and tested the plugin beta and Didn’t like it made writing a post twice as long. and very confusing.
    I also tried a few time to get used to upfront and do not like that editor either i installed Divi and Loved it.
    Wow I feel famous LOL :->

  • New Recruit

    *SIGH* If they DO make this the default editor, looks like I’ll have to find a plugin to put it back the way it was. Just like when they made linking “easier” with that craptastic “inline linking” thing. It was such a nightmare that I had to get a plugin to revert back to the old way of adding links. I wish WordPress would stop trying to make my life easier. Instead of adding things no one is asking for, maybe they could work on the zillion tickets and requests for things people actually DO want.

  • Mr. LetsFixTheWorld

    There is a lot of FUD ( Fears, Uncertainty, and Doubt) about Gutenberg, and a lot of unanswered questions that have people in a tizzy. The authors are taking steps to address this marketing issue. (I suggested above that WPMU DEV take the initiative to get a jump on this but … you snooze you lose.)

    Anyone who actually cares about this should subscribe (with whatever tool you prefer) to this page at the Gutenberg Github Project: https://github.com/WordPress/gutenberg/blob/master/docs/faq.md

    Of particular note: From notes there it seems they were planning this for three months and then developing for another three. They published what they have now, calling it an early beta, which I believe is a big part of the public relations problem. As a developer I wouldn’t dare to call software a Beta after only spending three months in code. I think if they rename this to simply “early conceptual preview” that it will relieve some of the tension. That said, anyone who works with this software should realize by looking at the Github status (issues, forks, pull requests, etc) that this is in very active development, and all of this hullabaloo about “the end of the world as we know it” is serious over-reacting at this specific point in time.

    It’s time to chill, sit back, look forward to 4.9, and give them time to develop Gutenberg with a mind for all of the feedback they’ve been receiving so far.

  • Dragon Rider

    Hi Everyone
    I took Tony’s advice and went over to github and found this very interesting comment in there FAQ.
    “Will I be able to opt out of Gutenberg for my site?
    There will also be a “Classic Text” block, which is virtually the same as the current editor, except in block-form. There’s also likely to be a very popular plugin in the repository to replace Gutenberg with the classic editor.”

    Very Telling if I do say so myself.
    Jaxom

  • Recruit

    Hi
    Whilst the TinyMCE editor drives me crazy at times, Gutenberg is entirely out of touch with the mainstream usage of creating basic blog posts and articles. The blocks method would possibly (very maybe) only be useful when creating static web pages not daily posts.

    Methinks this might be a case of the Pareto princicple – where the 80% of users are ignored. WP is first and foremost a blogging tool and blogging website.

    Lets pray they keep Gutenberg as an option in some way – selectable or via plugin only otherwise we are in for a disaster for all our clients that can barely use the current visual editor to create a basic post!

  • WPMU DEV Initiate

    May be it’s time to look at Joomla and Drupal again? WordPress was perfect as a plugin and Theme developer, this Gutenberg freak show breaks everything. I have to lean a new CMS or instruct my clients to stay with V4.8x. Simply said, Gutenberg in the core is a deal breaker for me. I am sure most developers agree with me. For God’s sake, all my projects depend on the TinyMCE custom buttons to generate shortcodes and meta boxes. And reports are that they are also going to kill the widgets. How stupid are these people?

  • Ian
    New Recruit

    Existing editor is fine. I just added a new page to my site, and after several minutes messing around in cornerstone (via the X theme and it’s near invisible, faded out controls) which also uses blocks to add the different types of content, I thought to myself, do you know, this would be so much easier and quicker to do in the regular editor. So I did, and it was.
    But then my kids hate it, we are faced with a drag and drop generation who need an app for everything…

Comments are closed.