We've recently changed the editing experience in Bootiga for our Drupal Commerce theme.

We started with Drupal's Layout Builder, but after testing it with non-technical store owners, we wanted something more intuitive.

So we've moved to Layout Paragraphs + Mercury Editor — and so far, we're really happy with the result.

Our goal with Bootiga is to make Drupal Commerce as easy as possible for non-technical users.

Do you know of any better alternatives to Mercury Editor for this? What would you choose today if the main priority was the best possible editing experience for the end user?

Hey, Robert from the MariaDB Foundation here. We run a yearly survey on how people actually use MariaDB. If you went with MySQL, PostgreSQL or something else we want to hear from you too :)

https://mariadb.typeform.com/to/tS69UzVo?utm_source=reddit_drupal

Drupal was one of the most common applications running MariaDB in last year's survey. I'm curious, what database are you using Drupal with, and how did you choose it? Any problems or wishes related to the database?

We revamped the questions this year and split them by role (developer, DBA, operator) to save you time. Over 400 answers so far, looking forward to reading yours. Anonymous results will be published at mariadb.org/survey.

Thanks for taking the time!
Cheers, Robert at MariaDB Foundation

Been doing Drupal migrations for about 10 years and seeing the same thing play out right now that happens every EOL cycle.

Teams think they have until December 9. They don't. Enterprise change freezes typically start mid-November. Some nonprofits freeze earlier because of year-end giving. A proper D10 → D11 migration takes 2-4 months.

So if you're starting now, you're already in rush territory. Starting in October means going into December with things half done.

The other thing nobody talks about — most good Drupal agencies are already booked into Q4. You're not just racing the calendar. You're racing everyone else who also waited.

If you want to check where your site actually stands, run this:

drush pm:list --status=enabled

Check every contrib module against drupal.org/security. That list will tell you exactly how much work is ahead. Happy to look at anyone's output if they want a second opinion.

https://www.drupal.org/psa-2026-09-21

There will be a security release for a widely used contributed module on September 23, 2026 between 17:00 and 21:00 UTC.

We are announcing this release in advance because the affected contributed module is used on a significant portion of Drupal sites, and the upcoming release will include a significant number of advisories. The advisory with the highest risk score for the release is currently rated as critical.

Edit

From slack,

This will be the first time we've handled this many advisories, but we're also taking steps to do as much in advance as possible, so we'll see how it goes and then we'll know how long it takes 🙂

Also,

This will not be covered by Drupal Steward. There are far too many individual advisories, and many of them would not be mitigatable by a WAF rule, so it would give a false sense of security if we did probably. (And nothing is highly critical.)

I'll update the PSA accordingly.

🫠

Drupal 9 marketing site, ~180 pages, 40 blog posts, the one contractor who knew it left. PHP and module updates were piling up, so instead of going to Drupal 10 I pointed Claude Code at it and rebuilt in Next.js.

What it did:

• Read the modules and theme to map content types, fields and views, then pulled the actual content out via JSON:API into MDX files. Fields became frontmatter, embeds became components.
• Rebuilt the theme as React components, close enough that nobody noticed
• Recreated the blog/tag listings as filtering over the files
• Wrote the redirect map for old URLs
• Set up SST with OpenNext: CloudFront, S3, Lambda, Route53 in one config. sst deploy, done.

Where it struggled: ~600 images in weird paths took a few passes, webforms had to be rewritten against Lambda + SES (and I lost spam protection for a week without noticing), and it kept trying to add a headless CMS until I told it Markdown in git IS the CMS.

Drupal's been off two months. Hosting went from $90/mo to ~$4. Content changes are now "open Claude Code, describe the edit, review PR, merge."

Downside: nobody non-technical can edit anything without me. Fine for us now, but I'm wondering if I've just made myself the new single point of failure, same as the contractor was.

What am I missing? Anyone running content-in-git + AI as the CMS past a couple hundred pages?

The Drupal Association is conducting its first-ever Drupal Ecosystem Retrospective. This is a good opportunity to directly give the Drupal Association your candid feedback and thoughts about what you feel is going well and what needs improvement in the Drupalverse.

The due date for filling this out is September 20, 2026 (I have no idea if there’s a specific time; I’m just a random Drupaler who wants as many people in our community to be heard). The due date happens to be the weekend before the Drupal Association’s board retreat and shortly before DrupalCon Rotterdam.

Anyways, please consider filling this out and/or sharing with other fellow Drupalists!

https://docs.google.com/forms/d/e/1FAIpQLSdgHEgx9QbutXygHlgxcJjgLn24gMQok2h2ujB9ePH_JpH9dg/viewform?usp=send_form

Hi everyone!

I'm a Drupal developer from Argentina and I'm considering starting to offer my services as a freelance developer, mainly working with clients from the US or other English-speaking markets.

I have 5+ years of hands-on Drupal experience, working with custom modules, content types, hooks/events, custom blocks, Layout Builder, Twig/CSS, SDC/Storybook, integrations, caching and performance optimization. I also have a broader Full-Stack background with React, Next.js, Node.js/NestJS, PHP/Laravel, Docker, AWS and CI/CD.

I've been working remotely with US-based teams, but most of my current work is through a company rather than directly with clients. So I'm trying to understand what the current freelance market looks like for Drupal developers.

A few questions for those of you already freelancing:

• What hourly rate would be reasonable for someone with my experience?
• What rates are you currently charging or seeing in the market?
• Is it realistic to get freelance work with basic spoken English but good written English, especially for remote work?
• How important is spoken English in your experience? Are most interactions with clients meetings, or is a lot of the communication done asynchronously through Slack/email/tickets?

I'm not necessarily looking to charge US senior rates from day one. I'd rather start with a reasonable rate, build some direct client experience and gradually increase it.

I'd really appreciate any advice or experiences you can share. Thanks!

I've been making Drupal sites for about 12 years, so it's rare that I get stumped when trying to figure out a good solution to a problem, but this one is tricky...

Okay so this is quite a big site (approx. 5000 nodes), with like 10 taxonomy vocabularies. One of them is Tags, with like 2000 tags.

And for almost all of those vocabs, the standard Taxonomy Term view (that appears on route /taxonomy/term/%) that appears on their term pages is just fine.

But for one of the vocabs - called Organisations - I need to use a different view. This view needs to have different fields and filters, and a different treatment for the Title override.

My first thought was to use a unique alias pattern (from Pathauto) to show those term pages at different URLs (e.g. /organisations/*), and then make the new view and make it show on the same route. However that doesn't matter, because the Taxonomy Term view shows on the route /taxonomy/term/%, so it applies to the Organisations pages no matter what I make their URLs / aliases.

And that Taxonomy Term view still applies even if I add a filter that excludes the Organisations taxonomy. In other words, the filter only reduces the results, but it doesn't affect whether the view is applied to that page or not.

Then I though perhaps I could make new pages for each organisation, then place block views on those pages to simulate the term fields and the grid of tagged content, similar to the other term pages. But this doesn't really work, because for those block views, they have to get their "contextual filter" value of the term ID from somewhere. The Taxonomy Term view just gets it from the URL, but with these new pages, the term IDs wouldn't be in their URLs (or I could put the ID in the URL, but that would look bad).

Do you have ideas on how to solve this in a practical way?

the Webflow Source announcement sent me back into Acquia’s Source CMS product guide.

it explicitly says "customers can’t modify the underlying Drupal code or install contributed modules".

I understand the deal: less maintenance responsibility, fewer opportunities to make a beautifully customized disaster.

buttttt Drupal’s flexibility is also why a lot of people chose it.

where does that tradeoff work for you?

for a straightforward marketing site, I can see the appeal. for a project with specific integration or editorial requirements, I’d want to know where the escape hatches are.

what’s the requirement that would make you say “managed SaaS is fine”... or immediately ask for the keys?

I covered the two Sources on my Headless show, but this is the part I’d rather hear from people building and maintaining Drupal sites.