• I thought I’d give this a chance by using it on new sites. It’s completely unintuitive compared to things that users are used to – like Microsoft Word or Google Docs. Most people using blogs and WordPress sites are not web designers. Even adding and moving a right aligned image ends up with a confusing jumble of blocks. Every new paragraph is a separate block, which also makes no sense. I can have three paragraphs that are connected in sequence and always will be – I want them to be in one block as every other block editor I’ve used would do.

    By all means, launch Gutenberg and promote it as a “featured” plugin, but to make it the default when most people are looking for a straightforward editing experience is counter to the ease of use that WP has been famous for. I’ve used other block editors extensively when I’ve needed complex layouts so I’m not against them. The problem is this is imposed on every page by default and isn’t very good.

    It also creates a training issue for the dozens of existing WP site users we support – unless we turn it off, of course.

    • This topic was modified 7 years, 9 months ago by davidrsim.
    • This topic was modified 6 years, 9 months ago by davidrsim.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Yes, we can install the “classic editor” plugin on every site, but I don’t know why yet another plugin is necessary when it could be a simple settings option to enable the wonderful new editor.

    WordPress has a long standing philosophy of “decisions not options”. I’m not supporting this philosophy – just clarifying that it exists. It is though a significant factor in how WordPress looks & feel today.

    In this case the Gutenberg team is following that pattern. The Gutenberg editor will become the default editor in WP 5.0 but they will also provide a range of relatively easy to use ways to opt-out.

    It’s very similar to the approach used when automatic minor updates where introduced. There is still a range of ways to opt out of automatic minor updates via code or plugins but the default is automatic minor updates on.

    Thread Starter davidrsim

    (@davidrsim)

    Thanks for the clarification. I’m a very long term WP user – I can’t remember a change that has resulted in such wholesale breakages of existing pages / themes / workflows. The appeal of WP is its simplicity.

    Given the plethora of page builders on the market already, this should be an exception to their rule or, even better, released as a featured plugin. They don’t force Jetpack into core; they shouldn’t force this either.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Training Issue’ is closed to new replies.