Tag Archives: Gutenberg

Gutenberg 19.2 Released with Enhancements and Bug Fixes – WP Tavern

[ad_1] Gutenberg 19.2 was released on September 11, 2024. This latest release includes notable changes such as Block Bindings UI, enhancements to the Zoom Out mode, an experimental client-side media processing feature, and some bug fixes. Here’s a rundown of the key features and changes: Block Bindings UI Moving Out of the Experimental Phase One of the most significant updates in Gutenberg 19.2 is removing the experimental flag from the Block Bindings UI. This feature, now fully integrated into the editor, allows users to link block attributes with external data sources seamlessly. By default, only admin users can create and modify bindings, ensuring greater control and security.  Vicente Canales from the Core team has shared this video in the announcement post.  Preview Options Extensibility The new release also adds extensibility to Preview Options via the Plugin API.Plugin and theme developers can now introduce custom preview options in the block editor’s preview dropdown. This allows users to preview content in different formats or environments, offering more flexibility in how they view their creations. Enhanced Zoom Out Mode The toolbar now has an “Edit” button, making it easier to switch between modes. Users can also exit Zoom Out mode by double-clicking on blocks and the “Shuffle” block toolbar button has been removed.  Content-Only Mode Enhancements In Content-Only mode, top-level locked blocks now support block styles, providing more consistent designs. Block icons are also now displayed in the toolbar for easier identification. Experimental Client-side Media Processing Gutenberg 19.2 introduces an experimental client-side media processing feature. This reduces the server load and potentially improves performance and efficiency.  Other notable highlights include: A new reorder control is available at the field level on the new view configuration UI. The minimum supported WordPress version for Create Block is now set to 6.6. Only admin users are allowed to create and modify block bindings by default. Block editor improvements include a ‘Reset’ option for the MediaReplaceFlow component and Block Library enhancements include better handling of social icons and pagination blocks. 10 bug fixes, including a fix for pagination arrows pointing the wrong way in RTL languages and resolving an editor error in Safari caused by the checkVisibility method. There has been one reported issue with this release, where it causes problems with the Web Stories editor. WordPress Core Committer Pascal Birchler has confirmed that the issue is related to Gutenberg and not Web Stories. Interested users can also check out Riad Benguella’s post on Gutenberg development practices and common pitfalls. [ad_2] Source link

Continue reading

Gutenberg 19.1 Introduces Plugin Template Registration API – WP Tavern

[ad_1] Gutenberg 19.1 has arrived, introducing the eagerly anticipated plugin template registration API and updates to image caption styles. This Gutenberg version will be later incorporated into WordPress 6.7. The highlight of this release is the plugin template registration API. It addresses a long-standing issue developers have faced with conflicts between plugins and themes, particularly when dealing with custom post types, taxonomies, or virtual pages. This new feature allows developers to register block templates directly within their plugins, providing fully customizable default content layouts. Till now, developers had to use multiple filters to register templates. By building on the Gutenberg block system, this update makes it easier for themes and users to adapt and personalize templates according to their design and functional needs. Justin Tadlock has published a detailed tutorial on this feature on the Developer Blog and will host a Developer Hours Session with Nick Diego on September 10, 2024. This release also tones down the intensity of the caption background, improving the image caption styles.  Other notable changes in this version include: Improved data view extensibility Better defaults for the zoom out view Added border support for core blocks Applied elevation scale to Modal, Popover, and Snackbar components. Fixed wp-config anchors to make wp-env compatible with WordPress versions older than 5.4. The community’s response has been enthusiastic, with feedback such as “Really like this feature”, “Great one, that I am looking for !” and “Literally the greatest news I’ve heard in years (and I had a baby last year)” [ad_2] Source link

Continue reading

Is Gutenberg Finally Winning Users Over? We Analyzed 340+ Opinions to Find Out

[ad_1] Over the past few months, I’ve been diving deep into what people really think about WordPress’ block editor – Gutenberg. I thought this was going to be a fun project. I analyzed over 340 opinions from platforms like Reddit, Twitter, YouTube, and WordPress.org. I also spoke with developers, colleagues, and other professionals in the WordPress community to get a well-rounded perspective. The goal was to understand how people feel about the block editor in 2024. When it first launched at WordCamp Europe in 2017, the initial reaction was curiosity, which quickly turned into disappointment. That reputation has been hard to shake ever since. However, I’m noticing a slight shift. For instance, take this chart: What it shows is the ratio of 1-star to 5-star reviews over time for the standalone Gutenberg plugin. As you can see, we were really close – really close(!) – to a tipping point, but negative reviews have started creeping up again. So, is the block editor actually improving, or are users starting to get frustrated again? Depending on how deep you want to go, I have two choices for you: 💪 “I’m interested in the whole thing! I want to see all the opinions, plus the potential implications for the WordPress ecosystem as we know it.” → Go to the main post on Themeisle 🤩 “I just want a compilation of some interesting/ridiculous/insightful/surprising comments.” → Keep reading Now, the chart I showed above tells just part of the story. While the percentage ratio of negative to positive opinions is what it is, it’s also important to note that Gutenberg has been getting significantly fewer reviews each year. In 2024, for example, only 37 reviews have been added so far (eight months into the year at the time of writing). Given that early reviews came in much larger numbers, it’s difficult to say with confidence whether the WordPress community has been enjoying Gutenberg more (or less) over time. What we can say for sure, though, is that people aren’t any less passionate about it. 🤩 Here are some of the most interesting opinions I found (according to my subjective assessment). [ad_2] Source link

Continue reading

Gutenberg 14.3 Improves Image Drag and Drop – WP Tavern

[ad_1] Gutenberg 14.3 was released this week with drag-and-drop improvements for both the block editor and the site editor. Automattic-sponsored contributor Aaron Robertshaw published a video, illustrating how the block editor now supports  dropping an image onto an empty paragraph block to replace it with a new Image block. The site editor has also added drag-and-drop capabilities for blocks and patterns in the new zoomed-out view, which was added in Gutenberg version 14.1. It zooms out to focus on building and composing patterns, allowing users to move sections around without affecting the inner blocks. It can be enabled under “Experiments.” In 14.3, users can drag blocks and patterns right onto the canvas with an overhead view that makes it easy to place in between existing blocks. video source: Gutenberg PR #44402 This version also introduces new support for alt + arrow keyboard combinations for navigating blocks. Robertshaw explained how they work: For example, if your cursor is towards the end of a long paragraph, you can quickly press alt + up arrow to move to the beginning of that paragraph. If you are already at the beginning of a text block, you’ll move to the start of the previous paragraph. Similarly, alt + down arrow will move you to the end of a block of text. The Styles typography controls have been updated to include the Tools Panels that users have available in the Block Settings interface. This makes the experience more consistent and expands the capabilities to allow for resetting the values. This release includes dozens of fixes and improvements to design tools, components, the Block API, and more. Check out the changelog in the announcement post for the full list of updates. Gutenberg 14.3 will not be included in the upcoming WordPress 6.1 release but will be rolled into core the next time around. If you want these features now, you can install the Gutenberg plugin. [ad_2] Source link

Continue reading

10up Publishes Gutenberg Best Practices Website – WP Tavern

[ad_1] 10up has published a Gutenberg Best Practices website as a public resource with tutorials, documentation, and example code. Maintaining current documentation has not been a strong point of the official Gutenberg project as the pace of the project makes it difficult for contributors and extenders to keep up. “Gutenberg introduced an entirely new editorial paradigm for content creation and page building within WordPress,” 10up Associate Director of Editorial Engineering Fabian Kaegy said. “Because the block editor is still fairly new, it is advancing quickly and changes are introduced regularly; as such, learning opportunities are scarce and we have felt an absence of best practice documentation that meets 10up standards for craftsmanship.” 10up’s Gutenberg Best Practices were written to supplement WordPress’ core documentation with what Kaegy said is a “more client-services-centric approach tailored to engineering enterprise-level editorial experiences.” For developers who are brand new to working with the block editor, the Reference section has a wealth of information about the anatomy of a block, the fundamentals of block theming with theme.json, block extensions, block variations, and more, with supporting videos and gifs. The documentation also gives a little more context for practical usage. For example, the section about Block Transforms includes information about when and how to define block transforms. The Training section of 10up’s Gutenberg Best Practices contains a mini crash course on the file structure of a block and all of its components, and how to build a custom block using the 10up Starter Block. This is especially helpful for developers looking for some extra guidance developing their first blocks. The Guides section contains more advanced topics like extending core blocks and including frontend JS with a block. The documentation is available on GitHub for anyone to contribute edits. The site also links to a discussion board on GitHub where developers are welcome to join discussions and workshop the best practices in collaboration with 10up employees. 10up has published the Gutenberg Best Practices website with a beta designation and intends to update and expand it as WordPress evolves. [ad_2] Source link

Continue reading

Gutenberg 14.4 Introduces Distraction-Free Mode, Redesigns Pattern Inserter – WP Tavern

[ad_1] Gutenberg 14.4 was released today with long-awaited support for distraction-free editing, to the delight of content editors around the world. It hides all non-essential UI and clears the canvas for a focus on text-based content creation. The mode can be toggled on in the options menu in the top toolbar. Distraction-free mode hides the top toolbar, any open sidebars, along with the insertion point indicator and the block toolbar. source: Gutenberg 14.4 release post The project to improve the editing experience for text-based content began with early explorations in February, which progressed into a PR that contributors have been refining for the last few months. This distraction-free mode is a monumental improvement over the days when users struggled to write with various UI elements popping in and out of view. Another major update in 14.4 is the redesigned pattern inserter. It has been updated to show the categories before rendering the patterns, giving users a more fluid visual preview as they browse the pattern library. Patterns can be dragged and dropped from the preview pane into the canvas. source: Gutenberg 14.4 release post Other notable improvements users may notice include the following: Performance benchmarks show an improvement in loading time for both the post and site editors. Check out the release post to see the full list of all the changes and bug fixes included in 14.4. This release will not be included in the upcoming WordPress 6.1 release next week, but users who are eager to adopt these new features can get them right now in the Gutenberg plugin. [ad_2] Source link

Continue reading

Gutenberg Contributors Explore a New Browse Mode for Navigating the Site Editor – WP Tavern

[ad_1] It’s easy to get lost while trying to get around the Site Editor unless you are working day and night inside the tool. The navigation is jumpy and confusing, especially when going from template browsing to template editing to modifying individual blocks. A large PR is in progress for redesigning this UI with the introduction of a “browse mode” that would make the experience feel more like a design tool. Gutenberg lead engineer Riad Benguella opened the PR as a continuation of the ongoing work on this project, which has its roots in ideas and explorations that have been fermenting since 2019. He shared a video that roughly demonstrates the target for the proposed UI changes. It essentially introduces a “navigable frame” where users can select from a menu of features on the left. More detailed efforts on improving the animations and placement of the menu items is happening simultaneously within the ticket. The original idea was to include the “Navigation menu” item inside the sidebar, but Benguella removed it in favor of keeping the PR contained to simply adding the “edit/view” mode. Although such a large PR has the potential to introduce a slew of regressions, Benguella said there is no other way around a big PR due to the the necessity of the structural changes to how the site editor is organized. He is attempting to keep it narrowly focused and not try to tackle features like browsing capabilities and adding UI (template lists, global styles, etc) to the sidebar. The idea is not without some pushback. Alex Stine, Cloud Platform Engineer at Waystar, warned against introducing another Mode into Gutenberg, saying it “feels kind of reckless considering we haven’t refined existing modes for all users.” He noted that Gutenberg already has select/edit mode contexts. “This was a feature basically added for screen readers only,” Stine said. “I am hoping this will one day be removed, but we’re not quite there yet. “I think the community is trying to solve the wrong problem. If Gutenberg itself did not have such a complex UI, there would not be the need for a hundred different modes in a hundred different contexts, blocks, or even editors. We have gone so crazy making everything so quickly, no one thought about how to unify the interface across all editors. This feels like it could be another patch to a bigger problem.” Stine cautioned against growing the UI for something that ultimately doesn’t make things any simpler. “In a sense this PR doesn’t introduce any new mode, it just redesigns the current navigation panel a bit,” Benguella said in response. “I think it’s an opportunity to improve the a11y of the navigation in the site editor. “The confusion in this PR is that it’s not about another mode in the editor itself, it’s higher level, it’s how we choose which template and template part to edit before actually entering the editor.” Although the project’s contributors have been referring to it as “browse mode,” it is essentially a redesign for the existing UI to make it more intuitive for users to navigate. Gutenberg may not need any more new “modes” but the site editor is in dire need design improvements that will unify the experience and make it less chaotic for getting around. During the most recent core Editor meeting, Gutenberg contributors called for feedback on the big PR, since it has so many moving parts and needs more scrutiny. It’s not ready to land in the next release of Gutenberg yet, but the concept is rapidly taking shape and may expand to include more features in the sidebar once the basic structure is in place. [ad_2] Source link

Continue reading

Gutenberg 11.5 Adds Widget Grouping, Iterates on the Block Gap Feature, and Updates Nav Menus – WP Tavern

[ad_1] Gutenberg 11.5 landed earlier today. 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. I have had mixed reactions to the features that made it into the latest release. At some points, I thought to myself, finally, this made it in. At other moments, I rendered my best version of Jean-Luc Picard’s famous facepalm. But, the wheel keeps turning, and the developers who put their time and effort into the project continue to improve it. 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. 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. This should be bundled in point release such as WordPress 5.8.2 so that users are not waiting for it until 5.9. Navigation Block Changes With nav menus still being a pain point in site editing, Gutenberg has added new levels of complexity. The Site Title and Site Logo blocks are allowed inside of the Navigation container. As Joen Asmussen shared in the original ticket, some complex layouts would benefit from allowing more inner elements within the Navigation block: Navigation block patterns. This could open a world of layout possibilities for theme authors through custom patterns. I have no issue with Gutenberg tackling the foundation for these more advanced layouts. However, we have yet to smooth out the basics of navigation. The experience of searching for and inserting in-site links is lackluster at best, requiring multiple mouse clicks. There is an open ticket for a lighter navigation experience, and that should be the focus. Theme authors should also note that the Navigation block now relies on the CSS gap property for spacing instead of margin. 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. This change could impact existing theme designs. FSE Admin Notice Limited to Themes Screen The lone FSE theme admin notice. There are plenty of gripes to be had with the Gutenberg plugin as its features are constantly in flux. 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. In previous versions of the plugin, this notice has appeared on every screen in the backend. Now, it only appears on the Themes/Appearance page. Over the past few months, I have kept the Toolbelt plugin by Ben Gillbanks active for the sole purpose of hiding this notice. Good riddance. Farewell. Widget Group Block Editing a Widget Group block title. 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. As I have been repeating since September 2020, the feature was fundamentally broken. The goal was to allow end-users to add blocks in more places, but it was never compatible with classic theme markup and styles. I proposed using patterns, but the team went with a Widget Group block. The end result is similar but not exactly the same. The good news is that it fixes what should have been a blocker for the feature landing in core. The better news is that this is likely to land in WordPress 5.8.2 instead of the 5.9 release later this year. I would not go as far as calling it a perfect solution. The experience does not make it immediately clear how to add a widget title. Users must first add a block. Once a block is added, they can then click on the heading/title placeholder that appears. Then, the UI switches to a field for typing the title. The following video shows how the Widget Group block works: I would rather have a bit of a janky experience than no solution at all. At least users now do not have to manually create widget wrappers. Some could even deactivate the Classic Widgets plugin if this issue was a holdup. “Row” Group Variation and Flex Layouts Adding a post meta (byline) section with the Row block variation. To begin testing the new flex layout system introduced in Gutenberg 11.2, the development team has added a variation on the Group block named Row. This allows users to align inner blocks side by side instead of on top of each other in the default “flow” layout. There are tons of use cases for the feature. One of the primary scenarios for theme authors will be aligning post and comment metadata bocks next to each other. Previously, this required use of the Columns block or custom styles, neither of which are ideal. The experience is rough around the edges. I often found it hard to click in the right spot to edit a block, and the appender button did not always appear for adding new ones. The Social Icons block also uses the new flex layout. However, there is currently no way to switch it to flow mode for vertical social links. More Block Gap Integration Gap between each Column block. The Columns block now uses the gap feature introduced in Gutenberg 11.4 for handling the spacing between individual Column blocks. There is no UI for end-users to control this yet, but it is likely to land in a future release as the feature evolves. Gutenberg 11.5 has now added a bottom margin to the post title in the editor. For whatever reason, the development team has made a leap and assumed its current handling of the block gap feature needed this. It is a complex problem to solve. In the meantime, some users might see more whitespace than they are accustomed to between their title and content in the editor. Lots of extra

Continue reading

#7 – Ajit Bohra on Gutenberg, Full Site Editing and React – WP Tavern

[ad_1] Jukebox #7 – Ajit Bohra on Gutenberg, Full Site Editing and React Play Episode Pause Episode Mute/Unmute Episode Rewind 10 Seconds 1x Fast Forward 30 seconds 00:00 / 00:46:59 Subscribe Share About this episode. On the podcast today we have Ajit Bohra. Ajit is a keen advocate of WordPress, having used it and committed to it, for many years. He’s a full stack developer working at Lubus which is based in Mumbai, India. His team works with WordPress as well as offering solutions built with Laravel and React. He’s on the podcast today to offer up his opinions about the near future in WordPress and why he’s confident that the project is moving in the right direction. To make matters easier to digest we break up the podcast into three distinct sections. Starting off with Gutenberg we discuss where the Block Editor is at right now and what Ajit sees as the benefits of a Block based approach to content building. We go into some concrete examples of why Ajit thinks that the Block Editor is preferable to the Classic editor as well as discussing some of the projects that he’s been working on to enhance the editing experience for his team and the community. We also talk about the pace of development and whether or not it’s keeping up with the expectations of WordPress users. We then move onto a detailed conversation about Full Site Editing which is going to play a pivotal role in WordPress’ utility going forwards. The power that it will offer non-technical users to build out their entire site is an exciting prospect, but right now it’s still a work in progress. Ajit talks about why Full Site Editing is needed to compete in the CMS market as well as how Block Patterns will make site building much easier in the future. Finally we get into the subject of WordPress’ need to move towards a future in which React is playing a vital part in the software’s Core. Why does Ajit think that the project needed to move away from a PHP based platform; after all, it was easy to work with and people had become very familiar with how to build sites using their PHP skills. It’s a case of having to keep up, and as Ajit says, he thinks that you have to unlearn to learn. We briefly discuss the resources which Ajit used to up-skill, websites that he frequents and courses which he recommends should you wish to take the plunge. In parts the audio is a little choppy, in fact this is a second pass at recording this episode, but I felt that the message contained within was well worth publishing despite that, and I hope that you do too. Useful links. Ajit’s Twitter account Lubus BlaBlaBlocks Beginner Javascript ES6 Javascript 30 React for Beginners The Net Ninja YouTube channel The Beginner’s Guide to React Epic React Is WordPress Development Really All That Hard To Get Into Today? Transcript Nathan Wrigley [00:00:00] Welcome to the seventh edition of the Jukebox podcast from WP Tavern. My name is Nathan Wrigley. Jukebox is a podcast all about WordPress, the software, the events, and the community. Every month, we’re bringing you someone from that community to discuss a topic of current interest. If you like the podcast, please share it with your friends. You might also like to think about subscribing so that you can get all the episodes in your podcast player automatically. And you can do that by searching for WP Tavern in your podcast player, or by going to WP Tavern dot com forward slash feed forward slash podcast. You can also play the podcast episodes on the WP Tavern website, if you prefer doing it that way. If you have any thoughts about the podcast, perhaps the suggestion of a guest or an interesting subject, then head over to WP Tavern dot com forward slash contact forward slash jukebox. Use the contact form there and we’d certainly welcome your input. Okay, so on the podcast today, we have Ajit Bohra. Adit is a keen advocate of WordPress having used it, and committed to it, for many years. He’s a full stack developer working at Lubus, which is based in Mumbai, India. His team works with WordPress as well as offering solutions built with Laravel and React. He’s on the podcast today to offer up his opinions about the near future in WordPress and why he’s confident that the project is moving in the right direction. To make matters easier we break the podcast up into three distinct sections starting off with Gutenberg, we discuss where the block editor is at right now and what Ajit sees as the benefits of a block based approach to content building. We go into some concrete examples of why Ajit thinks that the block editor is preferable to the classic editor, as well as discussing some of the projects that he’s been working on to enhance the editing experience for his team and the community. We also talk about the pace of development and whether or not it’s keeping up with the expectations of WordPress users. We then move on to a detailed conversation about full site editing, which is going to play a pivotal role in WordPress’ utility, going forwards. The power that it will often non-technical users to build out their entire site is an exciting prospect, but right now it’s still a work in progress. Ajit talks about why full site editing is needed to compete in the CMS market, as well as how block patterns will make site building much easier in the future. Finally, we get into the subject of WordPress’ need to move towards a future in which React is playing a vital part in the software’s core. Why does Ajit think that the project needed to move away from a PHP based platform? After all, it was easy to work with and people have become

Continue reading

Gutenberg 11.4 Overhauls Galleries, Adds Axial Padding for Buttons, and Lays Groundwork for Global Spacing – WP Tavern

[ad_1] Another two weeks have flown by, and another Gutenberg plugin update is in the books. I always look forward to the latest release, awaiting what goodies our contributor community has produced. Sometimes I jump the gun and install a development version of the plugin to understand an upcoming feature, such as the new “block gap” style setting. Other times, I like to be surprised with enhancements like the new vertical/horizontal padding controls for the Button block. Of course, there is always a good chance that a plugin update will throw off our theme’s editor styles in a new and exciting way. It feels like it has been a while since Gutenberg caught me off guard. At least it is only the post title this go-round. The WP Tavern theme is aging a bit anyway. It is due for an update (hint, hint). Aside from block gap and axial padding, Gutenberg 11.4 turns the Gallery block into a container for nested Image blocks and adds duotone filter support to featured images. Other notable enhancements include an option for adding alt text to the Cover block and font-weight support to the Post Date, Post Terms, and Site Tagline blocks. Axial Padding for Button Block Adjusting vertical and horizontal Button padding. The Button block now supports changing the spacing along the X or Y axis when unlinking the padding. Previously, users could define the padding for all sides, but this could be tedious work. In most designs, top and bottom (vertical) padding should match, and left and right (horizontal) should get the same treatment. This change should speed up padding customization in nearly all cases. However, it does introduce a regression. The consensus in the ticket was that the tradeoff for a less cumbersome experience was worth less flexibility for edge cases. Overall, this should be a win for most. I am already a happier user. Gallery Block Uses Nested Images Adding a link to an Image block within a Gallery. The Gallery block in Gutenberg 11.4 supports nesting individual Image blocks. It is currently hidden behind an experimental support flag and must be enabled via the Gutenberg > Experiments settings screen. Effectively, the Gallery block is now a container. Inserting media still works the same way. The difference is that end-users have access to customize each Image block within a Gallery separately. One use case for this feature is to allow users to add custom links around images. However, they now have access to more of the Image block’s options, such as custom theme styles. Last week, I covered this feature in-depth because it is expected to land in WordPress 5.9, and theme authors should be ready for the transition. This is a breaking change in terms of HTML. Any themer with custom Gallery block styles should test the front-end and editor output before WordPress merges the changes. Featured Image Duotone Support Applying a duotone filter to the Post Featured Image block. While we are still missing an image size control, I will take any Post Featured Image block improvements I can get at this point. The block felt like a second-class citizen for so long that I am giddy about any enhancements. Duotone filters, which landed in WordPress 5.8, allow end-users to add a CSS filter over images to control shadow and highlight colors. Themes can register custom ones, or users can modify them. The latest Gutenberg plugin update brings this feature to the Post Featured Image block. This change allows theme authors to explore adding some visual flair since the Post Featured Image block is meant for templating or site editing. It still has a long way to go before it is ready for more advanced theme design, but the tools are getting us closer. Global Block “Gap” for Themes Highlighting a Paragraph block and its preceding “gap” (top margin). One custom feature that has become commonplace with themes that support the block editor is a “global spacing” style rule, which controls the whitespace between elements. Gutenberg contributors have noticed this trend and are now shipping a standard solution for it. Themes that use a theme.json file will automatically opt into support. The gap feature adds a top margin to all adjacent sibling elements within block containers. This creates the space between each block using a standard method. Theme authors can control this via the styles.spacing.blockGap key in their theme.json files. If you are a theme developer, this is one of the most crucial components of block theming from a pure design viewpoint. It is not something to avoid until it lands in WordPress. The time to test and provide feedback is now. It is also merely a first step. There are pieces left to implement and problems to solve. There is currently an open pull request to bring this to editor block controls. There is also another ticket for zeroing out the margins for the first and last blocks, which would typically not need any. There are still some open questions on how to best deal with exceptions to the default block gap in the original ticket. Regardless of its unfinished nature, it is an exciting development if you care anything at all about vertical rhythm in design systems. Like this: Like Loading… [ad_2] Source link

Continue reading
1 2 3