ross
ross

Tried creating a long post on my blog using WordPress Gutenberg on my iPad.

1) It’s just too complicated when all I want is text + images + embeds. I didn’t want blocks. I wanted to just turn it off.

2) They’ve tried hard on mobile/touch devices, but it needs much more work.

|
Embed
Denny
Denny

@ross Is that a Wordpress app or editor mode of some sort? I’ve been using iA Writer to compose and publish. It’s been awhile since I used the app. I’ve used the web interface every so often but not much and didn’t notice anything new the last time.

|
Embed
johnjohnston
johnjohnston

@ross I’ve kicked the Gutenberg tyres a bit & feel it is for folk who make websites as opposed to bloggers. We have a big WordPress multisite in Scottish education. I am worrying about how a lot of folk will react. Especially as we have a fair number of tablet users.

|
Embed
colinwalker
colinwalker

@johnjohnston @ross I agree with that. I quite like it as a native alternative to the visual page builder plugins but it's overkill for normal blogging unless you always want to post NYT style “features” 🤷‍♂️

|
Embed
In reply to
ross
ross

@Denny It's the new editor that will be built into the core WordPress software as of version 5.0. Currently it's a plugin: wordpress.org/plugins/g...

|
Embed
ross
ross

@johnjohnston Yep. And I see what they're trying to do with it: compete with the likes of SquareSpace. But I'm increasingly of the opinion that forcing it on everyone who updates to version 5.0 of WP is a bad idea. It should be optional.

|
Embed
ross
ross

@colinwalker Exactly this. There are use cases. But the specified use case is a small proportion of what WordPress is used for.

|
Embed
colinwalker
colinwalker

@ross @johnjohnston At least we'll have the plugin to disable it should we want but on all the time is not the way to go. At least from my perspective it should stay disabled as I doubt my custom metaboxes will be compatible forcing it to fall back to the normal editor ;)

|
Embed
ross
ross

@colinwalker I'm pretty sure that custom meta boxes will be fine. It's just not been an area of huge attention for the development team yet. But I have faith that they won't not work.

|
Embed
colinwalker
colinwalker

@ross There was an update saying that custom meta boxes should be registered correctly and those that are unsupported force the editor to fallback to default.

|
Embed
ross
ross

@colinwalker It says "It currently only redirects if a meta box declares itself incompatible with Gutenberg"

I read that as, existing meta-boxes will work with GB with no change. You'll be forced to classic editor only if a meta-box explicitly declares incompatibility.

|
Embed
colinwalker
colinwalker

@ross I think there is going to be both explicit declaration and automatic failure based on compatibility once merged into core but I've added the declarations to mine to force it.

|
Embed
johnjohnston
johnjohnston

@colinwalker @ross I am not too worried about my own blogging, I don't use the editor much anyhow. But how to move things for big multisite (Glow Blogs). If we turn off as default, it will lead to a bigger jump for folk later on…

|
Embed