Discussion on the future of Drupal in 2024, including Drupal 11 and the introduction of recipes. They explore the use of Symphony Mailer in Drupal 10 and the upcoming deprecation of Drupal 7. The speakers share their experience creating a Drupal Advent Calendar and their expectations for the future of Drupal. They also discuss the challenges of module dependencies and look forward to Drupal 11 with the combination of project browser and recipes.
The combination of Project Browser and Recipes in Drupal 11 is transformative, making Drupal more accessible for non-developers.
Improving the admin experience and user interface in Drupal is a priority to enhance its user-friendliness for site builders.
The potential for Workspaces in Drupal 11 allows easier management and publishing of content in bulk, beneficial for retail operations and seasonal changes.
Deep dives
Project Browser and Recipes
The combination of Project Browser and Recipes in Drupal 11 is seen as transformative, allowing non-developers to easily build experiences and work with Drupal. The ability to easily create customized Drupal installations using starter kit teams is especially appealing. The hope is that this will make Drupal more accessible and user-friendly, opening up new possibilities for ambitious site builders.
Improved Admin Experience and UX
There is a general excitement about the continued efforts to improve the admin experience and user interface in Drupal. The goal is to make Drupal more user-friendly for site builders, reducing the need for workarounds and making it easier for non-developers to take advantage of Drupal's power.
Workspaces
An under-discussed feature is the potential for Workspaces in Drupal 11. This feature would allow users to handle multiple nodes and work on them in a dedicated space, making it easier to manage and publish content in bulk, which could be valuable for retail operations, seasonal changes, and other use cases. Lobbying for the completion and improvement of Workspaces is seen as an important step to enhance the content management capabilities of Drupal 11.
Prediction for 2024: Increased interest in HTMLX with Drupal
I predict that in 2024, there will be a rise in interest and adoption of using HTMLX with Drupal. This combination is seen as a perfect fit, and all it needs is a successful implementation to take off. I anticipate that we will see discussions about HTMLX in future Drupal community events.
Prediction for 2024: Resurgence of in-person Drupal events
In 2024, I forecast a continued resurgence of Drupal in-person events. Since the end of the pandemic, there has been a noticeable increase in engagement and participation. I believe this will further invigorate the community and lead to more maturity in areas such as the integration of Storybook and the development of a JSX theme engine for Drupal.
Today we are talking about Drupal in 2024, What we are looking forward to with Drupal 11, and the Drupal Advent Calendar with James Shields. We’ll also cover Drupal 10.2 as our module of the week.
Includes capabilities that previously required contrib projects
File name sanitization
A search filter on the permissions page
End Users
Performance enhancements and improved caching APIs
Support for PHP Fibers to accelerate handling things like asynchronous remote calls
Content Creators
Revision UI for media
Wider editing area in Claro on large screens
The return of “Show blocks” in CKEditor 5, missing until now
Site Builders
Field creation UI has a new, more visual interface, and an updated workflow
Block visibility can now be based on the HTTP response status, for example to make it visible or invisible on 404 or 403 responses
Tour module is no longer enabled by default for the Standard and Umami profiles
New “negated regular expression” operator for views filters (string/integer), to exclude results matching a provided pattern
Site Owners
Announcements Feed is now stable and included in the Standard profile
The functionality in the experimental Help Topics module has been merged into the main Help module, so the Help Topics module is now deprecated
New permission: Use help pages
Developers
A fairly sizable change is a move to use native PHP attributes instead of doctrine annotations to declare metadata for plugin classes. Work is already underway to get core code converted, and an issue has been opened to have rector do this conversion for contrib projects
A new DeprecationHelper::backwardsCompatibleCall() method to help write Drupal extensions that support multiple versions of core
A PerformanceTestBase is now in core, to support automated testing of performance metrics
A new #config_target property in ConfigFormBase to simplify creating configuration forms
Symfony mailer is now a composer dependency of core
New decimal primitive data type
Expanded configuration validation, Symfony autowiring support, HTML5 output from the HTML utility class is now default, and more
In addition to these and the features highlighted in the official announcement, there are three pages of change records for the 10.2.0 release, and we’ll include a link to those in the show notes
Get the Snipd podcast app
Unlock the knowledge in podcasts with the podcast player of the future.
AI-powered podcast player
Listen to all your favourite podcasts with AI-powered features
Discover highlights
Listen to the best highlights from the podcasts you love and dive into the full episode
Save any moment
Hear something you like? Tap your headphones to save it with AI-generated key takeaways
Share & Export
Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more
AI-powered podcast player
Listen to all your favourite podcasts with AI-powered features
Discover highlights
Listen to the best highlights from the podcasts you love and dive into the full episode