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?

After 2 years of hard work we are confidently presenting the "new way to work" for (marketing) content creators in Drupal :)

We would love feedback from the community

Pantheon hosting is in its second day of having issues. I cannot access my dashboard. Curious if anyone has any insight into this.

TLDR;

Since I work on 3 Drupal environments (local, staging, prod) and each has a DB, every time I add a new block locally, then deploy to staging, it disappears. Of course, different DBs, different UUIDs, I get why this is happening. The block I have locally simply doesn't exist on staging, I need to go there and create it, add to the block layout, dump DB and do a config export from this DB, commit to the codebase and deploy again. Same with prod.

So around 10 steps and 4 deployments for adding a block to a Drupal website. How do you solve it? Simply ignoring block configs has obvious downsides.

More details

I add a new promo banner block locally → commit config → deploy to staging → block is gone because the UUID is different on staging. I then have to dump staging DB, re-export, merge the diff, redeploy. Then repeat the whole thing for prod. For a single block.

I know I could just throw `block.block.*` into config_ignore and call it a day, but that feels stupid - no git history, no rollback, one wrong click from me or teammates and the layout is broken on prod with no way to trace what happened.

My semi-idea

Ignore only the blocks that actually cause problems (views blocks, custom content blocks) but keep tracking structural ones like menus and branding.

Is this roughly what others do? Is there a cleaner solution I'm missing? Would love to hear how teams with a lot of blocks are handling this.

i was able to update and upgrade my sites with ai, before nobody could help....i spend several days on slack, messaging also dev of specific theme...no answer.....ai knew everything. I havent visited slack now for over a year. For like moderate tasks in drupal ai is winner....it knows aeverything about every little module and you save like 99 % of the time...it is just amazing..... it knows ddev, docker, upgrades....altering theme...you name it....this is a major thing, because people on slack ususally are not the most friendliest