• I’m sure Gutenberg is the way to go, but there is still a long way to go. For users who have used the old editor, this will be a difficult change. Unfortunately, many things are not properly thought out.
    responsive/percentage image width – missing
    image style/class for responsive websites – can only be set manually
    non-breaking space – missing
    custom inline-styles – missing

    Its a lot to do. If the project fails, WordPress will lose against WIX and others.

    I can give the current state only one point.

Viewing 1 replies (of 1 total)
  • I agree change may be difficult for some. I’d like to try to help make it less difficult if I can! I work mainly in testing and I work a lot with the issues posted to https://github.com/WordPress/gutenberg/issues

    There are some open issues for the things you mentioned and I’ll note them here in case that’s helpful.

    responsive/percentage image width – https://github.com/WordPress/gutenberg/issues/8947

    image style/class for responsive websites – could you give me a bit more detail on this one?

    non-breaking space – https://github.com/WordPress/gutenberg/issues/3549

    custom inline-styles – for this, I think you mean adding the style attribute when editing code directly. If you are using that only sometimes, try out the Custom HTML block. If you are using that a lot, you might consider using the classic block.

    Thanks for posting your feedback!

Viewing 1 replies (of 1 total)
  • The topic ‘Good idea, but that’s a long way’ is closed to new replies.