Support » Plugin: Gutenberg » A Visit from St. Gutenberg

  • Web242

    (@dividendninja)


    A Visit from St. Gutenberg

    ‘Twas the night before 5.0, when all through the house
    Not a blogger was stirring, not even a mouse;
    The WordPress core was updated with care,
    In hopes that St. Gutenberg soon would be there;

    Matt and his team were nestled all snug in their beds;
    While visions of WordPress danced in their heads;
    And Matt in his ‘kerchief, and team in their cap,
    Had just settled their brains for a long Summers’s nap,

    When out of Automatic there arose such a clatter,
    Matt rose from his bed to see what was the matter.
    Away to his computer he flew like a flash,
    Logged into WordPress and threw up the Dash.

    The moon on the edge of the new-fallen code,
    Gave a lustre of dismay to login once told,
    When what to his wondering eyes did not appear,
    But all his posts and pages did completely disappear,

    With little old MCE editor so lively and quick,
    Matt knew in a moment it was a St. Gutenberg trick.

    More rapid than eagles his programmers they came,
    And Matt whistled, and shouted, and called them by name:

    “Now, Meta! now, Shortcode! now Custom Post and now Plugin!
    Oh, Pages! oh, Posts! all Goner and now not even Login!
    To the top of the porch! to the top of the wall!
    Now it’s all gone! gone away! gone away all!”

    As code that before WordPress would fly,
    Now they met with an obstacle, Saint Gutenberg, oh why?

    So up to the remote office the programmers they flew
    With a sleigh full of revisions, and Mullenweg too—

    And then, in a twinkling, Matt heard on the web
    That all the bloggers and designers had fled.

    As Matt drew in his head, and was turning around,
    Into the room St. Gutenberg came with a bound.
    He was dressed in Armani, from his head to his foot,
    And his clothes were as sleek with a new editor to boot;

    A bundle of blocks he had flung on his back,
    And he looked like a coder just opening his pack.

    His eyes—how they twinkled! his dimples, how merry!
    “Who needs MCE, when we have blocks and so many?”

    His droll little mouth was drawn up like a bow,
    And he began to recode WordPress, like no one could know;

    A wink of his eye and a twist of his head,
    Soon gave Matt to know he had so much to dread;

    Gutenberg spoke not a word, but went straight to his work,
    He pulled apart WordPress; then turned with a jerk,
    And laying his editor aside for all to adore,
    And giving a nod, he pronounced “Gutenberg is core!”

    He sprang to his car, to his team gave a whistle,
    And away they all drove like the launch of a missile.

    But I heard him exclaim, ere he drove out of sight—
    “WordPress is gone, and to all Gutenberg good night!”

    • This topic was modified 1 month, 4 weeks ago by  Web242.
    • This topic was modified 1 month, 4 weeks ago by  Web242.
    • This topic was modified 1 month, 4 weeks ago by  Web242.
    • This topic was modified 1 month, 4 weeks ago by  Web242.
    • This topic was modified 1 month, 4 weeks ago by  Web242.
    • This topic was modified 1 month, 3 weeks ago by  Web242.
Viewing 13 replies - 1 through 13 (of 13 total)
  • One of the greatest comments of all time!!

    Your comment is great!

    Plugin Author Joen Asmussen

    (@joen)

    As much as I’m sorry you had a bad experience testing this plugin, and would invite you to give specific feedback and try it again in a later version, I will also admit, this is one of the better one-star reviews.

    It’s so very hard to move mountains. And in this case, we’re moving mountains. At some point, you have to grab a shovel and start. Moving a mountain with a shovel takes a while. In four months we’ve moved a fair bit, but evidently there’s a lot more still to move. One stars are hard because you put yourself out there, all your work laid bare, and it can feel like the whole internet is against you. Do you spend time responding that “No, Gutenberg won’t get merged into core unless it’s ready” or “there are many ways to roll Gutenberg out, including letting you opt in to it” or even direct towards our FAQ or design docs (https://github.com/WordPress/gutenberg/blob/master/docs/faq.md and
    https://github.com/WordPress/gutenberg/blob/master/docs/design.md) which answers some of the more common concerns? Or do you spend that time fixing the 440 open issues, hoping that we’ll be ready in time?

    I love WordPress, I’ve loved it since version 1.2, and I just want to give back to it after all these years. It’s hard, hard work, and this particular one star really gave me a chuckle on a dark day.

    That said, I’d really love for you to try 0.8 coming out this week, and I’d appreciate specific action items — prose form or otherwise — for how we can improve in 0.9.

    @joen We don’t want gutenberg in core, stay it in plugin!

    Plugin Author Joen Asmussen

    (@joen)

    @thierrypigot I would really appreciate if you could expand on _why_ you so dislike Gutenberg.

    I’m very sorry you haven’t had a good experience testing the plugin. I’d also like to clarify that it’s not up to me whether it reaches core or not. I can only do the best work I can, try to build the very best editor.

    I don’t understand why core team is focused on this extend. We still haven’t native SEO fields, Accents in attachment file names are still there (5 years ticket https://core.trac.wordpress.org/ticket/22363 ) …
    Gutenberg give a nice UI, but you have 5 years late in front of elementor, beaver builder, visual composer ….

    What make WordPress is, is the simplicity and the fact of being able to do everything that one wishes. Why compromise the core and this philosophy?

    If you want to have this builder on WordPress.com, put it in jetpack!

    It’s not a plugin mistake,but a political and philosophy question.

    I have downloaded, used and build extends for gutenberg. I am involved in builders ecosystem, and i don’t want to be imposed a builder

    Plugin Author Joen Asmussen

    (@joen)

    Really appreciate your time to elaborate, thank you.

    I don’t understand why core team is focused on this extend. We still haven’t native SEO fields, Accents in attachment file names are still there (5 years ticket https://core.trac.wordpress.org/ticket/22363 )

    To clarify, the Gutenberg team is not the core team. We’re a small band of people crazy enough to take on this task, knowing how difficult it would be. While we’ve had a whole slew of contributions from the community (just look at this list), there’s still only six or seven of us doing the bulk of the work. We’ve made a bunch of progress in a short time, but we know that there’s still a long way to go.

    What make WordPress is, is the simplicity and the fact of being able to do everything that one wishes. Why compromise the core and this philosophy?

    I agree. This is exactly why we are building Gutenberg. It is built on the idea that we can take the flexibility and strength that you get with shortcodes, custom HTML, theme styles, and expand it drastically, put it front and center, and make the UI much easier. Take the Cover Image, for example, it expands quite a bit the kind of layouts you’re able to do with just a simple block. Here’s a video:

    Right now we are focused on building this _editor_, and working hard to get the blessing that we might be considered for merge into WordPress. This is not a done deal.

    If we get that blessing, there are many ways a merge can happen, probably including ways that’ll let you keep using the old editor. See some of the ideas here.

    • This reply was modified 1 month, 1 week ago by  Joen Asmussen.
    Plugin Author Joen Asmussen

    (@joen)

    Appreciate your time to elaborate, thank you.

    I don’t understand why core team is focused on this extend. We still haven’t native SEO fields, Accents in attachment file names are still there (5 years ticket https://core.trac.wordpress.org/ticket/22363 )

    To clarify, the Gutenberg team is not the core team. We’re a small band of people crazy enough to take on this task, knowing how difficult it would be. While we’ve had a whole slew of contributions from the community (just look at this list), there’s still only six or seven of us doing the bulk of the work. We’ve made a bunch of progress in a short time, but we know that there’s still a long way to go.

    What make WordPress is, is the simplicity and the fact of being able to do everything that one wishes. Why compromise the core and this philosophy?

    I agree. This is exactly why we are building Gutenberg. It is built on the idea that we can take the flexibility and strength that you get with shortcodes, custom HTML, theme styles, and expand it drastically, put it front and center, and make the UI much easier. Take the Cover Image, for example, it expands quite a bit the kind of layouts you’re able to do with just a simple block. Here’s a video:

    Right now we are focused on building this _editor_, and working hard to get the blessing that we might be considered for merge into WordPress. This is not a done deal.

    If we get that blessing, there are many ways a merge can happen, probably including ways that’ll let you keep using the old editor. See some of the ideas here.

    Web242

    (@dividendninja)

    Joen,
    My review stays 1-star. I actually agree with all of Thierry’s points:

    • What make WordPress is, is the simplicity and the fact of being able to do everything that one wishes. Why compromise the core and this philosophy?
    • If you want to have this builder on WordPress.com, put it in jetpack!
    • It’s not a plugin mistake,but a political and philosophy question.

    I agree with those points. I would like to see Gutenberg as an external plugin vs. core. Jetpack would be an ideal integration for Gutenburg – good idea!

    It seems Matt and team are pushing quickly on this, over a reason that was decided at Automatic. And it is a philosophical reason – even to the extent of ignoring backwards compatibility. This is not good.

    The real question in all of this is WHY?

    I’m not opposed to change or improvements – I think change can be a good thing if done properly.

    I don’t want to be negative like some other reviewers here, nor diminish the efforts of your hard work. But my initial view of Gutenberg is that it is terrible. These points have already been covered many times over:

    (1) Plugins disappeared on the back end, and could not be integrated.
    (2) Disliked that buttons disappeared while editing and have to go find them.
    (3) Takes longer to do anything (and I mean anything). It’s not intuitive.
    (4) Custom posts, meta, and shortcodes are critical (not-optional). I believe shortcodes have been covered. But custom post types and meta are critical.
    (5) Cut and paste didn’t work, but I think you resolved that.
    (6) MCE is easy and quick to use. Unlike Divi or Visual Composer etc. Visual editors should always be optional – not core. At this time Gutenberg resembles a visual editor.
    (7) Please understand that many people use WordPress beyond simple blogging, they need some guarantee of backwards compatibility.

    Please listen to the community.

    Cheers

    Web242

    (@dividendninja)

    Joen,
    I’m glad “A Visit from Saint Gutenberg” gave you a good chuckle!

    I feel strongly the MCE Editor can remain core, with Gutenberg as an advanced plugin (or option of some type).

    Why not keep both? and make everyone happy. This would give you the time to test and refine. If you are reinventing the wheel – it won’t be easy. People like a round wheel for a reason. 😉

    From what i read, when Gutenberg will be ready and in the core, there will be NO way to disable it / remove it.

    Guys at WordPress or whoever is in charge of the project. JUST DON’T DO IT.

    If you can, keep it optional. Otherwise people will move (should we start already looking for alternatives ?).

    I agree with @dividendninja
    In my mind, a plugin should be part of the core when everyone install that plugin by default on most of the WordPress around the world, and even then, it should be check if it is really better as part of the core than as a plugin.
    But if that is not happening, I do not see the reason to do that, unless this is not something the community is deciding but Automattic is, and if that is the case, that is a bigger issue.

    • This reply was modified 3 weeks, 6 days ago by  angelfplaza.
    QuantumCloud

    (@quantumcloud)

    Greatest poem of all time!

    “WordPress is gone, and to all Gutenberg good night!”

Viewing 13 replies - 1 through 13 (of 13 total)
  • You must be logged in to reply to this review.