1. richard Ginn

    Basic boring corporate layout patterns. We all need it.


  2. Eniola Samuel

    We’ve all been waiting for WordPress version 5.5 and here it is, I’ve seen much improvement and I can say I’m impressed.


  3. Lucy Ng

    In new version, Gutenberg has a lot of new features that users need. Now I can use it to build my own homepage, landing page, … more easily.


  4. Li-An

    Just another brick in the (commercial) Wall.


  5. Milan Petrovic

    Block patterns are the only positive thing in block editor in WordPress 5.5. New block editor has gone down hill in term of usabilty and intuitive use, with many useful features gone or made worse, and it is easily the worst edition of block editor since it was first added into core. And for me, editor performance is clearly worse then with WordPress 5.4.

    Each previous major WordPress version, improved on block editor, and all that is gone with new one.

    Overall great WordPress 5.5 now includes the worst version of block editor to date.


    • Andrew Nisbet

      I totally agree. I am now clicking all over the place trying to find a block’s menu for alignment eg on buttons, as there is no visual cue. Columns are the same.

      Tables still cannot be edited for font or point size, it is hard to identify which blocks are provided by which plugin, I have to use three different ones to replace plugins that no longer work because some blocks still do not work correctly.
      I have a plugin that calculates values but put two shortcodes in adjacent cells in a table and it plays havoc with bits of table code appearing all over the place. Why is 5.5 so different from 5.4? Where is the migration path?

      I have used WP for over ten years but my less techy users are pulling their hair out with all the editor changes. I am seriously considering moving to another CMS. Looks like WordPress is going to lose its premier position, see w3c decision. I fear its had its day.


  6. Dr Gallagher

    “One of the promises of the block system is that it allows users to switch between themes and maintain their content.”

    Didn’t we hear that about Custom Post Types?


    • Justin Tadlock

      Because a CPT can literally be any type of content/data, there could not truly be a guarantee of that, at least in terms of how the average end-user would see it. For example, if nav menus were a plugin instead of baked into core, you’d need massive theme adoption for them to work because the nav menu taxonomy and nav menu item post type are completely different from your typical posts/pages.

      If the CPT worked basically like a post or page, switching themes should typically be no problem.

      You’ll never technically lose your CPT content when switching themes. The conversation is just a bit more nuanced than that though.


Comments are closed.

%d bloggers like this: