❌

Normal view

Received β€” 4 November 2026 ⏭ Drupal - Open Source Content Platform | #Celebr8D8

State of CMS - 2026

State of CMS - 2026

Since 2016, the developer community has been conducting annual surveys on frameworks and programming languages. Many of you have probably participated in State of JS, State of HTML, or State of CSS. But what about those of us working with CMSs? There has been no equivalent survey for our community.

2026 has been a year of change for those of us who build and manage websites; I have a feeling that many of you are on the move, migrating websites from one CMS to another or building without it. AI is enabling rapid changes on all fronts. Broad market-share numbers tell us very little about your experiences building and managing websites with different tools; that is why I hope that we, as a community, can close this information gap with our own open-source State of CMS survey.

stateofcms.com

The anonymised results will be freely available on GitHub. I will also create and publish an interactive report, but I am especially excited to see what the community does with the data.

submitted by /u/kemnern
[link] [comments]

3 new components

Quick update; the Utility Components module now has 3 new components:

  • Styled text: Single line of text with support for font size, style and weight, letter spacing (tracking), line-height (leading), and capitalisation. It's good for those little colourful labels of all-caps text that AI likes to add to designs, or for extra large text (e.g. in a "key numbers" row).
  • Carousel: Displays multiple slides of content, one or more at a time. Choose between a "slide" and "fade" animation. Navigation between slides can be automatic, or controlled via swiping, scrolling, or arrow buttons. Built using Splide.
  • Marquee: Displays elements like images or text in a continuously-scrolling bar. Can be paused, and has controls for things like speed, gap, direction, etc. Built using Marquee6k.

They're vanilla and mostly independent, so you can just copy them into your existing theme if you want instead of installing the module. Just make sure to copy the relevant library if you do.

submitted by /u/dane_websites
[link] [comments]

Drupal minor versions will only get 8 months of security support from 2027, which in practice means 2 months to update

In case you missed PSA-2026-11-02 ( https://www.drupal.org/psa-2026-11-02 ): starting in 2027, each Drupal core minor version gets 8 months of security coverage instead of the 12 we've had since 8.6. The Security Team's reason is the flood of AI-generated security reports they can't keep up with on current funding. Fewer supported branches means less backporting.

The part that matters day to day: with a new minor every six months, when 11.6 / 12.1 comes out in June 2027, 11.5 / 12.0 only has two months of support left (until August 2027).

And Drupal 10 reaches EOL on December 9, the same week Drupal 12 (PHP 8.5 minimum) is released.

I'm migrating a few sites from 10 to 11 right now. Core isn't the issue. What eats the time is deprecated APIs in custom code, contrib modules several releases behind, the odd abandoned module, and patches in composer.json that no longer apply. Upgrade Status and Rector help, but the sites that were kept up to date are a completely different experience from the ones nobody touched for two years.

I wrote a longer post on what this means for site owners and what a maintenance budget should realistically cover now: https://menetray.com/en/blog/eight-months-drupal-shortens-security-support-and-your-site-cant-wait-year-anymore

Are your clients actually budgeting for regular updates, or are you still doing big catch-up jobs every couple of years?

submitted by /u/rmenetray
[link] [comments]
❌