Support » Plugin: Gutenberg » What we need, but not how we need it

  • dains

    (@dains)


    I see what you’re trying to do, but it’s backwards in presentation. Block content is great for content development and reusable blocks are great for repeated development, BUT we first need to focus on getting the content written. THEN we can mess around with the blocks, getting everything all set in place and tuned to our satisfaction.

    I think you could adapt this to your block model by letting us develop the text content in the normal editor, adding imagery etc. with blocks, then converting the text content we select to blocks while we’re working with it and letting us have the option to save the block for reuse.

    But please god don’t hide the normal editing tools everyone is used to, and make us select a block type every time! That’s horrible for our productivity. Nobody needs complexity of use when we’re trying to focus on creating content.

    Edit – also, what’s with automatically selecting 5 stars for the review? How many people didn’t see that, generating false 5-star reviews for plugins?

    • This topic was modified 8 months ago by  dains.
  • The topic ‘What we need, but not how we need it’ is closed to new replies.