One of the most complicated aspects of Drupal has always been the upgrading of your Drupal website to the next major version. Part of this complexity is rooted in the diverse ways you can build and arrange your content in a Drupal website.
This year the North America DrupalCon will be held in Baltimore, Maryland during the week of April 24th through April 28th. The North American conventions have averaged around 3,000 attendees in recent years and so are definitely a premier event in the field.
At some point or another, everybody who has worked with Drupal has encountered a bug or piece of functionality that didn’t work as expected. This isn’t an indictment of Drupal itself, but rather a reality of software in general. No matter how well-engineered the code, sometimes things break or run into unforeseen conditions.
A recent blog post from Dries Buytaert shed some light on an ongoing initiative for Drupal 8, the Workflow Initiative. The goal of this initiative is to increase the range of capabilities that Drupal provides with respect to content staging, editing, and deployment. While at first review this might seem mundane, the ability to have better control over the creation of content in Drupal is a feature set that is important to many people (as per the 2016 State of Drupal survey).
One of the Aspects of Drupal 8 that seemingly has confused people a great deal, but upon closer inspection is not exceptionally difficult to understand, is the routing system. While the system has a foreign sounding name compared to systems you might be familiar with in older Drupal versions, the underlying functionality the routing system controls will actually seem quite familiar once you take a look at the code and what it does.
One of the more interesting aspects of the extensive Drupal overhaul that came with the Drupal 8 update, was the file-base configuration management system. While settings are stored in the database of a Drupal website, with Drupal 8 those settings and configurations can now be automatically exported and save as files within the Drupal installations file system.
It’s been a little more than a year since the RC1 (or release candidate one) of Drupal 8 was released. With the ongoing stabilization and feature improves that have been released since the official launch, Drupal 8 has been fairly well received. While there are potentially still some contributed modules which you might need or want for your project that are still in alpha state or not ready for official use, by and large Drupal 8 is being adopted at a steady rate.
With the new year comes many great things and hope for the future, not just in our personal lives but also in the Drupal community. This coming Spring, the 2017 DrupalCon will be held in Baltimore and promises to hold some great sessions and information about upcoming additions to Drupal 8. Monarch Digital has been attending the annual North America DrupalCons for many years now, and will be in attendance at Baltimore as well. (Come by our booth and say hello if you are there!)