Dries Buytaert is the original creator and project lead for the Drupal open source web publishing and collaboration platform. Buytaert serves as president of the Drupal Association, a non-profit organisation formed to help Drupal flourish. He is also co-founder and chief technology officer of Acquia, a venture-backed software company that offers products and services for Drupal. A native of Belgium, Buytaert holds a PhD in computer science and engineering from Ghent University and a Licentiate Computer Science (MsC) from the University of Antwerp. In 2008, Buytaert was elected Young Entrepreneurs of Tech by BusinessWeek as well as MIT TR 35 Young Innovator.
Recent Blog posts
Decoupled Drupal seems to be taking the world by storm. I'm currently in Sydney, and everyone I talked to so far, including the attendees at the Sydney Drupal User Group, is looking into decoupled Drupal. Digital agencies are experimenting with it on more projects, and there is even a new Decoupled Dev Days conference dedicated to the topic.
Every spring, members of Acquia's Product, Engineering and DevOps teams gather at our Boston headquarters for "Build Week".
In the past, after every major release of Drupal, most innovation would shift to two areas: (1) contributed modules for the current release, and (2) core development work on the next major release of Drupal. This innovation model was the direct result of several long-standing policies, including our culture of breaking backward compatibility between major releases.
The goal of this blog post is to enable Drupal developers in need of web services to make an educated decision about the right web services solution for their project. This blog post also sets the stage for a future blog post, where I plan to share my thoughts about how I believe we should move Drupal core's web services API forward. Getting aligned on our strengths and weaknesses is an essential first step before we can brainstorm about the future.
In a recent post we talked about how introducing outside-in experiences could improve the Drupal site-building experience by letting you immediately edit simple configuration without leaving the page.
In a follow-up blog post, we provided concrete examples of how we can apply outside-in to Drupal.
The feedback was overwhelmingly positive. However, there were also some really important questions raised.
The one big question I get asked over and over these days is: "How is Drupal 8 doing?"
It's understandable. Drupal 8 is the first new version of Drupal in five years and represents a significant rethinking of Drupal.
So how is Drupal 8 doing? With less than half a year since Drupal 8 was released, I'm happy to answer: outstanding!