Multiple vulnerabilities are possible if an untrusted user has access to write Twig code, including potential unauthorized read access to private files, the contents of other files on the server, or database credentials.
You will understand ins and outs of Drupal
You will be able to build your own Drupal site.
You will be able to manage your Drupal site.
You will be able to install Drupal Computer
You will be able to create content on your Drupal site
You will be able to layout your Drupal site
You will be able to install, update and use Drupal Modules
You will be able to install, update and use Drupal Themes
A couple of developers I spoke with during DrupalCon Prague expressed concern about the disappearance of the Source button. It will become impossible to use HTML editing because of this. In my experience, HTML editing is used primarily to find workarounds for editing problems. Hopefully, in CKEditor 5, we won’t need these workarounds anymore.
The update to CKEditor 5 is a big deal, as one can tell by the number of sessions during DrupalCon Prague dedicated to this project. CKEditor 5 has been written from scratch. It is an entirely new editor with different architecture and APIs. The new architect makes browser-specific bugs a thing of the past.
At the moment, you need to go to Drupal.org to find modules to add to your project. What if the modules were available within your Drupal project and could be installed with a simple push of a button in the user interface?
The current way the issue queue is organized can be pretty frustrating for module maintainers. There is little room for project management or prioritizing issues. To solve this, the community created ContribKanban. With GitLab, each project gets Kanban boards out of the box to help manage the issues.