blognaus

This is an excellent review by @iamfantastikate and I can’t find anything in either the review or her follow-up remarks that could rationally be disputed by any honest person. It’s a shame that it will be dismissed and ignored, just like all the others.

> The reason why we are not going to make it as a plugin is that once it’s optional, theme and plugin developers will just ignore it.

This argument doesn’t stack up. If Gutenberg is as good as you think it is, even if it’s an optional plugin (let alone the ‘core plugin’ suggestion in the OP), it will be adopted by huge numbers of users. If that happens, theme and plugin developers won’t be able to ignore it and stay relevant.

Your argument only works if you believe Gutenberg would be rejected en masse in a ‘free market’ scenario. Why would you think that?

> Sure, it’s great for that 300 wrd blog about a handbag

Personally, I don’t think it’s great for that either unless you’re putting all 300 words in one paragraph.

> posting in other people’s threads.

You might want to check who started this thread.

I would also encourage you to re-read this from the viewpoint of the users who are reviewing and commenting here.

https://tam.blog/2017/01/the-user-is-the-casualty-of-our-modern-building-process/

Please don’t make us your casualties.

I guess something like Gutenberg might be useful as an optional page builder for those people who have a need to arrange various media in a non-straightforward way and can cope with its interface idiosyncrasies.

That’s not to say it’s suitable for written content on a page or a post; it’s not. Anything that uses the block approach certainly shouldn’t be the default editor. That’s not how people write. The block approach is an awkward obstruction between the user’s brain and the written content ending up on a web page.

The recent idea I saw of de-highlighting everything but the current block also isn’t how people write, and it indicates to me that the people doing the design don’t really understand the requirements of a very large portion of the user base.

I should point out that I’m not some Luddite naysayer who’s opposed to change. When I saw the notice for Gutenberg I was genuinely excited to try it out, because the classic editor is certainly imperfect and old-fashioned and could do with improving. I had real enthusiasm for what sounded like A Good Thing.

My enthusiasm turned to dismay when I actually tried to use Gutenberg. It really was the most counter-intuitive and awkward editing experience of my life. I’ve used large numbers of web and text editors and word processors over many years, some with very arcane interfaces. WordStar, for example. Norton Editor. Programming editors. Various HTML editors. You name it.

None of them were as obstructive to the writing process as Gutenberg. None. It was the absolute worst editing experience ever. And this is for a task (text editing with the option of inserting a few other things) that has basically been a solved problem for many years. You’ve solved a problem that didn’t exist, and you’ve created a different problem that also didn’t exist.

I’ve built a few sites for community groups using WordPress and have been able to leave them in the hands of non-expert volunteers to maintain and fill with content. I don’t think a single one of those volunteers could deal with Gutenberg. If this thing is as inevitable as it seems, I’m now horribly embarrassed that I have put those groups into the position where they are soon not going to be able to maintain their sites without help.

I’m sorry if you’ve put your heart and soul into this thing and are dismayed by its reception, but you really do need to hear what large numbers of people are saying. We’re not a minority of whiners opposed to change. We’re trying to convince you not to do something to WordPress that has a significant chance of killing it, and a 100% chance of harming it.

That’s why I say: “Make it go away”. Please listen.