2007 is the year of my first DrupalCon, and the year the #1 most wanted end-user feature was
Better media handling. 2019 is the year that Drupal will finally have it. Doing things right takes time!
Back then I never would’ve believed I would some day play a small role in making it happen 🙂
Without further ado, and without using a mouse:
The text editor assisted in producing this HTML:
Let's talk about llamas!
(I like llamas, okay?)
If you’re wondering why something seemingly so simple could have taken such a long time, read on for a little bit of Drupal history! (By no means a complete history.)
2007 and Drupal five
- Drupal’s core features for file management and media handling
- common problems and requirements (restrictions, performance issues, multi-lingual content, dependencies between nodes and files)
- first approaches: own node types for managing, improved filemananger.module (example: Bloomstreet,European Resistance Archive, Director’s Cut Commercials)
- next step: generic media management module with pluggable media types, mutli server infrastructure, different protocols, file systems, file encoding/transcoding
It’s surprisingly relevant today.
The era of the venerable Media module, from which many lessons were learned, but which never quite reached the required level of usability for inclusion in Drupal core.
2013 (?) – 2019
The Media initiative started around 2013 (I think?), with the Media entity module as the first area of focus. After years of monumental work by many hundreds of Drupal contributors (yes, really!), only one missing puzzle piece was left: WYSIWYG embedding of media. The first thing I worked on after joining Acquia was shipping a WYSIWYG editor with Drupal 8.0, so I was asked to take this on.
To help you understand the massive scale of the Media Initiative: this last puzzle piece represents only the last few percent of work!
Drupal has always focused on content modeling and structured content. WYSIWYG embedding of media should not result in blobs of HTML being embedded. So we’re using domain-specific markup (
) to continue to respect structured content principles. The result is document transclusion combined with an assistive “WYSIWYG” editing UX — which we wished for in 2013.
A little less than two months ago, we added the
MediaEmbed text filter to Drupal 8.8 (domain-specific markup), then we made those have previews using CKEditor Widgets for assistive “WYSIWYG” editing, followed by media library integration and per-embed metadata overriding (for example overriding
alt, as shown in the screencast).
Complete media management shipped in increments
Fortunately, for many (most?) Drupal 8 sites, this will not require significant rework, only gradual change. Drupal 8.8 will ship with complete media management, but it’ll be the fifth Drupal core release in a little over two years that adds layers of functionality in order to arrive at that complete solution:
- Drupal 8.4 added foundational Media API support, but still required contributed modules for it to be usable
- Drupal 8.5 made Media usable out-of-the-box
- Drupal 8.6 added oEmbed support (enabling YouTube videos for example) and added an experimental Media Library
- Drupal 8.7 made the Media Library feature-complete: bulk uploads, massively improved UX
- Drupal 8.8 will contain the key thing that was blocking Media Library from being marked stable (non-experimental): WYSIWYG integration
Today is the perfect moment to start looking into adopting it shortly after Drupal 8.8 ships in December!
See slide 40! ↩︎