Support » Plugin: Gutenberg » Gutenberg feedback from a Full Stack Developer

  • Hi,

    I admire the hard work you put in with the goal to improve WordPress. I’m a full stack developer and linux admin with over 10 years of experience. I had both hands deep into a lot of new technology from the get go.

    Developing for Gutenberg involves an amount of overhead that is unknown to me. How am I supposed to develop complex client’s projects all by myself with this? Have you ever thought about that situation?

    We’re the small devs, hard working like you do, that made WordPress successful. I’ve been there in the beginning when it wasn’t clear that WordPress is the horse to put you money on. I’ve convinced dozens of customers that WordPress is the solution they need, provided clean and fast custom websites that are easy to operate and maintain, at the same time being affordable to SMIs.

    How am I supposed to do the same with Gutenberg?

Viewing 9 replies - 1 through 9 (of 9 total)
  • JS

    (@jsylvia90)

    Totally agree!!! I have posted the same points. I have been designing websites since before Google even existed and moved to WordPress by their persuasion of its content management capabilities. Plus accessibility for visually impaired is completely lacking. My solution is to slap in the Classic Editor plugin on any of my sites that the client is maintaining themselves. Gutenberg should be the plugin not the editor.

    Yep. If they kept Gutenberg as a plugin nobody would have ever cared. But this “in your face” approach was prone to get feedback like mine and thousands of others.

    But now I’m really worried about the future of WordPress. What’s on the roadmap? Move to Node.JS / React entirely, because “it’s better for you peasants, you clueless folks”??

    See, it’s not only the editor, it’s the entire development and therewith my own future. And I’ve seen a lot of these “hipster” frameworks come and go, Django, RoR, younameit. All “so much better, build a whole CMS in 10 minutes from scratch”, remember? Now look in the job listings, still any Django or Rails jobs? Not in my Country. These things are awesome for big companies that develop their own stuff in big teams. But no good for average-Joe haircutter that needs a good custom website built for less than a $500.

    On top, I’m not anti-Node.js per se. I – not like that I’m maybe forced to use it in the future. From my admin point-of-view: I like what we established, a fast and lean Linux with Reverse Proxy, Apache2 and a ton of optimizations, also for the “not so optimized” PHP code – a lot to learn for me to understand and maintain, but now I can configure everything like the client wishes. Toss it all for all-in-wonder Node.JS webserver? Not gonna happen, like ever. LAMP is a world-wide established, super-stable and standardized platform every Linux admin can maintain. Node.JS is the cool new kid in town right now and maybe forgotten tomorrow.

    2cents as usual.

    Interesting thread… My favourite quote from the Gutenberg team follows:

    Ultimately, it will open new opportunities for plugin and theme developers to better serve users through a more engaging and visual experience that takes advantage of a toolset supported by core.

    Ultimately…

    ultimately
    /ˈʌltɪmətli/Submit
    adverb
    finally; in the end.
    “the largest firms may ultimately become unstoppable”
    synonyms: eventually, in the end, in the long run, at length, finally, sooner or later, in time, in the fullness of time, after some time, in the final analysis, when all is said and done, one day, some day, sometime, at last, at long last; …

    @djcowan Can you explain some more how this all went down? I obviously didn’t realise what Project Gutenberg is until it’s too late now, cause I was envolved in bigger project and same time study for my Linux Engineer exam.

    Node.js.. (c) Google Inc.
    React.js.. (c) Facebook Inc.

    Suddenly unstoppable in the most successful CMS. How did it happen? Nobody cared? Cannot believe it.

    • This reply was modified 9 months, 1 week ago by  bortran.

    These foundational elements will pave the way for stages two and three, planned for the next year, to go beyond the post into page templates and ultimately, full site customization.

    https://wordpress.org/plugins/gutenberg/

    […]So if you’ve written a plugin in PHP and want to update it for compatibility with Gutenberg, then it’s not going to be a simple task.

    https://premium.wpmudev.org/blog/future-of-wordpress/

    So I have a full year to rewrite each and every custom website and plugin I ever made? How on earth am I supposed to do that? With a new API that isn’t even developed yet? Who made this genious plan? Customers gonna sue the crap out of me once my sites are no longer supported.

    Best case: Schism – there’s gonna be a WordNode and a FreePress GNU version.

    Can I explain it? No, I don’t think so. However, I do know that pain is inevitable… but suffering—apparently—is optional.
    Wordpress was never developed with the intention being an enterprise CMS for large corporations… this was a risk that we all took knowingly.
    Wordpress has always been clear about its goals and its intent.
    We loved using WordPress because of its simplicity and consistency. We confidently told our clients–if you can format an email–you can manage a WordPress site. We wanted our clients to be in control of and take ownership of their own content.
    We have been “exclusively” developing “self-managed” WordPress sites for ten or so years too. That’s a lot of code to refactor, rewrite and redevelop.
    Retraining our corporate clients on how to use Gutenberg is simply not possible; not logistically, not physically and not emotionally…
    We’ve CLI’d the default editor plugin into our stable of sites and will look to develop a quarantine system and pin the now “outdated” sites against updates.
    This is a massive security issue and risk for clients on our shared hosting servers… but que sera… only time will tell… [end ramble]
    [restart ramble] My greatest concern is that Gutenberg will remove or break the separation that should always exist between content and the display… we set early rules and procedures into place to protect the raw content. We have never and will never add HTML or any mark up into our CMS content editors… we are just hoping that this is something we can continue to do moving on.

    • This reply was modified 9 months, 1 week ago by  dj.cowan.
    • This reply was modified 9 months, 1 week ago by  dj.cowan.

    @djcowan 100% what you wrote.

    Although I never expected WordPress to be an enterprise CMS, that’s a bit extreme end of the spectrum. My clients are small to medium biz and I’m the one providing a better product than the usual “here’s your visual builder theme that takes 3 seconds to load, deal with it”. All custom made, lean, fast. I sense the people with “enterprise” in mind may be found in dev-team Gutenberg.

    I had exactly the same thoughts as you after I posted my last reply: 10 years of deployed websites, how could I possibly rewrite these in a year? Same with the training: I’m doing exactly the same thing, it’s part of my product.

    Security risk of outdated sites will fall back on us, hard. We’ll have to deal with it, the clients only make the call. Not an option for me.

    I’m not even sure where to go with the sites I’m making right now. Add a “best before 2021” label?

    I think the WordPress devs have their heart in the right place but didn’t think their descission through on all ends.

    My xmas wish: I hope some people will see the issue as we’re seeing it and will continue to support the WordPress / Classic Editor (and what maybe become “classic” anytime soon) on their own basis. I’m willing to pay for it, but still, branching usually isn’t good.

    Classic editor will die eventually because more and more devs have to keep plugins and themes compatible with gutenberg as now it’s in core.

    WordPress end users hate Gutenberg, Developers don’t even like it. Everyone is saying from start that this is bad move by WP but why they still included it in core? I think even when 1% of people will use it WordPress will still keep Guternberg in core. WordPress team people are acting like Corporate.

    What I really find fishy is the fact that core team members started to contact plugin devs to tell them they should make their plugins compatible with Gutenberg. If you search around you’ll find what I mean.

    I find their acting strange as well. They cannot ignore the whole community. Reading some of their answers to the massive downvote of Gutenberg tells me they weren’t prepared for this to happen. We shouldn’t stop to speak up. Do not just install Classic Editor and call it a day, take action. Write to them. Write your opinion here. Post about on your blog.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Gutenberg feedback from a Full Stack Developer’ is closed to new replies.