Editor's Note: This post was written collaboratively by Dharizza Espinach Barahona of Montreal-based Drupal experts at Evolving Web, along with Eric Michalsen of Pantheon. When it was published, Drupal 9 was the newest version of Drupal. Drupal 10 and 11 have since been released but the ideas in this post still hold true.
At DrupalCon New Orleans this month, my co-worker Andrew Taylor and I presented Lessons from WordPress Core.
DrupalCon LA was a complete blast. In addition to exciting announcements, amazing sessions and tons of fun side events, there were also a lot of super productive sprints that really pushed Drupal development forward. In the Drush sprints, the remaining issues tagged for Drush 7 were all reviewed, and either resolved or deferred, cumulating in the release of Drush 7.0 Stable today.
If you’ve spent much time upgrading older websites to PHP 7, it’s likely you have encountered the annoying situation where PHP notices are printed directly into the HTML output, causing them to display in an ugly, unformatted jumble at the top of the page. The effect looks something like this:
This post is for development teams tackling their first non-trivial Drupal 8 build, with multiple developers, and a timeline of several months.
Editor’s Note: This blog post and conference presentation was written for teams looking to migrate to Drupal 8. The ideas here are just as applicable to teams now looking to migrate to Drupal 9, 10, or 11. The big deal about Drupal 9 is that it is not a significant architectural change, compared its previous version the way Drupal 8 was a significant architectural change to Drupal 7.
In case you haven’t heard, Drupal 9.0 will be released on June 3rd, 2020.
If we’re being honest, 2020 is a year of (mostly unpleasant) surprises. When DrupalCon Minneapolis was canceled, and DrupalCon Global sprung up its place, many long-time Drupalists had no idea what to expect.
Fortunately, DrupalCon Global is on the (short) list of happy surprises in 2020! I asked the Pantheon developer relations team to reflect on DrupalCon Global: Lessons we learned, exciting new directions for Drupal, and more.
We just finished covering how simple configuration is still easy in Drupal 8, but how is Drupal 8 making the hard things possible in a way to justify changing the old variables API? Well, in Drupal 7, when you needed to handle complex configuration, the first step was ditching variable_get(), system_settings_form(), and related APIs. Drupal 8 has improved this situation two ways.
The upgrade from Drupal 8 to 9 is a good opportunity to consider an upgrade to the backend UX for your content creators. This is the case both for existing and new sites, and whether you have a lot of content or not.