It isn't quite as bad as when the codebase was switched to Symfony, but the Drupal project has just kind of abandoned it's core presentation system in favor of the new Canvas tool, and compatibility with the rest of the core seems like an afterthought. So now you have at least 3 competing display configuration solutions, which don't necessarily work together, or entirely work alone.

It's a situation entirely inline with Drupal's reputation: they couldn't just get it right, and now serious Drupal teams don't know which way to go in the ecosystem.

▲

talon8635 2 hours ago | parent | next [-]

It still is symfony…

▲

echelon 2 hours ago | parent | prev [-]

Does anyone need Drupal anymore? You can just Claude Code all kinds of shapes of software.

I don't see how Drupal or anything like it survive. These types of softwares seem fitted to 2006, not 2026.

▲

scottfalconer 2 hours ago | parent | next [-]

Using Claude to build things quickly is great - but once you hit a certain level of scale, or have a need for governed workflows & oversight, you're more or less going to want some sort of CMS. When that happens, you can either go it alone, or build on top of a lot of well discussed well thought through solutions to these sorts of problems that the Drupal community has dealt with for a couple of decades.

▲

liveoneggs an hour ago | parent | prev | next [-]

Claude still has to write software in a target language, often using an established framework, especially one with a lot of examples.

PHP is, in fact, exceptionally good as a language for creating websites.

	▲	scottfalconer an hour ago \| parent [-]
		also the best code is usually less code, and frameworks can be really helpful there.

▲

ChrisMarshallNY 21 minutes ago | parent | prev | next [-]

One of the best things about Drupal (years ago, when I used to write plugins and themes), was that you could completely customize the backend, as well as the frontend, and that was a good thing, if you have low-tech users that author content. I despise having to walk people through WordPress' backend.

But that rewriting the base system, every couple of years, was why I dropped it.

Nowadays, with LLMs, it may be time to look at it again...

▲

1shooner an hour ago | parent | prev [-]

>You can just Claude Code all kinds of shapes of software.

Drupal is used at large organizations with hundreds of sites, thousands of users, and multiple more-or-less coordinated development teams. It's actually a great target for agentic coding, because it has such a well-established internal API. It can definitely feel like an anachronism, but I think there are few projects that could replace some of it's use cases. It's the B-52 of CMSs.

	▲	tstrimple an hour ago \| parent [-]
		This is how I view it. If you're going to be hosting dozens or hundreds of sites having a consistent platform like this is important even if Claude Code is doing all of the implementation work. It has understood and workable flows for things like content approval, timed releases, etc. All the things people think about when they talk about "managing content" and for the most part organizations still want human in the loop, especially for gated approvals and auditability. If I'm thinking of building a single one off site, then yeah I'd probably opt to just let CC handle it without worrying about a framework which is overengineered for my current need. That's what I do with most of the personal projects I work on these days. But I do have a skill to build consistency around the parts that should be consistent for everything I host. Like package shape and types of hooks available for deployment. How sites are publicly exposed and DNS management.