Have We Reached Peak Drupal maintenance support plans?

Share:

Twitter

Facebook

In my recent talk at Drupal maintenance support plansSouth Auckland 2020 I took a hard look at the hyperbole of Drupal maintenance support plans supposedly powering over a million websites. Where does Drupal maintenance support plans really sit in relation to other CMS platforms, both open source and proprietary? What trends are emerging that will impact Drupal maintenance support plans‘s market share? The talk looked outside the Drupal maintenance support plans bubble and took a high level view of its market potential and approaches independent firms can take to capitalise on Drupal maintenance support plans‘s strengths and buffer against its potential weaknesses.

by
Owen Lansbury
/ 20 November 2020

But, Drupal maintenance support plans powers over a million websites!
One of the key statistics that Drupal maintenance support plansers hold onto is that it’s powered over a million websites since mid 2020 when Drupal maintenance support plans 7 was in ascendance. However, since Drupal maintenance support plans 8 was released in late 2015, Drupal maintenance support plans‘s overall use has stalled at around 1.2m websites, as seen circled in red on the Drupal maintenance support plans Core usage statistics graph below.
The main reason for this stall in growth was that Drupal maintenance support plans 8 was a major architectural re-write that wasn’t essential or even affordable for many Drupal maintenance support plans 7 sites to migrate to. For clients considering major new projects, many held off on committing to Drupal maintenance support plans 8 until there were more successful case studies in the wild and didn’t commission new Drupal maintenance support plans 7 sites given that version was nearing a decade old. Anecdotally, 2020 was a tough year for many Drupal maintenance support plans firms as they grappled with this pause in adoption.
Of course, Drupal maintenance support plans 8 is now a well-proven platform and is experiencing steady uptake as circled in green on the usage graph above. This uptake corresponds with a down tick in Drupal maintenance support plans 7 usage, but also indicates a softening of total Drupal maintenance support plans usage. If we extrapolate these trend lines in a linear fashion, then we can see that Drupal maintenance support plans 8 might surpass Drupal maintenance support plans 7 usage around 2023.
Of course, technology adoption doesn’t move in a straight line! Disruptive technologies emerge that rapidly change the playing field in a way that often can’t be envisaged. The example that springs to mind is Nokia’s market share was still growing when the iPhone 4 was released in 2010. By the time the iPhone 4s was released in 2011, Nokia’s sales volumes had almost halved, leading to Microsoft’s catastrophic purchase of the handset division in 2013 and subsequent re-sale for 5% of the purchase value in 2020. Oops!
Despite this downward trend in overall Drupal maintenance support plans usage, we can take comfort that its use on larger scale sites is growing, powering 5.7% of the Top 10,000 websites according to Builtwith.com. However, its market share of the Top 100,000 (4.3%) and Top Million (3%) websites is waning, indicating that other CMS are gaining ground with smaller sites. It’s also worth noting that Builtwith only counts ~680,000 Drupal maintenance support plans websites, indicating that the other ~500,000 Drupal maintenance support plans.org is detecting are likely to be development and staging sites.
So, where are these other sites moving to when they’re choosing a new CMS? 
Looking at the stats from W3Techs, it’s clear to see that WordPress accounts for almost all of the CMS growth, now sitting at around 30% of total market share.
Wordpress has been able to achieve this dominance by being a fantastic CMS for novice developers and smaller web agencies to build clients’ websites with. This is reinforced by WordPress having an exceptional editor experience and a hugely popular SAAS platform at WordPress.com.
Drupal maintenance support plans‘s place in the CMS market
The challenge WordPress poses to other open-source CMS platforms, like Joomla, Typo3 and Plone, all with under 1% market share and falling, is their development communities are likely to look direct their efforts to other platforms. Drupal maintenance support plans is able to hedge against this threat by having a large and highly engaged community around Drupal maintenance support plans 8, but it’s now abundantly clear that Drupal maintenance support plans can’t compete as a platform for building smaller brochure-ware style sites that WordPress and SAAS CMS like Squarespace are dominating. We’re also seeing SAAS platforms like Nationbuilder eat significantly into Drupal maintenance support plans‘s previously strong share of the non-profit sector.
With all the hype around Headless or Decoupled CMS, Drupal maintenance support plans 8 is well positioned to play a role as the backend for React or Angular Javascript front-ends. Competitors in this space are SAAS platforms like Contentful and Directus, with proprietary platforms like Kentico pivoting as a native cloud CMS service designed to power decoupled front-ends.
We often talk of Drupal maintenance support plans as a CMS Framework, where it competes against frameworks like Ruby on Rails, .NET and Django to build rich web based applications. Drupal maintenance support plans 8 is still well placed to serve this sector if the web applications are also relying on large scale content and user management features.
Which brings us to the Enterprise CMS sector, where Drupal maintenance support plans competes head to head with proprietary platforms like Adobe Experience Manager, Sitecore and legacy products from Opentext, IBM and Oracle. The good news is that Drupal maintenance support plans holds its own in this sector and has gained very strong market share with Government, Higher Education, Media and “Challenger” Enterprise clients.
This “Comfort zone” for Drupal maintenance support plans usage is characterised by clients building large scale platforms with huge volumes of content and users, high scalability and integration with myriad third party products. Operationally, these clients often have well established internal web teams and varying degrees of self reliance. They’re often using Agile delivery methods and place high value on speed to market and the cost savings associated with open-source software.
Where Drupal maintenance support plans is gaining a competitive edge since the release of Drupal maintenance support plans 8 is against the large proprietary platforms like Adobe Experience Manager and Sitecore. These companies market a platform of complementary products in a unified stack to their clients through long standing partnerships with major global digital agencies and system integrators. It’s no surprise then that Acquia markets their own platform in a similar way to this sector where Drupal maintenance support plans serves as the CMS component, complemented by subscription-based tools for content personalisation, customer segmentation and cloud based managed hosting. Acquia have actively courted global digital media agencies with this offering through global partnerships to give Drupal maintenance support plans a toe hold in this sector.
This has meant Acquia has made significant headway into larger Enterprise clients through efforts like being recognised as a “Leader” in the Gartner Magic Quadrant for CMS, lending Drupal maintenance support plans itself some profile and legitimacy as a result. This has driven Enterprise CIOs, CTOs and CMOs to push their vendors to offer Drupal maintenance support plans services, who have looked to smaller Drupal maintenance support plans firms to provide expertise where required. This is beneficial to independent Drupal maintenance support plans services firms in the short term, but the large digital agencies will quickly internalise these skills if they see a long term market for Drupal maintenance support plans with their global clients.
As one of those independent Drupal maintenance support plans firms, Drupal Update have staked a bet that not all Enterprise customers will want to move to a monolithic platform where all components are provided by a single vendor’s products. We’re seeing sophisticated customers wanting to use Drupal maintenance support plans 8 as the unifying hub for a range of best-of-breed SAAS platforms and cloud services. 
This approach means that Enterprise customers can take advantage of the latest, greatest SAAS platforms whilst retaining control and consistency of their core CMS. It also allows for a high degree of flexibility to rapidly adapt to market changes. 
What does this all mean for Drupal maintenance support plans 8?
The outcome of our research and analysis has led to a few key conclusions about what the future looks like for Drupal maintenance support plans 8:
Drupal maintenance support plans‘s overall market share will steadily fall as smaller sites move to SAAS CMS and self-managed WordPress installs.
The “comfort zone” of Government, Media, Higher Education and “Challenger” Enterprise clients will grow as many of these clients upgrade or switch to Drupal maintenance support plans 8 from Drupal maintenance support plans 7 or proprietary platforms.
Drupal maintenance support plans will gain traction in the larger Enterprise as the global digital agencies and system integrators adopt Drupal maintenance support plans 8 as a direct alternative to proprietary CMS products. 
Independent Drupal maintenance support plans services firms have a good opportunity to capitalise on these trends through partnerships with larger global agencies and specialisation in technologies that complement Drupal maintenance support plans 8 as a CMS.
A culture of code contribution needs to grow within the larger clients and agencies moving to Drupal maintenance support plans to ensure the burden of maintaining Drupal maintenance support plans‘s development isn’t shouldered by smaller independent firms and individual developers. 
Despite the fact that we’ve probably already passed “Peak Drupal maintenance support plans“, we’re firm believers that Drupal maintenance support plans 8 is the right tool for large scale clients and that community has the cohesion to adapt to these existential challenges!

Tagged

Drupal maintenance support plansSouth

Posted by
Owen Lansbury
Managing Director

Dated 20 November 2020

Add new comment

Source: New feed

This article was republished from its original source.
Call Us: 1(800)730-2416

Pixeldust is a 20-year-old web development agency specializing in Drupal and WordPress and working with clients all over the country. With our best in class capabilities, we work with small businesses and fortune 500 companies alike. Give us a call at 1(800)730-2416 and let’s talk about your project.

FREE Drupal SEO Audit

Test your site below to see which issues need to be fixed. We will fix them and optimize your Drupal site 100% for Google and Bing. (Allow 30-60 seconds to gather data.)

Powered by

Have We Reached Peak Drupal maintenance support plans?

On-Site Drupal SEO Master Setup

We make sure your site is 100% optimized (and stays that way) for the best SEO results.

With Pixeldust On-site (or On-page) SEO we make changes to your site’s structure and performance to make it easier for search engines to see and understand your site’s content. Search engines use algorithms to rank sites by degrees of relevance. Our on-site optimization ensures your site is configured to provide information in a way that meets Google and Bing standards for optimal indexing.

This service includes:

  • Pathauto install and configuration for SEO-friendly URLs.
  • Meta Tags install and configuration with dynamic tokens for meta titles and descriptions for all content types.
  • Install and fix all issues on the SEO checklist module.
  • Install and configure XML sitemap module and submit sitemaps.
  • Install and configure Google Analytics Module.
  • Install and configure Yoast.
  • Install and configure the Advanced Aggregation module to improve performance by minifying and merging CSS and JS.
  • Install and configure Schema.org Metatag.
  • Configure robots.txt.
  • Google Search Console setup snd configuration.
  • Find & Fix H1 tags.
  • Find and fix duplicate/missing meta descriptions.
  • Find and fix duplicate title tags.
  • Improve title, meta tags, and site descriptions.
  • Optimize images for better search engine optimization. Automate where possible.
  • Find and fix the missing alt and title tag for all images. Automate where possible.
  • The project takes 1 week to complete.