Insights
Drupalcon 2023
Hannibal attended Drupalcon 2023 eand we like to share what the future holds for Drupal
At the annual Drupalcon event for Drupal developers, Drupal founder Dries Buytaert offered a fascinating insight into what the future holds for this acclaimed content management system. Inspired by other platforms such as React, Contentful, Squarespace, Wix and Adobe, Has taught Drupal what works and what doesn't in the world of web development.
One of the most notable announcements was the introduction of the Project Browser for Drupal 10.3. This innovative tool makes it easier for developers to install modules, increasing the efficiency of development processes. In addition, a new Field UI is being added to Drupal, making field creation even more flexible, which will benefit developers and site builders alike.
For site builders, there is good news: Drupal is working on speed improvements and exploring features similar to Gutenberg's functionality. This will result in more freedom and the ability to create reusable blocks, further increasing Drupal's flexibility.
Regarding maintenance of Drupal sites, automatic code fixes are already available in Drupal 10, and automatic updates are planned for 10.3. It is gratifying to learn that 97% of contribution modules are already ready for Drupal 10, making the transition to this new version considerably easier.
Drupal also highlights the Open Web Manifesto on Drupal.org, which expresses a commitment to always build on the foundations of freedom for all.
In addition, there are plans for a rebranding, a new website and targeted marketing efforts. Interestingly, developers are no longer the only target audience; Drupal is also targeting new partners and Web Summit participation. In 2024, we can expect brand changes, with a new website planned for May. In short, Drupal's future looks exciting, with numerous developments and updates on the horizon.
Accessibility on Wednesday: Improving the Drupal user experience
The Wednesday of Drupalcon 2023 focused on improving accessibility for users. Several tools and tips were shared to achieve this noble goal.
Several "Inclusive UX tools" were available, including tools for color rating, contrast ratio and color contrast control. One notable tool was the "EightShapes Contrast Grid," which provided various ratings for color contrast, ranging from AAA to DNP.
"Color.review" was an engaging tool focused on creating color combinations that work well for everyone. The importance of sufficient contrast in colors was emphasized with the "Contrast Ratio - WCAG Color Contrast Checker.".
In addition, valuable tips for empathetic design were shared. Here the emphasis was on semantics and the correct use of heading tags, sections, footers and headers. The importance of legible text, proper font size and avoiding overly long sentences was also emphasized, as was the use of clear and meaningful links and keyboard navigation focus style
Adding a "skip to main content" option was cited as an easy way to improve accessibility, while the exclusive use of color for visual interest and unnecessary typographical changes were discouraged.
The legal and ethical consequences of not prioritizing accessibility in Drupal web development, such as potential lawsuits, financial penalties and damage to reputation, were emphasized.
Steps to meet accessibility standards were shared, including using audit tools such as the "axelerant accessibility audit," following WCAG guidelines for at least AA compliance, regular testing and ongoing training.
In addition, Drupal's crucial role in promoting accessibility was highlighted, with attention to aspects such as search engine forms, color contrast, images and form labels.Drupal offers useful modules to support accessibility, such as the "Accessibility audit" module with tools like "accessibility checker" and "a11y," and modules for site builders and end users to improve the accessibility of Drupal websites
.
This session offered valuable insights for making Drupal websites more accessible to all users.
Shifting workloads to background processes: Efficiency in action
The focus is on improving efficiency, responsiveness and resource utilization optimization on Web sites. The goal is to perform heavy tasks efficiently and move less critical tasks to the background for a seamless user experience.
To determine which tasks are prioritized, criteria such as criticality, complexity, CPU versus I/O utilization, urgency and direct impact on the user are used.
There are several approaches to addressing these optimizations. One example is performing tasks such as inventory management in the background, and combining functionalities to keep the code streamlined.
Useful tools, such as the "Batch API," are available to manage resources but do not perform tasks in the background. The "Cron API" handles scheduled tasks, but has some challenges such as overlap and timeout problems and a lack of oversight.
One powerful tool is the "Queue API," which outsources resource-intensive tasks without disrupting the user experience. However, it requires attention to memory management and prioritization (following the FIFO principle).
Queueworkers can be deployed to automate generic queuing tasks, and convenient contrib modules are at your disposal to facilitate task management.
All in all, using the queue provides an effective method to improve the performance and memory management of Web sites, resulting in a smooth user experience even when performing complex tasks in the background.
Automated software updates: A big step toward security and efficiency
At Drupalcon 2023, automated software updates and the many benefits they bring were discussed at length. The main benefit is improved security, as regular updates protect the Web site from security threats. In addition, automated updates save time, cost and reduce risk.
The process of automated updates involves four steps: detection, application, testing and deployment. Several tools are available to detect updates, such as Dependabot, Snaky, Codario and Mend Renovate. Automated tests, such as Cypress.io, Codeception and others, help test updates before and after deployment.
One of the biggest challenges is relying entirely on automated testing. In general, successful automated software updates require solid hosting infrastructure, automated detection, deployment and testing.
The main reasons why automated updates are not yet widely used are lack of budget or experience. A fair amount of testing and error analysis is required before a perfect setup is achieved.
Nevertheless, it is important to recognize that automated software updates are a worthwhile investment in ensuring a high-performing Web site.