DrupalCon Portland Wrap-Up
Last week, Alexis Findiesen and I traveled to Portland, Oregon for DrupalCon. Portland, cleverly noting that Drupal’s logo is a water drop, welcomed over 3,300 Drupalistas from all over the world with four days of nearly non-stop rain! Now that Alexis and I are back on the east coast and mostly dried out, here’s a quick summary of a few of my favorite sessions, keynotes and DrupalCon moments.
Drupal 8 is Coming!
Now that Drupal 8 “Code Freeze” is only about a month away, we’re starting to get a really good idea of which features are going to make it into the final release, coming this winter. Project lead Dries Buytaert’s The Current State of Drupal 8 keynote on Tuesday gave a good overview of where things stand now. Or rather, where they stood last Tuesday, but I’m getting ahead of myself. Drupal 8 development has been focused on several major core initiatives, and the leads of most of those initiatives offered updates in breakout sessions. Here’s a sampling:
- Views, long one of the most popular contributed modules for Drupal, is moving to Drupal 8 core. While the user interface is mostly unchanged from Drupal 7, under the hood it’s been completely rewritten, and it should make site building much easier.
- Drupal 8 has a new templating engine called Twig. It’s going to remove a lot of the complexity from Drupal theming, while at the same time giving themers even more flexibility to make Drupal sites look awesome.
- The Mobile initiative is going to make it much easier for Drupal to handle all kinds of browsers, whether it’s a site visitor viewing your site on a giant 27″ monitor, or your site’s managing editor making an emergency update from her iPhone.
- Last, but certainly not least, the Configuration Management Initiative promises to eliminate one of the biggest causes of headaches for Drupal developers and site owners—synchronizing configuration settings from development to staging to production servers without blowing away content.
These and other sessions gave us some great information to help us continue to plan our own Drupal 8 migration (Have you started working on your migration strategy yet? We can help!), and upgrading the modules we’ve contributed to the Drupal project to version 8. There were also some great sessions on designing and prototyping for Drupal, creating interactive maps, and using Drupal as a backend to power data-driven mobile apps.
“Responsive Design Won’t Fix Your Content Problem”
Drupal 8 does a great job of presenting content to a wide variety of devices in the post-desktop era, with responsive design out of the box. But Wednesday’s keynote speaker, user experience guru Karen McGrane, says what the web really needs to be future-friendly is responsive content, with true separation of content from form, and an end to letting content creators treat the web like print.
Social Events and the Hallway Track
While the sessions were great, the real draw of DrupalCon is the opportunity to meet and hang out with other Drupalers, from down the street or the other side of the globe. Hallway conversations, informal “Birds of a Feather” sessions, lunches, dinners, a wet midnight trek to Voodoo Doughnuts, and even a “pinball pub crawl” gave us lots of chances to share Drupal war stories, talk about favorite modules and techniques, and explore chances for collaboration.
On Tuesday night, a group of volunteers gathered in DrupalCon’s 24-hour Coder Lounge to build a website to help organize resources for victims of Monday’s tornado in Moore, Oklahoma. The next day, FEMA director Craig Fugate officially announced the launch of help4OK.org in a tweet.
Whenever you get several Drupalers together in the same place at the same time, great things tend to happen. When you get over 600 Drupalers together in the same place at the same time, truly magical things can happen. Every Drupal 8 session I attended included a plea from the presenter that went something like this: “Do you like what you see here? Do you want to make sure it makes it into the final D8 release? We need your help! Come to the sprint on Friday!” And people did. In droves.
Alexis and I decided to help out with the new Twig templating engine. Earlier in the week, there was a lot of concern that Twig wouldn’t make it into Drupal 8. While Twig itself had been added sometime back, most of the rest of Drupal hadn’t yet been converted to use Twig. Unless every single template in Drupal core got converted to Twig, well before the July 1 code freeze, Twig would be pulled out in favor of the old PHPEngine. A couple dozen of us settled around a few big round tables in one of the convention center’s meeting rooms and started finding things to work on in the issue queue. Before long, there was an announcement that Twig had just been committed to core! Not too long after that came the news that the “mega-patch” (that would convert all of Drupal core’s templates to Twig) was nearly ready. We helped out with checking to make sure the new templates were outputting the exact same markup as the old ones, profiling to make sure the new templates weren’t any slower than the old ones, and a couple of other Twig-related tasks.
Elsewhere in the convention center, other teams were working on other Drupal 8 initiatives, several contributed modules, and Drupal documentation. It was an exciting day!
Sadly, the next North American DrupalCon isn’t for another year, in Austin. But CapitalCamp, D.C.’s annual Drupal Camp, is barely two months away!