Support » Plugin: Gutenberg » Different approach and I like it

  • Ok so this plugin is getting an incredible amount of hate, mostly from people that are used to some free page builder that some random company created. And maybe for your daily blog, a “do it yourself framework for people without code knowledge” is great.

    But when talking about customized solutions for clients, this editor is great! It allows developers to write (reusable!) modern React components without heavy and insecure dependencies and easily integrate headless APIs. When structured well, the frontend editing capabilities are very user friendly!
    Talking from personal experience as a developer, explaining to a client how to edit content was never easier. In fact, I didn’t have to explain anything.

    I agree the learning curve is a little crazy and when your definition of web development is a page with 20 plugins and some page template overwritten using style hacks and jQuery scripts, this is a big step. On the other hand it allows lightweight and extendable solutions like never before in WordPress.

    • This topic was modified 1 year, 2 months ago by fvellerts.
Viewing 6 replies - 1 through 6 (of 6 total)
  • You might have a point. However, I maintain 200+ customer sites, and not a single site needs a heavily customized editor. Isn’t it a bit arrogant to say that most negative reviews came from people who “don’t understand why web development exists”?

    @cutu234 Indeed, I wanted to remove that part anyway but wasn’t at work until now. I also don’t understand why Gutenberg had to be implemented everywhere, right away… I just liked the idea of it, you are right it is only great for highly customized backends.

    @fvellerts I would claim myself as a really good react developer, since I’m doing it for several years. The same for WordPress. But honestly working with Gutenberg does not feel like working with React. It starts with these nonsense attributes in order to bridge the save and edit methods. It would be much better too simply use normal state without any abstraction layer and then save it to the database. In this case, we would not need to update everything in 3 places. (attributes, edit, save)

    Then the core is implemented really poor. Look at those components, that’s far away from clean/sustainable react code…

    The whole architecture is just a mess and you never know where to look for what you’re searching. It’s simply not self-explaining and the whole project is super bloated.

    So yeah, I agree there are a lot of bad reviews from non-technical people. But that’s just because the User experience is so poor. This doesn’t mean the development experience is better… It’s not!

    • This reply was modified 1 year, 2 months ago by orlandster.
    • This reply was modified 1 year, 2 months ago by orlandster.
    • This reply was modified 1 year, 2 months ago by Andrew Nevins. Reason: Removed personal remark

    To throw my two cents in – I develop sites professionally, and Gutenberg SLOWS me down. That’t the main issue. Luckily, they made an in house way to turn it off.

    @mrmut It slows down the webpage or your development process? I agree that the React implementation is not the best and it feels really complicated at the start. Now that I have a webpack setup and created a few blocks, new blocks can be created based on the other ones or original WordPress blocks which should speed up the process a lot in the future.

    It slows webpage development. They hidden a lot of features that are necessary for the process of making site. As for the users and their usage of blocks, in my experience it doesn’t go further than adding a post with theme image, or something like that. It is a Q if the WordPress benefits from their blogcentric approach, or only complicates stuff.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Different approach and I like it’ is closed to new replies.