You are here
Happy 13th birthday Drupal! It’s hard to believe so much has happened with Drupal when it really just started as a little hobby project. I'm super proud of what we accomplished. After all these years, it continues to be a passion and labor of love to grow, maintain and sustain the larger community.
A birthday presents us with a great time to look back and reflect. Though there are many things we could reflect on, I'd like to use this post to look at the bigger picture and share my perspective on the market. This means this blog post mainly offers a business perspective rather than a technical perspective.
From web to digital
Drupal was grown out of my own interest in the web. Today, it is a critical component of many organizations’ operations. For most organizations, having an online presence -- like a website or mobile application -- is an essential part of running their business, and it only continues to grow in importance. The rise of mobile and social media means we no longer talk about having a “website” or having a “web application;” instead we talk about the totality of the “digital experience.” Providing visitors or customers with a great digital experience is no longer a nice-to-have; it is a make-or-break point.
From content to experiences
For Acquia, creating high quality content and driving traffic to our site was the #1 way to generate new leads in 2013. This is true for the vast majority of organizations; high-quality, valuable content remains important. Five years ago, this meant if you had a business, and you didn't have a blog, it was time to start one. Today, it involves so much more than creating pages or cranking out new sites; you create and manage your content, and find ways to promote and reuse it across multiple channels to generate awareness and reach more people. You track and measure all of your efforts and try to optimize the content for different users. Content is gold, but delivering the right content to the right user at the right moment in the right format is platinum. It's no longer just about publishing content; it’s about managing the entire experience of a site visitor or user over time.
From mobile to context
Just like in the last half decade or so, "mobile" has completely redefined the internet, in the next half decade or so, "contextualization" will redefine it once again. The next big challenge, and opportunity, for Drupal, is figuring out how to make it a platform not just for content creators to deliver essentially the same content to users in their preferred language on their preferred device, but a platform for content creators to deliver the most appropriate content to each individual user.
Digital experience platform
As the Drupal community, we need to stop thinking of Drupal as a "content management platform" and start looking at it as a "digital experience platform" used to create ideal visitor experiences. This means publishing content that is easily accessible on multiple devices, and ensuring the site can be easily integrated with other tools, such as social media sites and customer relationship, e-mail and campaign management systems. We've been doing this for many years but it doesn't hurt to recognize the trend, double down on it and evolve our vocabulary.
You may have heard me talk about Web Experience Management (WEM) in the past, but we should move away from that term. The fact is that “web” doesn’t capture all the possible touch-points for Drupal, be it a website, mobile device, game console, wearable device, or something else.
Creating better interfaces to develop structured content, and delivering that content to a variety of devices and channels, is an important part of creating ideal customer experiences. Another important part is the ability to personalize what content to present to a user. Though it will be interesting to see how CMSs facilitate this direction, it seems imperative that CMSs deliver tools to empower content creators to not only create great content, but to also help them make decisions about what content to deliver to whom, when and in what format. Over time, these content decisions will become more data-driven and automated, and less opinion-based and manual.
Few CMSs are actually growing in market share; our industry will continue to consolidate further in 2014. The fact most CMSs become less and less relevant isn’t a surprise since CMSs are becoming more complicated. The CMSs that will survive are those that (1) are able to keep up with the speed of the Internet and (2) offer the least amount of friction to adopt. Open source CMSs that foster a healthy community are well positioned to win in the long run. Drupal's biggest challenge going forward is to create a user experience that gets out of a user's way and lets them do their business regardless of how simple or complex their task is. This is why I'm so passionate about in-place editing, and usability in general, but also creating a great developer experience. It's important that we continue to focus on those goals in 2014 and beyond.
For a long time, there has been somewhat of a misconception about Drupal’s viability for the largest, most complex deployments. Analysts, technology decision makers and proprietary competitors such as Sitecore and Adobe will claim that Drupal is great for simple sites but lacks the scale and depth of features needed for enterprise deployments. They're wrong! They only have to look at how GE, White House, MSNBC and many others are using Drupal. Drupal 8 is in a great position to take this "digital experience management" to the next level and to further cement Drupal's reputation; from the mobile improvements, to the authoring experience improvements, to APIs, to getting even better at structured content, Drupal 8 is set up for growth.
We've come a long way in the past 13 years. I'm immensely proud of our community for making this awesome contribution to the betterment of the internet for everyone. But we also have a lot of work ahead as the internet, just like the drop, is always moving. Drupal 8 will continue to help democratize web publishing and digital experience management. This is exciting since we can bring these tools to the masses (including individuals, small and large organizations) rather than only being available to those that can afford the million dollar license fees sold by proprietary software vendors. Happy birthday, Drupal!
As is now a tradition, here is my annual Acquia retrospective. Time to look back at 2013. In your life, you only get an opportunity to do so many things, so you have to focus on doing things that matter. I'm fortunate that Drupal and Acquia are remarkable stories. I take time to write these retrospectives for you and for me. I write them for you, because you might benefit from my experiences or from analyzing the information provided. But I also write them for myself so I don't forget this incredible journey. If you want, you can read previous retrospectives: 2009, 2010, 2011 and 2012.
For Acquia, 2013 was another excellent year. It was our fifth full year in business (i.e. revenue-generating year), and we finished the year with 19 consecutive quarters of revenue growth. In short, 2013 was a year of continued momentum, record bookings and great customer success. With five-year sales growth of more than 84,100 percent, Acquia was identified as the second fastest-growing company on Deloitte's Technology Fast 500 in North America. Acquia was also listed among North America's fastest growing software companies in 2013's Inc. 500. We're all very proud of that.
We hired 208 people this year and ended the year with 412 employees, up from 280 employees at the end of last year. 337 employees are based in the US, with 197 in Burlington, 27 in Portland, and 113 remote employees. We employ 75 people outside of the US, 53 of which are based in our office in Reading, UK. In 2013, we almost doubled our headcount in the Reading and Portland offices. Additionally, we hired 31 interns in 2013.
Acquia grew its customer base to more than 4,000 organizations. Some of the brands we've added as customers include Intel Corporation, Polycom, News Corp Australia, Timex, the National Association of Realtors, the X PRIZE Foundation, Columbia University, McGraw Hill Financial, Bart.gov and the Red Cross.
In 2013, Acquia continued to be focused on providing Drupal support to our customers. We reached the milestone of 100,000 support requests received and resolved during our company lifespan. In 2013 alone, we resolved almost 32,000 customer service requests, up 30 percent from 2012. We invested a lot in scaling our support team and on improving overall customer satisfaction and responsiveness. For example, we created a dedicated customer onboarding team. The result is that we spent more time with our customers to better understand their needs and help solve their Drupal questions. In 2014, we'll continue to keep customer success front and center. It's something we are very passionate about.
With regards to Acquia's software products, it was certainly our busiest year. Not only did we continue to invest heavily in Acquia Cloud and Acquia Network, we also launched some new products. Acquia Commerce Cloud was unveiled last quarter, providing a platform for creating content-rich, socially enabled shopping experiences. Acquia Cloud Site Factory was also released, providing a platform for launching and managing hundreds of websites. We unveiled Drupal Commons 3.0, our Drupal-based community platform, that was identified a Social Platform leader by Forrester Research. And we delivered the general availability release of the Mollom Content Moderation Platform, a content moderation platform built for the enterprise.
The cloud continues to prove to be a great way for organizations to save money, manage websites more efficiently and bring them to market faster. And Drupal is no exception to this trend -- in 2013, many organizations decided to standardize on Drupal in a big way, moving away from the variety of different systems -- exactly the vision we laid out in 2010.
And the proof is in the numbers: Acquia Cloud grew from 4,300 AWS instances at the end of 2012 to 7,300 AWS instances at the end of 2013. In aggregate, we're now serving more than 22 billion hits a month or 319 TB of bandwidth. I believe that makes Acquia the largest Drupal infrastructure provider in the world. Some of the Acquia Cloud achievements I'm most proud of include hosting the Grammy Awards (462 million visits) and hosting Red Nose Day during their largest fundraising event ever (£75 million/$113 million raised in one night).
Drupal community and Acquia
In 2013, we continued our long track record of giving back to the larger Drupal community.
- We sponsored 77 Drupal events in 2013, helping thousands of Drupal developers connect and collaborate together.
- Our product teams sponsored work on numerous important community modules, such as Media, Organic Groups, and more …
- The authoring experience work for Drupal 8 that we started last year landed in core this year, including WYSIWYG and in-place editing. We also sponsored work on redesigned content creation page and an improved blocks UI for Drupal 8.
- Also on Drupal 8, we sponsored work on the Web Services and Migrate in Core initiatives, donating the Migrate module authors' time.
- We helped set up numerous process improvements to help streamline Drupal 8 core development, including various "hard problems" discussions at DrupalCons to work through complex issues, releasing monthly alpha releases for user and developer feedback, and laying out the criteria for beta 1. We've also helped establish communication channels to help promote what is happening in Drupal 8: the This Week In Core series, and the Drupal 8.0 landing page.
- We helped the Drupal Association to establish Drupal.org Working Groups to provide better leadership and transparency to the Drupal website. Some of our team also helped assist on Drupal.org upgrade and security issues.
I'm particularly proud of Acquia's contributions to Drupal. It's part of our philosophy to give back, and we work hard to do our part by contributing to the Drupal community -- the reason why we exist. I'm proud of this because it is not trivial to give back as much as we do.
What I'm most proud of is that we have accomplished all of this "the open source way". Since Acquia's interests are so aligned with Drupal's, we try to raise the tide for the Drupal community at large.
At the end of the day, we're not selling Drupal or cloud hosting. We're selling what can be done with Drupal. The belief in the limitless. No matter what you dream, you can do it, and Drupal will get you there -- and Acquia is here to help you succeed. Thank you for 2013, and we're looking forward to working with more customers that are changing the world.
(I originally wrote this blog post as a guest article for Forbes. I'm cross-posting it to my blog.)
To "assemble" means to build. Assembling also means that we come together. Sometimes, both aspects are true. When that happens and we work together to build, we are better off for it.
The open source community is a perfect example of this. When Linux creator Linus Torvalds spoke about how it felt to get contributions from a worldwide network of people, he remarked "I had hoisted myself up on the shoulders of giants". I'm lucky enough to feel the same way.
The Internet has created a culture of sharing, letting people connect and collaborate on areas of common interest. When I started developing Drupal in 2000 from my university dormitory in Antwerp, I never imagined I'd build a network of people who were interested in building a content management system with me. Yet word of my project spread, and before I knew it, I was getting contributions to my project from around the world. Soon I also was standing on the shoulders of giants.
We didn't know it at the time, but this founding group of Drupalists was creating the basis for the assembled web. The assembled web is the next stage in the evolution of the web. While the coded web will always continue to exist, it will be a minority.
Think of the assembled web almost as an app store model for creating a digital experience. For example, if you want your website to allow social comments to flow in from Facebook or Twitter, you can simply add a module that someone has already coded. If you want to add analytics, maps, or almost anything you can imagine — there's probably a module for that.
While the modules are built on a foundation of code, they require no coding to install and build with ... to assemble. Instead, the vision of a great digital experience can be accomplished by someone with no coding experience, who can now simply "snap" the pieces of a new web experience together.
So, why is the assembled web rising to prominence so quickly, and what does that mean for developers?
- First, there are more websites now than ever before, and there's no sign of that growth slowing down. Ten years ago, a company had one website. Now, that same company might manage dozens or even hundreds of sites.
- Second, the complexity of websites has skyrocketed. Applications, integrations with third-party systems, social media integration, and the mobile web have all driven this complexity. New technologies emerge and replace the old. For example, Flash has almost been driven to extinction, replaced by HTML5, CSS3 and other more modern standards.
These two trends, set against the way many sites are built today, make it difficult to keep up with the changing standards, much less innovate and move the digital experience forward.
There is only one way to keep up: do more with less. I first imagined the assembled web in 2005, when the widespread use of content management systems began to replace the webmaster role as we knew it. Webmasters were no longer hired to write HTML by hand, or upload code to an FTP. In a way, the CMS eliminated the middleman.
Beyond our own evolution as developers, outside forces have also fundamentally altered the web. Ten years ago, the global phenomenon of Facebook didn't exist. Twitter didn't exist. The iPhone had yet to be released and create the mobile ecosystem that we know today. Think about the amount of change that's happened in such a short period. Now what will the world, and the web, look like another 10 years from today? No one knows.
The best thing to do is to adopt a platform that can change at the pace of the web. Developers will be tasked with building new functionality, and expanding the world of possibilities that modules can deliver. The innovation that developers will bring is crucial, and will power the assembled web by lowering barriers and democratizing the experience of site building.
The assembled web doesn't just have implications for the way developers create websites. It will have a widespread impact on any person or organization that needs to keep up with rapidly changing external forces. That's pretty much everyone. Think about how the assembly line changed manufacturing the first time. And how 3D printing is changing it again now. We can build faster and smarter than ever before. Similarly, the assembled web gives more people the tools to build the web as we know it.
Anyone without coding experience will be able to use an open source CMS to assemble a site by simply snapping modules together. A marketer could build a site for a new product launch without relying on the engineering team. An entrepreneur could launch a company site without hiring a webmaster. This phenomenon frees up time for developers to create new ways to connect citizens to their governments, nonprofits to donors, businesses to customers, friends and family to each other. Launching a disruptive business idea or reacting to today's rapid market changes could be accomplished without technical assistance. Going from vision to realization, for the first time, would be a single step. This advantage would finally bring the speed of digital site building in line with the speed of the web.
This evolution isn't a scary thing for developers; it's an opportunity. The web has forced a constant reinvention of everything. Careers. The way we compete for business. Being more efficient in the way we assemble a website will allow us to focus on the things that matter more, like innovation and creativity. By standing on the shoulders of giants, we can make things look and operate more beautifully than we'd ever have expected.
Over the past two years, we've built Drupal 8 into what will be the most flexible, future-proof Drupal version ever. Core developers have contributed thousands of hours of work to expanding Drupal 8's capabilities and modernizing our APIs.
We're several months into Drupal 8's API completion phase, and we're releasing monthly alphas as we nail down key APIs, refine the developer experience, and continue vital work on performance. To finish Drupal 8, we must focus on essentials, so I'd like to ask the Drupal developer community to look ahead to the next big step: the first Drupal 8 beta.
When does alpha become beta?
Earlier in the year, we announced that Drupal 8's first beta would be released once we had a stable data upgrade path from Drupal 7. At DrupalCon Prague, however, the Drupal core developer team made a bold decision: instead of using Drupal's
update.php database update script to convert Drupal 7 sites to Drupal 8 on the fly, Drupal 8 core will instead include a robust data migration API (based on the popular migrate module) to migrate data from existing sites into new Drupal 8 installations. This means that Drupal 8 core will provide reliable, extensible migration from Drupal 6 as well as Drupal 7. We believe this to be important for organizations running older versions of Drupal can reliably modernize their sites.
Data migration no longer blocks a beta release
In order to make this important data migration change possible for Drupal 8, the initial Drupal 8.0 release will be primarily intended for building new Drupal sites, and the finished data migration path for existing Drupal 6 or 7 sites may be provided in a later Drupal 8 release, like Drupal 8.1. (For more information on how we might improve the Drupal release cycle after the release of Drupal 8, see the proposal to manage the Drupal 8 release cycle.)
This means that a data upgrade path from Drupal 7 is no longer a prerequisite for releasing Drupal 8.0-beta1. Instead, we will focus on what testers and contributed module authors most need from a Drupal 8 beta: (1) a stable data model and (2) stable critical APIs.
Stable data model
A stable data model means that developers should not need to perform data migrations between beta releases of Drupal 8 (except where necessary to resolve critical issues). The Drupal 8 data model includes database schemas, file-based configuration storage, and storage services like the Entity and State systems.
Stable critical APIs
To provide contributed module developers with a useful milestone for module porting, beta 1 will include stable critical APIs. These are fundamental APIs that most or all contributed modules depend on, including the configuration system, the Entity and Field API, the Plugin API, and the Routing and Menu systems.
Other API changes approved by core maintainers will continue through the end of the API completion phase, but after the first beta, we will shift from away removing deprecated code and instead retain more backward compatibility layers. (Module/theme developers who wish to go through the porting process only once should wait for the first release candidate.)
What issues are blocking beta1?
Drupal core maintainers determine which specific issues must be resolved to meet the criteria above. We have worked with core developers to identify a list of beta-blocking issues. There are currently 48 of these "beta blockers" outstanding. As you can see, there are many difficult problems in this list that need to be solved. We need your help to resolve these issues so that we can release beta1 and expand Drupal 8's reach to new testers and contributors.
It's focus time!
While the end of Drupal 8's development cycle is in sight, there's still a lot of work to do. Now more than ever it's essential to focus on the critical issues that will bring Drupal 8 closer to release. If we don't, we risk pushing Drupal 8's release off for many more months. The sooner we create a beta, the sooner we can release Drupal 8 to the world.
Many people looking forward to Drupal 8's release aren't sure how best to help out. I'd like to ask all sub-system maintainers to watch their sub-system's issue queues closely to help new contributors triage issues and fix bugs, especially for beta-blocking issues. I'd also like to ask everyone to review patches carefully, make only necessary API changes, and document APIs clearly. Or, if you aren't able to work on Drupal 8 issues directly, consider sponsoring core developers for Drupal 8 contribution.
Help us make Drupal 8 the best release of Drupal yet by working on our alpha releases and toward a Drupal 8 beta!
For the International Day of People with Disabilities (IDPwD) today on December 3rd, I want to take some time to reflect on the Drupal community’s work to support universal access to information technology. Drupal is an inclusive community, both in how we interact with each other and in the results of our work.
We understand the need to create software that is accessible, both for consumption and production of content. Our accessibility statement opens by saying:
As an inclusive community, we are committed to making sure that Drupal is an accessible tool for building websites that can also be accessed by people with disabilities.
Donna Benjamin and Jesse Beach wrote a great overview of the accessibility improvements efforts in Drupal 8. It will meet higher standards of access than our previous releases. As developers and site builders, we continue to incorporate new techniques and access technologies into Drupal. Accessibility to the core.
As a community, we're proud and thankful for the efforts of all those who have contributed time and energy writing, reviewing and testing patches aimed at improving the accessibility of Drupal. There is much work still to do. If you are able, please join the accessibility effort to make sure our next version is our best yet. Thank you!