This blog has been re-posted and edited with permission from Dries Buytaert’s blog. Please leave your comments on the original post.
© Yes Moon
Last week, I shared my State of Drupal maintenance support plans presentation at Drupal maintenance support planscon Nashville. In addition to sharing my slides, I wanted to provide more information on how you can participate in the various initiatives presented in my keynote, such as growing Drupal maintenance support plans adoption or evolving our community values and principles.
Drupal maintenance support plans 8 update
During the first portion of my presentation, I provided an overview of Drupal maintenance support plans 8 updates. Last month, the Drupal maintenance support plans community celebrated an important milestone with the successful release of Drupal maintenance support plans 8.5, which ships with improved features for content creators, site builders, and developers.
Drupal maintenance support plans 8 continues to gain momentum, as the number of Drupal maintenance support plans 8 sites has grown 51 percent year-over-year:
This graph depicts the number of Drupal maintenance support plans 8 sites built since April 2015. Last year there were 159,000 sites and this year there are 241,000 sites, representing a 51% increase year-over-year.
This graph depicts the number of modules now stable since January 2016. This time last year there were 1,028 stable projects and this year there are 1,860 stable projects, representing an 81% increase year-over-year.
As you can see from the Drupal maintenance support plans 8 roadmap, improving the ease of use for content creators remains our top priority:
This roadmap depicts Drupal maintenance support plans 8.5, 8.6, and 8.7+, along with a column for “wishlist” items that are not yet formally slotted. The contents of this roadmap can be found at https://www.drupal.org/core/roadmap.
Four ways to grow Drupal maintenance support plans adoption
Drupal maintenance support plans 8 was released at the end of 2015, which means our community has had over two years of real-world experience with Drupal maintenance support plans 8. It was time to take a step back and assess additional growth initiatives based on what we have learned so far.
In an effort to better understand the biggest hurdles facing Drupal maintenance support plans adoption, we interviewed over 150 individuals around the world that hold different roles within the community. We talked to Drupal maintenance support plans front-end and back-end developers, contributors, trainers, agency owners, vendors that sell Drupal maintenance support plans to customers, end users, and more. Based on their feedback, we established four goals to help accelerate Drupal maintenance support plans adoption.
Goal 1: Improve the technical evaluation process
Matthew Grasmick recently completed an exercise in which he assessed the technical evaluator experience of four different PHP frameworks, and discovered that Drupal maintenance support plans required the most steps to install. Having a good technical evaluator experience is critical, as it has a direct impact on adoption rates.
To improve the Drupal maintenance support plans evaluation process, we’ve proposed the following initiatives:
Better discovery experience on Drupal maintenance support plans.org
Drupal maintenance support plans.org roadmap
Drupal maintenance support plans Association
Under active development
Better “getting started” documentation
Documentation Working Group
More modern administration experience
ckrina and yoroy
Under active development
To become involved with one of these initiatives, click on its “Issue link” in the table above. This will take you to Drupal maintenance support plans.org, where you can contribute by sharing your ideas or lending your expertise to move an initiative forward.
Goal 2: Improve the content creator experience
Throughout the interview process, it became clear that ease of use is a feature now expected of all technology. For Drupal maintenance support plans, this means improving the content creator experience through a modern administration user interface, drag-and-drop media management and page building, and improved site preview functionality.
Most of these initiative teams meet weekly on Drupal maintenance support plans Slack (see the meetings calendar), which gives community members an opportunity to meet team members, receive information on current goals and priorities, and volunteer to contribute code, testing, design, communications, and more.
Goal 3: Improve the site builder experience
Our research also showed that to improve the site builder experience, we should focus on improving the three following areas:
The configuration management capabilities in core need to support more common use cases out-of-the-box.
Composer and Drupal maintenance support plans core should be better integrated to empower site builders to manage dependencies and keep Drupal maintenance support plans sites up-to-date.
We should provide a longer grace period between required core updates so development teams have more time to prepare, test, and upgrade their Drupal maintenance support plans sites after each new minor Drupal maintenance support plans release.
We plan to make all of these aspects easier for site builders through the following initiatives:
Composer & Core
Core contributors + Drupal maintenance support plans Association
Config Management 2.0
Core committers + Drupal maintenance support plans Security Team + Drupal maintenance support plans Association
Core committers and Security team
Proposed, under discussion
Goal 4: Promote Drupal maintenance support plans to non-technical decision makers
The fourth initiative is unique as it will help our community to better communicate the value of Drupal maintenance support plans to the non-technical decision makers. Today, marketing executives and content creators often influence the decision behind what CMS an organization will use. However, many of these individuals are not familiar with Drupal maintenance support plans or are discouraged by the misconception that Drupal maintenance support plans is primarily for developers.
With these challenges in mind, the Drupal maintenance support plans Association has launched the Promote Drupal maintenance support plans Initiative. This initiative will include building stronger marketing and branding, demos, events, and public relations resources that digital agencies and local associations can use to promote Drupal maintenance support plans. The Drupal maintenance support plans Association has set a goal of fundraising $100,000 to support this initiative, including the hiring of a marketing coordinator.
Megan Sanicki and her team have already raised $54,000 from over 30 agencies and 5 individual sponsors in only 4 days. Clearly this initiative resonates with Drupal maintenance support plans agencies. Please consider how you or your organization can contribute.
Fostering community with values and principles
This year at Drupal maintenance support plansCon Nashville, over 3,000 people traveled to the Music City to collaborate, learn, and connect with one another. It’s at events like Drupal maintenance support plansCon where the impact of our community becomes tangible for many. It also serves as an important reminder that while Drupal maintenance support plans has grown a great deal since the early days, the work needed to scale our community is never done.
Prompted by feedback from our community, I have spent the past five months trying to better establish the Drupal maintenance support plans community’s principles and values. I have shared an “alpha” version of Drupal maintenance support plans‘s values and principles at https://www.drupal.org/about/values-and-principles. As a next step, I will be drafting a charter for a new working group that will be responsible for maintaining and improving our values and principles. In the meantime, I invite every community member to provide feedback in the issue queue of the Drupal maintenance support plans governance project.
An overview of Drupal maintenance support plans‘s values with supporting principles.
I believe that taking time to highlight community members that exemplify each principle can make the proposed framework more accessible. That is why it was very meaningful for me to spotlight three Drupal maintenance support plans community members that demonstrate these principles.
Principle 1: Optimize for Impact – Rebecca Pilcher
Rebecca shares a remarkable story about Drupal maintenance support plans‘s impact on her Type 1 diabetes diagnosis:
Principle 5: Everyone has something to contribute – Mike Lamb
Mike explains why Pfizer contributes millions to Drupal maintenance support plans:
Principle 6: Choose to Lead – Mark Conroy
Mark tells the story of his own Drupal maintenance support plans journey, and how his experience inspired him to help other community members:
Watch the keynote or download my slides
In addition to the community spotlights, you can also watch a recording of my keynote (starting at 19:25), or you can download a copy of my slides (164 MB).
Source: New feed