digitalvast.blogg.se

Keeps defaulting to flowlayout
Keeps defaulting to flowlayout









keeps defaulting to flowlayout

The end result is similar but not exactly the same. I proposed using patterns, but the team went with a Widget Group block.

keeps defaulting to flowlayout

The goal was to allow end-users to add blocks in more places, but it was never compatible with classic theme markup and styles. As I have been repeating since September 2020, the feature was fundamentally broken. While I generally believe the Gutenberg plugin developers and core WordPress make good use of feedback, the block-based widgets system has been one area where the project has dropped the ball. Widget Group Block Editing a Widget Group block title. Over the past few months, I have kept the Toolbelt plugin by Ben Gillbanks active for the sole purpose of hiding this notice. Now, it only appears on the Themes/Appearance page. In previous versions of the plugin, this notice has appeared on every screen in the backend. However, the most annoying thing about running the plugin has been its persistent, non-dismissible admin notice when a user is running a block theme. There are plenty of gripes to be had with the Gutenberg plugin as its features are constantly in flux. FSE Admin Notice Limited to Themes Screen The lone FSE theme admin notice. This change could impact existing theme designs. I almost missed this since I customized this for my own projects months ago - welcome to 2021, where we no longer need to rely on hacky margin solutions for simple spacing. Theme authors should also note that the Navigation block now relies on the CSS gap property for spacing instead of margin. There is an open ticket for a lighter navigation experience, and that should be the focus. The experience of searching for and inserting in-site links is lackluster at best, requiring multiple mouse clicks. However, we have yet to smooth out the basics of navigation. I have no issue with Gutenberg tackling the foundation for these more advanced layouts. This could open a world of layout possibilities for theme authors through custom patterns. The Site Title and Site Logo blocks are allowed inside of the Navigation container.Īs Joen Asmussen shared in the original ticket, some complex layouts would benefit from allowing more inner elements within the Navigation block: With nav menus still being a pain point in site editing, Gutenberg has added new levels of complexity. This should be bundled in point release such as WordPress 5.8.2 so that users are not waiting for it until 5.9. Gutenberg automatically outputs some default editor styles if the user’s active theme does not register its own or have a theme.json file present. One quick note is that everyone not running a theme that supports the block editor should check that their backend styles are not out of place. But, the wheel keeps turning, and the developers who put their time and effort into the project continue to improve it. At other moments, I rendered my best version of Jean-Luc Picard’s famous facepalm. At some points, I thought to myself, finally, this made it in. I have had mixed reactions to the features that made it into the latest release. It is a hefty release that includes extensive changes to the Navigation block, a new way for grouping widgets, and more block gap feature integration.











Keeps defaulting to flowlayout