Gutenberg Phase 2 to Update Core Widgets to Blocks, Classic Widget in Development

Gutenberg phase 2 development is underway and one of the first orders of business is porting all existing core widgets to blocks. This task is one of the nine projects that Matt Mullenweg outlined for 2019, along with upgrading the widgets-editing areas in wp-admin/widgets.php and adding support for blocks in the Customizer.

Contributors on phase 2 are also developing a Classic Widget, which would function as a sort of “legacy widget block” for third-party widgets that haven’t yet been converted to blocks. There may be many instances where plugin developers have not updated their widgets for Gutenberg and in these cases their plugins would be unusable in the new interface without the option of a Classic Widget. This block is still in the design stage.

The widgets.php admin page will need to be completely reimagined as part of this process. Mark Uraine, a designer who works at Automattic, created some mockups to kick off the discussion about what this screen might look like.

Widgets as blocks

These mockups are just explorations of where widgets may be headed next, and they do not take into account everything that will be required of this screen.

Nick Halsey, one of the maintainers for WordPress’ Customize component recommended abandoning this screen altogether in favor of showing widget block areas in the Customizer:

The widgets admin screen has a fundamental disconnect with the way that widget areas actually work – with different areas showing in different parts of the screen and potentially on different parts of the site. It will be very difficult to clearly reflect the frontend page structure on this screen in a way that users will be able to understand. Experimenting with contextual approaches to this experience in the customizer offers numerous opportunities for this fundamental problem to be solved. Starting with the visible edit shortcuts that are already in core, revamped widgets could be edited directly on the frontend (of the customize preview) or in an overlay that is more directly related to the display on a particular screen. The ability to navigate to different parts of the site within the customize preview solves a problem that this screen will never be able to address.

Getting blocks to work in the Customizer is also part of phase 2, but conversation on the ticket related to wp-admin/widgets.php indicates the team is not going to abandon this screen just yet.

“While this screen will eventually be deprecated in the future, especially as more of the site is built in Gutenberg, it’s a necessary “baby step” to get us all there together,” Uraine said. “Maybe the best thing is to keep the existing layout, but just allow the use of all blocks within the accordion content areas? This will keep our resources and investment minimal on this particular piece with just a few suggested tweaks to the mockup in the initial post. It will also allow us to move to the Customizer more quickly.”

Gutenberg accessibility contributor Andrea Fercia encouraged contributors to address accessibility before creating visual mockups by designing the information architecture first. He encouraged them to organize the required information and controls while thinking about how someone might navigate them in a linear way.

“The customizer is not fully accessible,” Fercia said. “The admin widgets screen is the only place where persons with accessibility needs have a chance to manage widgets without having to face big accessibility barriers.”

Discussion on the future of the widget management screen continues in the ticket and contributors are looking to get more input during this exploration stage. There’s also a project board where anyone can share a blog post with their own explorations.

Porting widgets to blocks has its own project board if you want to follow along or jump in on an issue. Most of the core blocks are already finished and a handful are still in progress.

Updating the widgets management page and bringing blocks into the Customizer is a major overhaul but will further unify WordPress’ interface for editing and previewing content. Widgets have served WordPress well over the years, making it easy for users to customize their websites without having to know how to code. The feature has also survived many evolutions, eventually making its way into the Customizer five years ago in WordPress 3.9. One of the limitations with widgets is that they can only be used in “widgetized” areas. Transforming widgets into blocks removes that limitation and makes it possible to use widgets in posts and pages as well.

10 Comments


  1. “insert wptavern gutenberg hate comment here”

    But in all seriousness I think this is a huge step forward for WP and the team is doing a great job.

    Report

    Reply

    1. I don’t hate Gutenberg; WordPress and I are friends and GB isn’t going anywhere so I want the best for it.

      That said, I am looking forward to seeing things become more cohesive; I remember being concerned about what a hot mess it all seemed like and then it got so much better. It’s not my kind of rodeo, so I don’t use it, but when I see thoughts like this:

      Gutenberg accessibility contributor Andrea Fercia encouraged contributors to address accessibility before creating visual mockups by designing the information architecture first.

      it makes me think things are in good hands. If you can’t get from A to Z immediately, a thoughtful and iterative process that attempts to transition people without too much confusion sounds like a nice change of pace!

      It’s actually weird. Menu doesn’t look like Widgets doesn’t look like Customizer, but it’s so familiar that I don’t even question it. The opposite; the idea of everything looking like blocks seems confusing at first. But I use a page builder where everything’s done the same way and handle it fine. So I’ll be fine =)

      Report

      Reply

  2. I am curious how the phase 2 (beta) testing will be in general — from what I read/ heard, they want to use the Gutenberg *plugin* again for that.

    This seems rather strange to me: users, and a lot of devs/ agencies already have voted with their feet that they don’t want it and then should install it again. Crazy thought.

    Apart from that I really hope the Widget Block for regular widgets that are not transformed into a block will be really usable.

    Additionally, I am still waiting on abstraction “things” to happen for people to migrate regular widgets from their plugins into usable blocks. I think there should be something like that. I mean that in an EASY, really easy to follow way.

    Report

    Reply

  3. This update has a lot to understand and potentially like. What about sites that have chosen to stick with the classic editor, how would widgets as blocks work then? Would the classic widget work for those sites?

    Report

    Reply

  4. Putting widgets into the customiser where you can live preview how they will look and function does seem sensible. I always found the current mechanism of configuring widgets a bit dusconnected from what appears on the front end.

    Report

    Reply

  5. Maybe the best thing is to keep the existing layout, but just allow the use of all blocks within the accordion content areas?

    The most logical approach would be to add Gutenberg to the preview area, but that would mean recoding it to work on the frontend? Or could the the blocks be added like widgets and the inline editing be in the preview area?

    Report

    Reply

  6. It is an interesting journey, we’re on with WP and Gutenberg.

    Not being best friends with Gutenberg right now, i still clearly see the innovative potential and i am looking forward to what it might become.

    Right now i still prefer BeaverBuilder… but well… that is not for free… and for pages, where less design is ok… Gutenberg might do the job.

    Report

    Reply

  7. Gutenberg is quite a good editor. But, still, I don’t know, why I prefer classic editor. After this update, I will definitely try it again.

    Report

    Reply

  8. Honestly, besides accessibility (which is a real problem), they should focus on fix those annoying issues Gutenberg has instead of moving into a phase 2. Better to successfully close phase 1 and then move ahead than open more and more issues.

    Report

    Reply

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.