This should not be in core yet

  • Peter Hardy-vanDoorn

    (@petervandoorn)


    6 years, 9 months ago

    As a developer of websites for clients, I have a huge concern over the functionality being added here. For blog posters, there’s no doubt that Gutenberg will be a boon, but for the websites that I develop, it will be hugely detrimental to have my clients adding all sorts of layout options to areas of the page that, in order to remain consistent to the design and functionality which I have developed for them, shouldn’t have.

    If the various components of Gutenberg can be managed by me then it won’t be a problem – I’m thinking to have a filter or action that I can use to turn off, for example, the full-width content blocks, or multi-column blocks. Even better would be to disable the whole thing and revert back to the simple text editor. At the moment, I’m not a fan!

    • This topic was modified 5 years, 8 months ago by Peter Hardy-vanDoorn. Reason: Still not good enough for core
Viewing 1 replies (of 1 total)
  • Plugin Author Tammie Lister

    (@karmatosed)

    6 years, 8 months ago

    @petervandoorn one thing worth noting is in some shape or form, you will be able to ‘turn off’ Gutenberg. The form of that isn’t set yet. As you say, on a code level you may even do this yourself. The experience though is going to be what the feedback makes it, so I would encourage you to keep reviewing and keep giving feedback. Whatever shape that feedback comes in, it all matters and helps make Gutenberg the best project it can be.

Viewing 1 replies (of 1 total)
  • The topic ‘This should not be in core yet’ is closed to new replies.