Drupal Core currently provides a very rudimentary API for sending transactional emails. This applies to both, the way emails are constructed (markup rendered to plaintext) as well as the way they are delivered (using the very limited PHP mail function).
A growing number of contrib projects are attempting to close this gap. However, to give site builders the tools they need to make their emails look good and work with modern email infrastructure, contrib projects must apply crude hacks to work around the limitations of the core mail API.
This session is a very short introduction into core and contrib mail APIs followed by a (hopefully) long Q&A where the audience is encouraged to bring in their PoV regarding the future of transactional email. The results of this session will ideally lead to a clear and broadly accepted plan for the next step on how Drupal core transactional email is going to be modernized in upcoming releases.
Why we moved the database drivers to their own module and what we want to do next. First thing is that we would like to use PHP Fibers to load data synchronously from the database. The second thing is that we would like to use MongoDB as a backend and store content entity data in a document format.
The presentation showcases the improvements brought to Drupal by CKEditor 5, the changes to configuration process, and the Drupal modules and premium features available to improve the editor's functionality and collaboration.
The controller (Drupal Austria - Verein zur Förderung und Unterstützung der Opensource-Software Drupal, Austria) would like to use the following services in order to process your personal data. Technologies such as cookies, localStorage, etc. can be used for personalization. This is not necessary for the use of the website, but allows us to interact with you more closely. If you wish, you can adjust or revoke your consent at any time via our privacy policy.