7 Comments

  1. Joseph McMurry
    · Reply

    I think you meant “5.6” instead of “5.1” in “WordPress 5.1 Beta 1 is expected to ship today.”

    Report

  2. Cameron Jones
    · Reply

    I think the best feature of 5.6 is going to be that they didn’t include half baked underdone features to meet an arbitrary deadline. It takes guts.

    Report

    • Lazy Brad
      · Reply

      Still punting those does not leave much in the release at all.

      Even application passwords and the default theme (both of which are great btw) were previously a standalone plugin and theme respectively.

      Report

  3. Matías
    · Reply

    I think you are spot on with your reflection on the struggles between hyper-focus and inter-relations between some of the present work in phase:2. We have projects underway that are both ambitious in scope and have considerable dependencies between each other. In the end, as you well mention, it all needs to come together into a cohesive user experience, which is what matters the most. It’s tricky, for example, to release global styles without many of the pieces from site editing that allows for it to make sense. However, several specific design tools that are rehearsed and stressed through global styles can and are released independently in specific blocks but with less fanfare. (There are several additions to block features in 5.6 in that sense.)

    Ultimately, the balance between getting things out there as soon as possible to gather broad and meaningful feedback, while ensuring we are shipping things as ready as possible, is an ongoing product challenge. I think it’s important, though, to try to release things as soon as possible as the contrast with real usage is always invaluable for the project as a whole.

    I think it’s also worth saying that, while the site editing projects advance little by little together in the plugin, there are many other parts that do make the light of day, large and small, int he major WordPress releases — like Patterns, which was released in the previous major version and includes several improvements already in 5.6, or the block directory integration. The same can be said about the block editor itself, which includes hundreds of substantial improvements from major release to major release.

    Report

  4. Rod Olman
    · Reply

    Any information about how much the API (is there one?) will break before the feature is finally released?

    Report

  5. Ian Pegg
    · Reply

    I’d rather have one new feature that works as opposed to 10 that don’t. We are talking about shipping a release to millions of production sites after all.

    Hats off to the core team for doing the right thing. There are still many bugs and UX issues in Gutenberg post editor that I wouldn’t like to see replicated to widget and menu editing just for the sake of meeting a deadline!

    Report

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: