![]() However, there used to be a problem with lazy-loading responsive images in Drupal because their tags lacked the width and the height attributes.ĭrupal 10.1 comes to the rescue providing the width and height attributes for responsive image tags, as well as adding a toggle element to switch between the loading=”lazy” and the loading=”eager” options in the “Responsive image” field formatter settings. Image lazy-loading has been widely used in Drupal as a recognized technique to boost website speed. ![]() Responsive image lazy-loading with a set width and height When checked, the Twig development mode checkbox exposes and automatically selects two additional checkboxes:ĭrupal 10.1’s new Development Settings page with Twig and cache settings. ![]() In a nutshell, there are the following checkboxes on the new page: See more details in our article about the new Development Settings page in Drupal 10.1. Managing the Twig and cache settings is indispensable for a clean and easy theme development process, helping front-enders to seamlessly troubleshoot issues in templates and instantly see the impact of their editing. Previously, front-end developers had to do cumbersome edits to the services.yml files, but not just a few button clicks in a handy interface are needed to achieve the same goals. This presents an exceptional leap forward in front-end workflows. The Drupal 10.1 admin dashboard boasts a new Development Settings page where you can enable the Twig development mode and disable caching. They are safe to refactor or delete without fear that they might be used somewhere else. SDC components can be shared and reused across multiple development projects at a snap of a finger. Furthermore, SDC automatically looks for component files and generates a library to render each component. When located in the same directory, all files are easy to find even for front-end developers that are new to Drupal. A slide about the SDC file structure from an internal workshop held by our team’s developers. The files include a YAML file with the metadata, a Twig file with the templates, a CSS file with the stylesheets, a JavaScript file with the scripts, and anything else that might be needed within a component. The essence of this new addition is its ability to group together all files that are necessary for rendering a UI component so they reside in a single directory. This incredible architectural improvement generated a lot of buzz in front-end development circles so our team held an internal workshop as well as published a detailed article about SDC. Drupal 10.1 advancements for front-end developers Single Directory Components (SDC)Ĭreating and managing interface components becomes significantly easier and more consistent in Drupal 10.1 with Single Directory Components (SDC). ![]() The Drupal 10.1 release has introduced tangible advancements for everyone, but it offers an exceptionally remarkable array of new features and updates that front-end developers would appreciate the most. The progress on the way from Drupal 10 to Drupal 11 is even more impressive. Drupal 10 was released with a bunch of improvements for front-end development such as modern JavaScript components in place of jQuery, Views Responsive Grids, the New Theme Starterkit Tool, the end of support for Internet Explorer 11, and more. It’s great to know that Drupal helps them along the way. Front-end developers are committed to crafting website interfaces that are not just visually captivating but also a joy for users to interact with.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |