Every time I come back to a Drupal project after working on other stacks,
there’s a short phase where everything feels… heavier than expected.

not necessarily bad just different:

• configuration layers
• content types + fields + views
• hooks / services / structure

but after spending some time with it, things start to click again and the flexibility becomes clear.

it made me wonder

is Drupal actually complex by nature,
or does it just feel that way because you need to stay “in its ecosystem” consistently to be comfortable with it?

especially compared to tools where you can jump in quickly after a break.

curious how others feel
does Drupal complexity go away with regular use,
or is it just part of the system regardless?

Drupal 7 EOL hit in January and I've seen a lot of teams scrambling. Put together a step-by-step guide covering:

- Content type and node mapping
- Field migration with TypeScript
- Media and file handling
- Taxonomy migration
- Go-live checklist

Hope it helps someone: cosmicjs.com/blog/migrate-from-drupal-to-cosmic

Building an AI-assisted module with open-source AI-Task-Manager.

Hey guys,

somehow my content looks kind of weird since a few days. The gaps between the text got less and I can't edit the text directly in the cms.

I get this error "Your site doesn’t include support for the "core/group" block. You can leave this block intact, convert its content to a Custom HTML block, or remove it entirely."

In the system tab it says that there are updates available. The problem is I'm an SEO and my client thinks I've breaked the page even though all I did, was changing the CMS content. (Text and Internal Links)

Could this have been caused by me? Or is this a deeper problem.

Just published a contributed module on drupal.org for auditing Drupal projects:

https://www.drupal.org/project/audit

It analyzes your installation and gives you scored reports across different categories: module updates, security, cache, performance, SEO, fields, Views... with concrete recommendations in each one. It's built around independent submodules so you only enable what makes sense for each project.

The idea is that you install it, run the audit, and get a clear picture of what's wrong and where to focus. It works on any hosting, everything stays on your server, and most submodules are fine to run on production. The only exceptions are audit_phpstan and audit_phpcs, which do static code analysis and require dev dependencies so those are better suited for development or staging environments.

Curious how you currently handle audits across your Drupal projects and whether something like this would fit into your workflow or not. Any feedback is welcome.

I was using the gemini and gpt can upgrade drupal 7 to drupal 10 without problem, but it took lots conversations and times one command after one commands, if there is an agent that I can pass the login info for him to online automatically check and run the commands , that will save lots times without spending time on hundreds conversations and manually run the commands. anyone has experience on this ? I guess either there is way for this already or it won't be far by the tech today.

Maybe a dumb question but can any old schlub, like myself, push code to an issue fork to the fork's gitlab branch? There's an issue on a contrib module, and it has a patch that almost works. I made a small fix on my local that seems to completely fix it. I see the instructions on the issue page for pulling and pushing with git. Is that it?

I've been a long time Drupal dev, and I've always wanted to contribute back to the community but haven't been sure about the process.

Drupal site-builders rejoice! We currently have two major page building projects approaching production-maturity: Canvas and Display Builder.

In the first part of our hands-on article series we show you how to build a page layout and highlight the strengths and weaknesses of both solutions. If you ever wondered what is best for your next project but never had the time to do the testing yourself, this is for you. 🖖

Edit: Any feedback is appreciated!

Ciao a tutti 👋

sto lavorando a un progetto chiamato MieApp, pensato per chi vuole imparare ad usare Drupal per costruire web app senza saper programmare, cioè come un site builder puro.

Non è un progetto commerciale, ma un contributo alla crescita di Drupal, che uso da anni per scopi personali e lavorativi.

Il sito offre gratuitamente e senza registrazione una serie di mini guide pratiche, che passo passo suggeriscono come tradurre una necessità in un progetto Drupal, utilizzando una app di esempio che il lettore può anche veder girare dal vivo.

👉 Per ora è solo un abbozzo e mi farebbe davvero piacere avere un feedback, suggerimenti e critiche per migliorarlo e completarlo.

MieApp è qui

https://mieapp.bottasini.eu

Grazie 🤝

In a previous post I shared how I used Claude to create a Drupal website just by prompting and tweaking via the Drupal admin pages. Wasn't a perfect or the "Drupal way" of a website but it worked. Was mainly just twig files with raw HTML in there so most edits require editing the twig files.

BUT I took this workflow and had Claude analyze my AI Drupal site builder codebase to see what it was missing, and oh was it missing a lot. It filled in gaps I didn't even know about and was a lot better than me hammering and hoping.

After adding the workflow and testing/tweaking I finally got it to create a fully customized and working Drupal site running in DDEV!!

Then the easy part of porting it over to my web server to finally update a website I built in 2020 and hadn't touched it since. The final (and very basic) Drupal website is at: webdevday.com and my AI Drupal website will eventually be at drupod.com

I’ve been messing around with the new Drupal Canvas AI sub-module, but honestly, the layout output was driving me crazy. It felt like it was just guessing where things should go and ignoring my design system.

I just stumbled on this step-by-step video that explains the "Context" side of things. It shows how to actually train the AI using a coding agent to generate knowledge guidelines so it respects your component props and grids.

If you’ve been struggling with messy AI-generated pages in Drupal, this workflow is a game-changer:

It’s a quick watch but the part about the AI Context module saved me hours of manual tweaking.

​

Drupal's new marketplace is "certified partners only" during the pilot phase. The stated reason: ensure quality. The actual result: established agencies get first-mover advantage, small builders dont get invited to the ball.

Also, the marketplace seems like a gray area with the GPL. How are premium themes compatible, are the GPL parts contributed back to the community?