• From the point of view of a developer and having used WordPress since the days of 1.X, Gutenberg set out to accomplish a lot but so far it has delivered very little.

    I familiarised myself with it in the early stages of development and attempted to use it in multiple projects when the plugin was in various stages of development. I always ended up ditching it after countless of wasted hours or days.

    In its current state I would consider it a step down from the Classic Editor and find very little reason for it to be the default in WordPress 5.0+. It is more confusing to the average website owner than the Classic Editor would be, and currently a lot less flexible than most Page Builder plugins on the market.

    Edit 22nd Jan, 2019:
    Attempted to use it in the development of a new website, WP 5.0.3. Constant “Update failed” messages during attempted auto-saving; manual updating not functional multiple times; several glitches when using the native Heading block with nested strong/em tags and not reverting back to the visual editor after attempting to use the code editor to fix it; layout-wise still highly random and janky to use even with the Enhanced Blocks plugin. My score remains at 1/5 for now.

    • This topic was modified 5 years, 10 months ago by Edward M.. Reason: Clarity
    • This topic was modified 5 years, 10 months ago by Edward M.. Reason: 22 Jan case study
Viewing 1 replies (of 1 total)
  • Thread Starter Edward M.

    (@emedara)

    Update 3rd Feb, 2019:
    Attempted to use Gutenberg on a new website again. All that was required was a 3-column layout with a captioned image in each. Simple enough, right?

    The default dimensions with which an uploaded image is placed in Gutenberg are absolute, and based on the column width inside the editor. That would make the image tiny in almost any real-world application (save for very narrow layouts). You can change them to a percentage, but there’s a glaring issue pictured here: https://i.imgur.com/sR5NwPF.jpg

    • Set the image width to 100% and it breaks the layout within Gutenberg. However, the achieves the desired effect in the front-end: the image occupies 100% of the column width. However, as the screenshot above illustrates, it’s impossible to use Gutenberg that way as it overlaps with its UI and all adjacent blocks.
    • Set the image to 33% (or anything else) and, once again, everything is going to be too small in the front-end.

    I’m not going to waste any more time trying to use it in this project, but I’ll try to document further attempts on other websites.

    • This reply was modified 5 years, 10 months ago by Edward M..
Viewing 1 replies (of 1 total)
  • The topic ‘A disappointment’ is closed to new replies.