🇬🇧United Kingdom @dunx

I added a few comments mainly on capitalisation of some of the bullet points.

I made some clarification comment(s). Nice work.

Light review. Some small suggestions made in comments.

Same same. The document referenced in the spreadsheet is the empty template, but given it's the example page, are we supposed to be reviewing that?
https://new.drupal.org/node/11423303

Will did this one. I just did a quick review.

Forgot to update the ticket when I did the original work on this!

Forgot to update the ticket when I did the original work on this!

Forgot to update the ticket when I did the original work on this!

I'm in the process of finding images for the 4 pages that Zoocha has authored:

1. Healthcare & Life Sciences
2. Retail & ecommerce
3. Travel
4. Sport and Entertainment

I'll chase a reply via Slack.

Commenting as requested.

I've been discussing this with Rafa elsewhere and she's correct that to be totally GDPR compliant you need to be able to log how approval was requested and how it was obtained. The tricky bit is working out what you can store in this log to ensure you remain GDPR compliant!

Klaro's paid for versions include managed consent records and ChatGPT tells me the following:

Klaro supports a mechanism for recording users’ consent decisions so that the site owner can demonstrate when, how, and for what consent was given (or declined) — an important requirement under GDPR (“accountability” principle).

Depending on how Klaro is configured (client-side storage, backend logging, or a hybrid), the consent records can include:

1. Consent decisions for individual services E.g. { "google-analytics": true, "openstreetmap": false, … }
2. Klaro config ID The identifier of the particular Klaro configuration (or version) used when the user made the decision
3. Type of consent decision action E.g. "accept", "decline", "save", etc.
4. Hostname / domain The site domain (or hostname) where the consent was collected
5. URL path / pathname The specific page path where the user made the consent decision
6. Client / user agent / version Some anonymous info about the client (browser or Klaro client version)
7. Cookie or localStorage storage The record is stored in a cookie or localStorage (by default, Klaro stores the consent decision in the browser)
8. Timestamp / digital signature / hash To ensure integrity and prove the record wasn’t tampered with, Klaro can cryptographically sign consent records with a timestamp and authenticated hash.

That list might be a good place to start.

dunx → created an issue.

Is that a font that Drupal uses? Doesn't look like anything obvious on the website and doesn't seem to match either the 'I' from https://www.dafont.com/zt-gatha.font or https://fonts.google.com/noto/specimen/Noto+Sans fonts from the brand guidelines.

It's nice and simple for sure.

There's a similar discussion ongoing in the private ai-initiative-sponsors channel (https://drupal.slack.com/archives/C09CGB95VPT/p1758013833878459 ), so it would be good to consider how the 'Founders', 'Gold' and 'Silver' tags could be added to the new logo or how it might be used to identify the 'Drupal AI Initiative' as well as a more general 'Drupal AI'.

Commenting as requested. I'll be jumping in asynchronously later this evening.

Just jumping in on #11... for example when the component is full CKEditor based. That is currently totally unusable in the sidebar for editors creating long form content. Obviously resolved for LB in https://www.drupal.org/project/layout_builder_modal → but this "depends what you're doing" approach is also cool.

Commenting as requested.

Nice video walkthrough - very helpful.

I know I was the first to suggest the option was added to the Operations drop down - and I like that it's there - but the 'AI Automator Run Order' tab now feels a bit weird. I haven't tried this myself, but can you also add new operators from that tab? I'm just thinking of how intuitive this interface would be for both seasoned and new Drupal admins, i.e. does it match other similar admin UIs such that it's consistent and intuitive. That feels a little like the Views UI where you can add a field to a View and then 'Arrange' the fields via another button.

As long as users can get to the options they need, having multiple ways of doing this doesn't seem like a problem to me. Nice work.

Commenting as requested. I do like the 5pm start for these meetings in the UK as I get to spend the last 30 mins of work and the first 30 mins of my evening organise our team contributions.

Commenting as requested. Trying to pass on relevant issues to our team to focus on during the week.

penyaskito → credited dunx → .

I just added 'Google Consent Mode v2' to the title. I'd been told there was an issue but was struggling to find it. Hopefully that's useful.

I like the suggestion. The first screenshot is nasty-long. As well as separating out the automators, a simple link from file Operations would be good.

Following orders to comment here from async meet over in Slack :)

Is this an enhancement we can/should be pushing towards CK Source? I don't know enough about adding plugins to know whether this is a common use case.

My first async meeting. Looking forward to getting stuck in.

Thanks for that additional information, which actually makes the situation worse for our purposes. That could even be manipulated to maintain credits within the last 3 or 12 months.

There is a single immutable point in time when the contribution credit is awarded and, as this is the contribution record feed, I am requesting a feature where that time is provided as part of the feed... and no problem if the answer is 'we can't/won't provide that'. That would make this feed really useful for our purposes and possibly others as we aim to turn more takers in to makers.

Hi. We've worked through this and the field_last_status_change does not match the date the credit was awarded.

Having a single credit awarded/earned/applied/recognised date is crucial for those partners wanting to accurately incentivise staff for earning credits within a calendar month. Without it, credits can be recorded for an individual within the month it was earned and the month the issue was marked as 'Closed (fixed)' (assuming that date will never get changed again after this final status change) unless we do a heap of manual cross-checking of issues against credits already attributed.

As the feed doesn't seem to include the issue status, it's not possible to create logic to lock down the award of a credit to a single point in time, i.e. the month the status changed to 'Closed (fixed)'.

As an example, the field_last_status_change is 10 July 2025 for dunx on issue https://www.drupal.org/project/project_browser/issues/3497651 🐛 Ally issues for Project Browser in gin dark mode Active , which is the date the issue was automatically closed. I was awarded that credit on 26 June as shown in the issue screenshot.

Could this feature request be re-opened as we would still very much like to be able to determine a single date for credit award within this really useful feed?

Separate system. Understood. Thanks for the info.

Nice one thanks.
Shall I raise a separate ticket for the weighting part?

dunx → created an issue.

dunx → created an issue.

Just moving this old request to the new module responsible for resolving it. Had been raised again the d.o website.

It looks like this will be implemented soon.
https://www.drupal.org/drupalorg/blog/the-new-contribution-records-system →

@jurgenhaus, for clarity the module does display a 'RobotsTxt module works only if you remove the existing robots.txt file in your website root.' warning on the status screen. I came here because this module is included in the SEO Recipe on Drupal CMS and there's not a lot a 'marketer' can do about that message.

Totally agree that the module should try to resolve the issue itself as already suggested.

D11.2 released and I'm not seeing a dashboard icon when installing Drupal CMS dev. Particularly bad when the menu is minimised as you have no idea there's even a menu item there.

Worth noting that when the menu is expanded, there is at least a space to the left of 'Dashboard' which is different from the original screenshots in this issue.

I spotted the same 'RobotsTxt module works only if you remove the existing robots.txt file in your website root.' warning on the status screen this morning when doing some work on a fresh install of Drupal CMS based on D11.2 with just the SEO Recipe installed.

Module description: Use this module when you are running multiple Drupal sites from a single code base (multisite) and you need a different robots.txt file for each one.
Why is this module even part of the SEO recipe, which is very unlikely to be running in a multisite configuration?

The easiest solution is to remove RobotsTxt from the SEO Recipe to Drupal CMS. Its inclusion generates a warning that the target audience of Drupal CMS may miss or be unable to easily deal with. Unless the module description is wrong and it has other uses I'm not aware of.

It may just be how you've written the issue description, but the robots.txt file needs to be in root, so 'site/robots.txt' is invalid.

dunx → created an issue.

Forgot to make the code change (that's an ex-dev for you!)... so all the above, plus the code change gives:

Which looks good to me. I reverted to light mode and that also still looks fine.

Steps to test, using ddev locally:

1. Installed last dev version of Drupal CMS.
2. Enabled dark mode in gin admin theme.
3. Visit project browser pages and click on a Recipe.

Still not accessible. Doesn't make any difference whether the Recipe is installed or not - that panel's text contrast is still very low.

My votes for

1. Will Huggins (zoocha-will)
2. Marine Gandy (Mupsi)

The original URL was displaying https://www.braintreepayments.com/ but linking to competitor site https://squareup.com/signup/

I've changed the link and text to https://www.paypal.com/us/braintree, which is where that https://www.braintreepayments.com/ URL now redirects.

dunx → created an issue.

Understood. It is getting increasingly difficult to know where to target issues. I'm looking at Drupal CMS to try and suggest improvements to that as a product, but it's a bit of a Frankenstein's Monster, with parts taken from all over.

I know Adam has already referenced :) but I raised this a week later with some suggested changes.
https://www.drupal.org/project/drupal_cms/issues/3508207 🐛 Updates and Update Extension tabs don't belong under Appearance Active
Exactly the same observations, but with my "I am a new marketer using Drupal CMS for the first time" hat on.

phenaproxima → credited dunx → .

dunx → created an issue.

dunx → created an issue.

I've never used Wordpress, but did come across this video linked from another article, that gives an ex-Drupal-and-now-Wordpress-developer's opinions on Drupal CMS. I found it quite interesting how much they seemed to like the new Drupal CMS interface. Some of the comments are also informative.

https://www.youtube.com/watch?v=NipyycdGPvw

dunx → created an issue.

dunx → created an issue.

Even AWS Lightsail is talking about Drupal 7 and 8 installation via Bitnami :|

https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-...
https://docs.bitnami.com/aws/apps/drupal/configuration/install-plugins/

If Drupal CMS is going to succeed, it needs to be as easily installed as Wordpress on "cheap" hosting.

This feels like a major blocker to uptake for me right now. Sure, I could probably get it working somewhere cheap as others already have, but we're Drupal experts. What about these marketers we're talking about?

I appreciate I'm not offering answers or solutions.

Can we get this merged?

You don't even need ddev config --project-type=drupal11 --docroot=web because ddev config --project-type=drupal --docroot=web will work as ddev recently changed the drupal alias from drupal10 to drupal11. We are assuming some ddev defaults here that ddev might change. I don't know what oversight or warning we might get of those.

I think --create-docroot is also now a default and I don't think it was before.

Related to https://www.drupal.org/project/drupal_cms/issues/3500075 📌 Test (and then possibly document) installing on shared hosting Active , but what about PHP version? A shared hosting provider might only offer PHP8.3 and Drupal Core 11.1 supports PHP8.4. What happens when PHP8.3 is no longer supported (by Drupal or PHP).

No action required, just a reminder that what works now might easily change. I'm not suggesting we re-enable that installation script, but a more intelligent installation script might be exactly what we need in the future to help more people install Drupal CMS more easily.

pameeela → credited dunx → .

A bit of feedback related to my secondary minor issue with the commands. The script I'd created to spin up Drupal CMS dev version was running composer require cweagans/composer-patches because usually I'm applying patches to test under the issue queue.

That was causing the Recipes browser to show a "View Commands" button rather than an "Install" button. If you click on a "View Commands" button, close the modal to see the Recipe browser and scroll back to the top, you'll see an error message displayed:

Unable to download modules via the UI: Problems detected related to the Composer plugin cweagans/composer-patches. The composer-exit-on-patch-failure key is not set to true in the extra section of composer.json.

If you add that config to the composer.json extra stanza, then "View Commands" is replaced by "Install". The same occurs if you don't require composer-patches in the first place too of course.

I was hoping that was why I wasn't seeing the other Recipes within the Installer, but no joy. However, it's now possible for me to install Recipes via the browser, so if the decision to remove them from the Installer was intentional, I'm more than happy for this to be closed as Working as intended and hope the above is useful to the next person. The change threw me that's all.

Thanks :)

dunx → created an issue.

Yes to the ideal world of @chrisatredfin :)

Do the Drupal Association have any bandwidth to speak to the any of the big cheap hosting providers to help us help them?

Many of them already say they can host Drupal, whilst still using the old Drupal 8 logo for example. Perhaps it's in their interest to be more proactive in this respect. They would also be doing some marketing for Drupal CMS in getting their solutions out in front of their massive user base

dunx → created an issue.

I'm seeing the same as you @pameeela. Four focusable elements when tabbing through:

1. Skip to content
2. Email field
3. Password field
4. Finish button

But... there is a visually hidden "Regional settings" between the password and button. This is on -dev. I don't know under what circumstances these are supposed to display and I know the language selection stuff has been removed. Again, I don't have context on that.

I'm using Chrome on Mac and that's not focusable for me, so perhaps a browser issue and we suspect rkoller was using Windows due to mention of High Contrast Mode is the parent ticket.

I raised this from somebody else's larger issue. Can anybody provide screenshots from Windows High Contrast Mode for this issue?

Sorry, I'm on a mac, so can't use Windows High Contrast Mode. Hopefully, some kind soul can provide some screenshots.

Great topic.

The three hosting providers being recommended by Drupal at https://new.drupal.org/drupal-cms/trial under the Ready to launch? Find a Drupal host heading (Acquia, Pantheon and Platform.sh) are very unlikely to be the sort of service that somebody who wants to knock up a quick website can afford. I know there's some free/time-limited options, but these are typically £$€100s per month, when users are probably looking for that per year. We risk putting new users off immediately and losing them very quickly and forever if they believe those are the necessary or typical costs for hosting Drupal CMS.

Four related issues (including this one):

1. https://www.drupal.org/project/drupal_cms/issues/3500771 🐛 Front-end Performance Suggestions (Via Google Lighthouse) Active
2. https://www.drupal.org/project/drupal_cms/issues/3479394 ✨ Add Google Lighthouse testing Active
3. https://www.drupal.org/project/drupal_cms/issues/3500770 📌 Aim For 100 in Google Lighthouse Scores Active
4. https://www.drupal.org/project/drupal_cms/issues/3481524 📌 CMS Benchmarking Active

Four related issues (including this one):

1. https://www.drupal.org/project/drupal_cms/issues/3500771 🐛 Front-end Performance Suggestions (Via Google Lighthouse) Active
2. https://www.drupal.org/project/drupal_cms/issues/3479394 ✨ Add Google Lighthouse testing Active
3. https://www.drupal.org/project/drupal_cms/issues/3500770 📌 Aim For 100 in Google Lighthouse Scores Active
4. https://www.drupal.org/project/drupal_cms/issues/3481524 📌 CMS Benchmarking Active

Four related issues (including this one):

1. https://www.drupal.org/project/drupal_cms/issues/3500771 🐛 Front-end Performance Suggestions (Via Google Lighthouse) Active
2. https://www.drupal.org/project/drupal_cms/issues/3479394 ✨ Add Google Lighthouse testing Active
3. https://www.drupal.org/project/drupal_cms/issues/3500770 📌 Aim For 100 in Google Lighthouse Scores Active
4. https://www.drupal.org/project/drupal_cms/issues/3481524 📌 CMS Benchmarking Active

Four related issues (including this one):

1. https://www.drupal.org/project/drupal_cms/issues/3500771 🐛 Front-end Performance Suggestions (Via Google Lighthouse) Active
2. https://www.drupal.org/project/drupal_cms/issues/3479394 ✨ Add Google Lighthouse testing Active
3. https://www.drupal.org/project/drupal_cms/issues/3500770 📌 Aim For 100 in Google Lighthouse Scores Active
4. https://www.drupal.org/project/drupal_cms/issues/3481524 📌 CMS Benchmarking Active

I've created 6 child issues with this as parent.

Point 1 https://www.drupal.org/project/drupal_cms/issues/3500930 🐛 Improve a11y of Drupal CMS installer - recipe checkbox contrats Active
Points 2 and 6 not raised as language selection no longer present.
Point 3 https://www.drupal.org/project/drupal_cms/issues/3500931 🐛 Improve a11y of Drupal CMS installer - focus clarity Active
Points 4 and 9 https://www.drupal.org/project/drupal_cms/issues/3500932 🐛 Improve a11y of Drupal CMS installer - missing focus Active
Point 5 https://www.drupal.org/project/drupal_cms/issues/3500935 🐛 Improve a11y of Drupal CMS installer - missing icons in high contrast Active
Point 7 https://www.drupal.org/project/drupal_cms/issues/3500933 🐛 Improve a11y of Drupal CMS installer - low contrast on buttons Active
Point 8 https://www.drupal.org/project/drupal_cms/issues/3500934 🐛 Improve a11y of Drupal CMS installer - buttons with poor focus Active

Hopefully I've included all the required info. I re-used the same images and alt text ;)

dunx → created an issue.

dunx → created an issue.

dunx → created an issue.

dunx → created an issue.

dunx → created an issue.

dunx → created an issue.

Steps to reproduce:

1. git clone https://git.drupalcode.org/project/drupal_cms.git
2. cd drupal_cms
3. ddev config --project-type=drupal11 --docroot=web --php-version=8.3
4. ddev start
5. ddev composer install
6. ddev launch

Skipped majority of config (no option to install SEO Recipe anyway).

Applied SEO tools recipe:

• This wasn't presented as an option on installation for dev, which confused me and it took a while (far too long in fact as the "commands" shown didn't work not matter what paths I was using under ddev) to figure out how to install it using the drupal script.
• I installed drush and from web, ran ddev drush recipe ../recipes/drupal_cms_seo_tools -v

View page source:

• Plenty of og and twitter tags present so recipe is installed.
• Both og:description and twitter:description are missing, presumably because they have null values before the patch.

Removed container, to start again, so repeated all of the above with the above recipe patched before I installed it.

View page source:

• Both og:description and twitter:description now have the vale "This is the home page of your new site. Start by editing this page, or creating new pages.".

All looks good to me.

For us Euro lot, it meant we were in a loop until the launch in the evening for us. Nice to see you launch it live though :)

"d.o" as in via the website if you'd come in via the press release. Was temporary and all resolved now of course.

@mrdalesmith that's a different issue on the page before you reach this one. I tested and made comments on that yesterday. This issue is not resolved by that solution. This issue should be re-opened.

Could easily become the longest issue queue ever ;)

I think getting the EOOTB/no/low-code tag in there would be beneficial. So here's mine...

Drupal Core pre-configured with best-in-class enterprise-grade solutions and smart defaults. Ready for content creators, designers, and marketers to build sites easily via a no-code AI-powered interface.

I can't see any changes in your fork, so I've not been able to install and test this. I'd very much like to see the Access Denied error resolved.

I've made some text change suggestions on that other issue 📌 Make selection of AI Provider clearer on module homepage Active , which just adds a new Warning message and doesn't address the Access Denied error.

If those suggestions are picked up, then perhaps your new message could read:

There are no AI providers available. Choose at least one AI provider module from those listed on the AI module homepage, add to your project, install and configure it here. Then update the AI Settings.

With links to:

1. "AI module homepage" to https://www.drupal.org/project/ai →
2. "AI Settings" to /admin/config/ai/settings

Steps to reproduce...

1. Install latest D11 Umami plus drush
2. Download admin_toolbar and key modules.
3. ddev composer require 'drupal/ai:^1.0.x-dev'
4. ddev drush en ai ai_translate key admin_toolbar admin_toolbar_tools -y
5. Create an Article in English.
6. Click translate tab.

I see an error message:

I click on the link in the error to /en/admin/config/ai/providers and the text there tells me to "Choose a provider from the AI module homepage, add it to your project, then install and configure it first."

I ignore the first instruction to "Choose a provider" and click on the link to "configure it first" instead, which goes to /en/admin/config/ai/providers

I see an Access Denied error.

Issue reproduced.

Let's install this fix...
ddev composer config repositories.ai vcs https://git.drupalcode.org/issue/ai-3499412.git
ddev composer require drupal/ai:3499412-no-provider-warning-dev

Back at /en/admin/config/ai/settings I now see a new Warning message: "You have no AI providers enabled. Please install and enable a provider module."

This is an improvement as it makes it clear you have an immediate issue you need to deal with.

I think clarity would be further enhanced by changing the second sentence shown on screen from:

Choose a provider from the AI module homepage, add it to your project, then install and configure it first.

to

Choose at least one AI provider module from those listed on the AI module homepage, add to your project, install and configure it. Then update the AI Settings on this page.

There's some related chat over at https://www.drupal.org/project/ai/issues/3499412#comment-15944839 📌 Make selection of AI Provider clearer on module homepage Active too.

Text at #2 is perfect.

I think the other issue was discussed at https://www.drupal.org/project/ai/issues/3498757#comment-15939611 🐛 Installation/configuration resilience (ai_translate) Active , which you pointed to an existing ticket at https://www.drupal.org/project/ai/issues/3498887#comment-15944828 ✨ Add useful message on providers page when no provider enabled Active

I'll try to test that patch and the above patch today.

I raised the same issue over in https://www.drupal.org/project/ai/issues/3498757#comment-15939611 🐛 Installation/configuration resilience (ai_translate) Active , so I'm in a position to test this patch later today.

dunx → created an issue.

I had a similar issue installing a patch to project_browser yesterday. Full steps at https://www.drupal.org/project/project_browser/issues/3498901#comment-15... 🐛 Recipe description appears twice in modal Active

Error was

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/drupal_cms_starter 1.x-dev -> satisfiable by drupal/drupal_cms_starter[1.x-dev].
    - drupal/drupal_cms_starter 1.x-dev requires drupal/project_browser ^2-alpha7 -> found drupal/project_browser[2.0.0-alpha7, 2.0.x-dev] but it conflicts with your root composer.json require (3498901-recipe-description-appears-dev).

@wouters_f you said "What you're describing has nothing to do anymore with the ai_translate module. You can't configure providers that you haven't installed so the 404 makes sense in some way."

Where should I raise this access denied issue then if it's not against this module?

It's not a 404, it's an access denied. But I hear you. Happy to make some improvement with the first issue and much appreciated of course.
I can raise the second issue separately.

Will update this to RTBC.

Okay, I tried this:
ddev composer require drupal/project_browser:"dev-3498901-recipe-description-appears as 2.0.7-alpha7" (Thanks the_g_bomb)

A quick refresh and now the Recipe modal looks like this:

Looks fixed to me so another for RTBK.

Tested on drupal_cms dev.

Steps using ddev to reproduce:

1. git clone https://git.drupalcode.org/project/drupal_cms.git
2. cd drupal_cms
3. ddev config --project-type=drupal11 --docroot=web --php-version=8.3
4. ddev start
5. ddev composer install
6. ddev launch

Followed be skip of available recipe installation and minimum setup.

Visit project recipes page at /admin/modules/browse/recipes and then click on a recipe.
The *modal* looks like this:

Applied patch:
ddev composer require 'drupal/project_browser:2.0.x-dev'
ddev composer config repositories.project_browser vcs https://git.drupalcode.org/issue/project_browser-3498901.git
ddev composer require drupal/project_browser:dev-3498901-recipe-description-appears

Hmmm... MR not applying:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/drupal_cms_starter 1.x-dev -> satisfiable by drupal/drupal_cms_starter[1.x-dev].
    - drupal/drupal_cms_starter 1.x-dev requires drupal/project_browser ^2-alpha7 -> found drupal/project_browser[2.0.0-alpha7, 2.0.x-dev] but it conflicts with your root composer.json require (3498901-recipe-description-appears-dev).

Is that an issue with the MR or (more likely I'll happily admit), a problem with me?

Tested on drupal_cms dev.

Steps using ddev to reproduce:

1. git clone https://git.drupalcode.org/project/drupal_cms.git
2. cd drupal_cms
3. ddev config --project-type=drupal11 --docroot=web --php-version=8.3
4. ddev start
5. ddev composer install
6. ddev launch

Followed be skip of available recipe installation and minimum setup.

Project recipes page at /admin/modules/browse/recipes currently looks like this:

Ah, looks like this is already fixed in dev! Well, I'll leave this here just in case. Nice work. Looking forward to the launch party in London tomorrow :)

Testing this issue with the patch at the above issue:

1. ddev composer config repositories.project_browser vcs https://git.drupalcode.org/issue/project_browser-3499406.git
2. ddev composer require drupal/project_browser:dev-3499406-fix-fallback-logic

Unfortunately didn't fix anything for me.

I've just raised https://www.drupal.org/project/project_browser/issues/3499630 🐛 Some mandatory parameters are missing ("source") to generate a URL for route "project_browser.browse" Active which is a different error message experienced on a fresh D11.1 install, which looks to be related to project_browse.browse