Love it, but still I don’t understand

  • Resolved LZL0

    (@lchief)


    6 years, 6 months ago

    Firstly, I should mention that I really love this plugin and the work which is being undertaken on Github and how quickly the plugin is being developed.
    However, I see multiple issues with this plugin being added to the core.
    I really hope that you guys, including Matt, did proper research into what people wanted in the first place.
    I want to keep this short, but also informative.
    My issues with Gutenberg:
    1, If you don’t care about small bloggers and websites, are you sure big corporations, like Coca-Cola, The New York Times and other want this plugin included in the WordPress core?
    2, If you are putting this into the core, are you confident enough that Gutenberg won’t impact release schedules beyond 5.0?
    Let me elaborate, you guys mentioned that you intend to include Gutenberg into the core ‘when it is ready’, most likely to be included in version 5.0, however minor bugs, future browser updates causing incompatibility and other potential issues along the way – in my own opinion – can and will make very hard to maintain the codebase of Gutenberg within the codebase of the WordPress core to resolve said issues. Upon resolving those issues everybody will have to update WordPress again, regardless if Gutenberg is switched off or not. Gutenberg, being included in the WordPress core may adversely affect the number of minor updates in a single year.

    You should really explore other opportunities regarding Gutenberg and the WordPress core. I see the reasons why you would like to include it, but including it directly into the WordPress core is just foolish.

    In order to keep Gutenberg relevant and bug-free you could adopt a new approach to Gutenberg.
    You could include Gutenberg as a ‘core plugin.’ A core plugin would be included in the default WordPress package, could be updated at any time through the plugins page, while it could not be deactivated through the WordPress plugins page. Site admins would have the means to delete it and remove its code, satisfying their cravings of not being forced to have Gutenberg.
    Making Gutenberg a ‘core plugin’ as described above is also going to support its ongoing development, making updating Gutenberg in the future with improvements and bug fixes a breeze.

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

  • I couldn’t agree more, nice to see a common sense approach to this issue.

    I agree as well. If we have survived sa loooooong without any progress in the editor matter, we can really make it good this time. That means development and listen, feedback and development again.

    As an Agile process until all aspects has been considered.

    The customizer should have become a plugin instead. When you dont need it, it loads a lot of shit anyway.

    WordPress has to go forward to scale down, not scale up with “pretty” things.

    Moderator Marius L. J.

    (@clorith)

    Hi,

    So we don’t really care if big corporations want Gutenberg or not, our work is for the masses. We want to provide a good editing experience for the majority of users, whomever they may be.

    The reason why we are not going to make it as a plugin is that once it’s optional, theme and plugin developers will just ignore it. By guaranteeing that it will be part of WordPress we will see plugins and themes utilize it. We want, nay need, them to also use Gutenberg. This is how we can provide a good experience for the end user, when they use the tools we give them. Just look at how confusing and hard to use shortcodes are, they tried to solve a problem, dynamic content, but what will they produce? You won’t know till you save and preview a page. Here you get a block that instantly gives you an idea of what is going on, and you are more confident in your content that way. And I believe plugins and themes will have happier users as well from this, meaning wins all around ??

    > The reason why we are not going to make it as a plugin is that once it’s optional, theme and plugin developers will just ignore it.

    This argument doesn’t stack up. If Gutenberg is as good as you think it is, even if it’s an optional plugin (let alone the ‘core plugin’ suggestion in the OP), it will be adopted by huge numbers of users. If that happens, theme and plugin developers won’t be able to ignore it and stay relevant.

    Your argument only works if you believe Gutenberg would be rejected en masse in a ‘free market’ scenario. Why would you think that?

    Moderator Marius L. J.

    (@clorith)

    This is a 3+ months old topic, if you wish to make a statement about Gutenberg, please create your own topic or review. I am closing this thread to avoid bothering the original participants with email notifications.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Love it, but still I don’t understand’ is closed to new replies.