1. Steve

    As a designer/developer I’ve embraced Gutenberg and use it for all my new projects. I’ve already found Gutenberg to be quite limiting when it comes to creating unique and compelling designs. A lot of my design focus has switched to the themes header/footer layouts.

    With the introduction of FSE I feel like those limitations are only going to be increased. Maybe I don’t fully understand it yet, but I’m not even sure how I’m supposed to create a standard menu on desktop, which then switches to a ‘hamburger’ toggle with a popout/overlay animation on mobile.

    I hope I’m proven wrong.


  2. Binil P

    People might switch from wordpress to some other platform if they don’t do this properly.


  3. Peter Shaw

    The elephant in the room is that WordPress has large architectural problems and missing backend apis.

    The problem is these issues are not being tackled at all (or even acknowledged) atm. As sadly the community is obsessed by Gutenberg. Which for all its coolness will only ever be a presentational tool.


  4. Federica

    As a developer I love to experiment new things and I did so with Gutenberg and the whole block system. But when it comes to clients’ projects sometimes the time frame is tight and a “real” how-to guide would have been very handy: in my opinion that was missing for custom blocks apart from a few (not so useful for me) “hello world” examples. Therefore, since Gutenberg appeared on the scene a lot of my time was used in finding solutions with a trial-and-error approach or trying to understand the whole thing by reading (a ton of) code. I don’t think it was a waste of time, on the contrary, I would have found it useful if only I had the time to enjoy it!
    That said, I really hope that for FSE there will be also a good guide for developers to get the most out of it while enjoying the learning process.


  5. Francesca

    Hello, folx! Thank you for picking up the planning roundup post. Quick clarification – that I also added to the post – Full Site Editing is not THE scope of the release. Bug scrubs have started on December 15, and once everyone is back from a much-deserved winter break, there might be other items popping into the radar. Full Site Editing is a whole Gutenberg phase, so naturally, it will span over multiple releases.
    As per Nav Menus and Widgets being completed for 5.7, I couldn’t find any confirmation of this timeline. Can you point me to the source? I might have missed something!


  6. Andrew Wright

    I manage a large corporate network of WordPress sites. One of the strengths of WordPress now is the ability for us to lock down the design while allowing the authors to easily add content. We can (relatively) easily reuse, migrate and repurporse content because we don’t use page builders.

    I realise that this isn’t the use case for the vast number of small sites out there, but the corporate and government world is subject to much stronger restrictions.

    I would hate to see that capability lost from core WordPress.


    • Justin Tadlock

      The roles and capabilities system is not going anywhere, which is what you’d rely on to do that today. What you should see is an even stronger system, which supports helpful developer tools like template locking (available on the post-type level right now).


    • Felix

      Keeping design & content strictly separated has been the purpose of every CMS since the early days. This basic principle ensures the longevity and transportability of our content. Every blog / magazine owner relies on it. WordPress gave us a good 15+ years of this reliability. I hope as well as you that this does not get sacrificed for the „democratizing design“ agenda. Happy holidays!


  7. WolfBern

    This is wat I use Divi (WP plugin) for, even reading this article, I dont think it will be a sufficient replacement for it…


  8. Val

    I’d love working with Gutenberg, but I find it quite hard to work with at this point. The WP team should make it work more like the site builders and create a better UI.


  9. Gary Taylor

    I get that theme developers should be getting ready for the change; but what about us hobbyists? What we (I, certainly) need is a list of equivalences and functions and calls (a bit like the list I did of blocks and styles the other month), so that we can see how our hand-built themes can be converted into block-based themes. We don’t all farm that aspect of our sites out ;-)


    • will

      Agreed; how to do ‘X’ in Gutenberg or FSE isn’t clear in many cases in the documentation or I’ve found more often, there isn’t an answer just yet.

      I asked specifically how themes should migrate to the FSE this summer – https://github.com/WordPress/gutenberg/issues/24313 – and the answer is not yet known.

      Generally, there’s been more focus on making FSE themes from scratch.


  10. Art

    Well here’s my two cents. As developer I took it upon myself to switch for every editor on to Gutenberg because let’s face it, it’s soon to be native to WordPress, but as the editor is in its infancy state, it’s got room to grow. This is where ACF Pro comes in for me: I am able to take any design at any complexity and develop custom blocks built for Gutenberg and my users can build their own pages with my blocks. This helps keep designs nearly perfect based on any XD Design that is put in front of me.

    If the new update will ease this projects that is great. But I don’t see that happening based on anything custom.

    In 2021, ACF Pro! This is “still” the ways


    • Niki

      Are you locking templates down, say for example, the homepage?


      • Art

        Only static components that do not require editing. Take for example the Header / Footer of a page, those never change, hence, require no standard user adjustability. The context is changeable but the component itself, isn’t.

        I used to work directly with Flexible Content within ACF Pro but now transitioned to ACF Custom Blocks due to their native nature of integration on to WP. I would like to see something native from WP that either replaces this process or aids it.


  11. Tim Toomey

    Bring it on.

    I’m only worried about the abandonment of the customizer, widgets, and menus because those are integral to “universal” theme elements–even in our themes that are all block-based. Keeping our themes from the repo in compliance with all the theme review requirements for blocks, sample content, etc., is a lot of work–especially with markup changes that happen with each release to the block editor.

    That said, the end-users are the ones who benefit most from the changes to how WordPress content is managed, and those are mostly my clients, who have been VERY happy with all the visual editing tools and templating abilities that come from the block editor. Seeing their eyes light up during training on the block editor and seeing them update their sites more often with more content that’s better designed and more engaging is what I signed up for, and it’s starting to really pay off for me, at least.

    I’m definitely worried about the workload but excited about the possibility of winning over more potential theme users who currently rely on Elementor or other bloated tools.



  12. Chris McCoy

    i feel non techy users have had trouble using gutenberg vs classic editor, a good % of them had to enable to classic, one client didnt know classic editor existed, and planned on ditching the wordpress platform completely because of gutenberg.

    myself i prefer classic as well, i feel i can write up a post much faster using classic editor, hopefully they keep classic up to date and working through 5.7


  13. Michael Weichert

    Any github issue references that talk about deprecating the Customizer? I’d like to read more about this is the first I’ve heard about that.



  14. Lucy Ng

    I tested some famous Gutenberg theme but they haven’t supported this feature yet. Perhaps it takes time for them. For me, the tt1-blocks theme is a good starter theme.


Comments are closed.

%d bloggers like this: