Drupal 8.6 is expected in September 2018 with a feature freeze since 18 July. With all the major improvements introduced in the previous versions, expectations are running high across the Drupal community of developers, marketers, content managers and open-source enthusiasts.
Following our reflection over the past and present of Drupal, let’s anticipate the future as we highlight the most interesting initiatives that are working hard to be included in Drupal 8.6:
To ease the adoption of Drupal 8, the Migrate API became a part of the Drupal core. While custom migrations were possible from the beginning, the module keeps on extending functionality to further ease content migrations, both from Drupal installs and other sources.
Starting from a contributed media module, Drupal now includes an entire Media API, which allows better media management and re-usability.
Allows content authors the flexibility to alter the layout of webpages without the need of pre-defined templates or complex administrative interfaces.
Allows for (de)scheduling of content, content staging between environments, handling simultaneous work on the same content and other nifty features for content managers.
A new installation profile to showcase the power of a Drupal 8 website. Instead of the former (demo) dull, empty page, the user is welcomed with a blooming food magazine. Filled with content (recipes, images and other media) it shows the possibilities of Drupal.
Working on an automated way of installing Drupal updates, incorporating composer.
Drupal 8 (and symfony) are relying on composer for its updates and dependencies. The integration is not 100% transparent however.
Drupal is shipped with a completely new way of handling configuration management (based on active / staging files on the disk). A second iteration is started to improve this for different environments and re-usability.
Improve and enhance the different levels of documentation (developer / end-user).
A complete list of initiatives and their most up-to-date status is available online. Apart from the list above, there are also a lot of community ideas being generated from problems or improvements the community identifies. If they receive sufficient interest from both the community as the Drupal core team, an idea might be approved and it can become an active initiative, which can be included as an experimental module in a future release of Drupal.
Kevin is Drupal Web Developer and Consultant at AMPLEXOR based in Belgium. Kevin is an Acquia Certified Developer with over 6 years of experience in planning, development, maintaining Drupal websites and leading development teams in Drupal. He has also volunteered at the organization of the yearly Belgian DrupalCamp event.