🇺🇸United States @Kristen Pol

Wow, that's really nice!!!

I've gone through the Drupal AI Summit Paris slides and did some tidying up, but I'm not seeing an issue for that deck in particular. I do see Paul mentions it above.

kristen pol → created an issue.

kristen pol → created an issue.

I’ve listened and will follow up on the needs UX workflow diagram and documentation in the channel

Thanks 🙏 let me know if I need to do anything on this end

Marcus pinged the AI maintainers and asked them to chime in and approve/comment on this, and I'm happy for this move forward.

Watched the video from @littlepixiez and it looks great!

Thanks to everyone for the hard work!

I'll ask the team tomorrow at our weekly meeting

Thanks! I'm keeping this open until I catchup and watch it which will be by the weekend at the latest.

Related issue from Jamie:

📌 [DEMO] Brand and Style Enforcer Agent Active

Thanks 🙏

This might work well

Let’s add some folks on Wed during our sync

Putting in DA queue

kristen pol → created an issue.

Thanks, Yannick!

I'll post the ux meeting recording shortly and list to it :)

I officially asked the AI Initiative project maintainers with a deadline of last week and no one said they didn't want to opt-in so I'm officially asking to opt-in:

https://www.drupal.org/project/issues/ai_initiative →

We understand this will be potentially disruptive and we can't "go back" to the old issues once we cutover.

Thanks!

We are still working through the doc, but things are getting more clear.

Marking postponed for now based on the parent issue:

#3558401: Drupal AI UX Project Governance: Meta Issue →

Added child issue as this came up recently when reviewing AI strategy:

#3560667: Create a Drupal AI glossary for AI terminology →

kristen pol → created an issue.

We are still working through the doc, but things are getting more clear.

Hmm... still see these on 11.1.6... reopening

Warnings:

Theme hook username not found.
Theme hook responsive_image_formatter not found.

I don’t have any detailed feedback at this point but I want to say a huge thanks to you and Emma for taking this on because it’s so important! Beautiful work 🙏😍🙏

Thanks! Here’s the slack thread for historical reference which has some other examples

https://drupal.slack.com/archives/C5ABFBZ5Z/p1764093499328319

Thanks 🙏

These look good. Briefly discussed with Aidan+Emma today on our call. We will be updating the master doc week and we'll have another meeting either Friday or early next week.

Had a good call with Aidan+Emma and we are making good progress... doc will be updated this week and we'll have another meeting either Friday or early next week

Had a good call with Aidan+Emma and we are making good progress... doc will be updated this week and we'll have another meeting either Friday or early next week

I'm working on a roadmap doc that covers the redesign/rearchitecture and working through it with Aidan/Emma/Marcus/Jamie/Ted.

Hope to have something next week to open up to the wider community.

I'm working on a roadmap doc that covers the redesign/rearchitecture and working through it with Aidan/Emma/Marcus/Jamie/Ted.

Hope to have something next week to open up to the wider community.

Updated the issue summary with a link to the slack discussion where this idea started.

IMO it’s important to give recognition when someone suggests something in slack but someone else creates the issue

I had a good call with Aidan about this role (during a call about other stuff) and I’m good with it

There’s always the opportunity to add others if it makes sense or to split responsibilities

Similar to Emma/Cristina sharing the core role

I think it’s useful to understand how that Drupal core UX Manager role came about:

📌 Add UX Manager as a new core maintainer role Active

Fantastic! Okay… these can be reviewed to see what issues to makes where :)

contribution record is updated and Aidan can paste his notes when he's read

Yannick gathered the attendees names for me ❤️

Aidan Foster
Emma Horrell
bbruno
Kristen Pol
arianraeesi
yannickoo

which translates to:

afoster, bbruno, emma horrell, kristen pol, arianraeesi, yannickoo

I've updated it to include the global context info

I've reviewed, updated, tested, and merged:

✨ Create a global context Active

so it's in place for the redesign/rearchitecture work even though it may not remain as a concept

I'll update the doc

I've reviewed, updated, tested, and merged:

✨ Create a global context Active

so it's in place for the redesign/rearchitecture work even though it may not remain as a concept

Tested thoroughly and will merge this despite the rearchitecture:

🌱 [META] CCC rearchitecture and roadmap Active

Tested with new global context and no "always include" context

Global context:

when creating content for components, add the word "AI-Driven"

Prompts 3 & 4:

update the title and meta description for my page

update the page title to match my meta description (because it didn't update the title)

[images]

Results

Used AI-Driven in title and meta description and it doesn't have other context other than the components so the text is otherwise generic

[images]

Prompt 5:

create a page with these mercury components: 1) testimonial, 2) project, 3) webform

[images]

Results

Used AI-Driven in all components and it doesn't have other context, so the text is otherwise generic

[images]

Tested with v2025 demo repo and the default 3 "always include" context.

Global context:

when creating content for components, add the word "AI-Powered"

[image]

First prompt (from empty page):

add a project component to my page

Results:

It filled in the page title and metadata and added "AI-Powered"

[image]

Second prompt (from empty page):

create a page with these mercury components: 1) testimonial, 2) project, 3) webform

Results:

It added the testimonial, project, and webform, and added "AI-Powered" in the text for the first two

[images]

Follow up issue to keep in mind:

#3559504: Toggling between AI Context local tasks losing content →

kristen pol → created an issue.

Moving to the DA queue

Also added tracker info to most issues and updated the issue summary template

adding tracker info

kristen pol → created an issue.

Since this is a "discussion" item, moving back to active.

Needs to be considered as part of rearchitecture:

🌱 [META] CCC rearchitecture and roadmap Active

Part of 🌱 [META] CCC rearchitecture and roadmap Active

Postponing until we've prioritized in the roadmap and defined the new architecture:

🌱 [META] CCC rearchitecture and roadmap Active

These notes are getting bubbled up into:

🌱 [META] CCC rearchitecture and roadmap Active

Notes are here:

📌 Research AI Context categories Active
📌 AI Context 1.0 roadmap for Drupal CMS 2.0 Active

Further discussion will happen as part of these and this:

🌱 [META] CCC rearchitecture and roadmap Active

I also did a quick manual test of creating context, editing context, changing settings, and changing pool configuration before merging.

Thanks!

Ignoring the last item from Cursor given the property is defined in EntityForm: https://api.drupal.org/api/drupal/core%21lib%21Drupal%21Core%21Entity%21...

I'll merge this.

Updated import/use statements to be alphabetical.

Here's Cursor's assessment:

Checking for linter errors and reviewing doc blocks and coding standards.

## Code review summary

### Linter status
- No linter errors found.

### Doc blocks
- All classes have class-level doc blocks.
- All public/protected methods have doc blocks with `@param` and `@return`.
- Properties have doc blocks with `@var`.
- `{@inheritdoc}` is used correctly for interface implementations.
- Doc blocks follow Drupal standards.

### Coding standards
- All files include `declare(strict_types=1);`.
- Classes are marked `final` where appropriate.
- Type hints are used consistently.
- Constructor property promotion is used correctly.
- Namespaces are properly declared.
- Consistent formatting and spacing.

### Minor observation
In `AiContextForm.php` (line 26), `$this->entityTypeManager` is assigned but not declared in the class. This is likely fine if inherited from `EntityForm`, but consider declaring it explicitly for clarity.

Overall, the code looks clean and follows Drupal coding standards. The PR appears to have addressed doc blocks and coding standards effectively.

I've reviewed and noticed a couple minor things I'll change and then I'll run it through cursor as well.