🇺🇸United States @Kristen Pol

This is still an issue... also can't click on the card when it's in there to get its properties.

You have to use Layers to get cards in place and edit properties.

https://github.com/phenaproxima/xb-demo/pull/68

done

https://www.drupal.org/project/demo_design_system/releases/1.0.5 →

I'll create a PR for xb-demo for this

kristen pol → created an issue.

While CKEditor is working, it is hijacking the styles, so that the theme (light/dark) and style props aren't working... so something else is needed

whoops

fixed

kristen pol → created an issue.

Follow-up:

📌 Make paragraph field support limited HTML to demonstrate CKEditor Active

kristen pol → created an issue.

After I went to the enabled component list, they showed up so closing this

Does that branch help this issue get back into scope?

I read the subject in the queue and knew exactly who must have filed this issue :D

I updated the docs and everything seemed to install fine but the SDDS components are not showing up in XB so I've pinged the Slack channel to see if anyone has any thoughts

Weird... when I deleted the code component, it shows the placeholder text... hmm

Previously, I had MOVED the code component into the regular components area, and I swear it didn't show anything

remove XB patch step

kristen pol → created an issue.

I’m not opposed to the logo… it just doesn’t feel like “Experience Builder” to me… but not sure what would. I’m NOT a designer:)

The starshot-paragraph component is another good one where this could be added

Oh... haha:

https://twig.symfony.com/doc/3.x/filters/striptags.html

You can also provide tags which should not be stripped:

{{ some_html|striptags('<br><p>') }}

That is not obvious DX :D

Okay... then this seems fine. I'll merge

I see this is the correct information in the yml as noted here:

https://www.drupal.org/project/experience_builder/issues/3519135#comment... ✨ Use CKEditor 5 for text area prop's example form element in code editor, adjust prop shape sent to backend Active

I don't understand the striptags though... you are stripping out all the links and bold and such? Doesn't this defeat the purpose of the CKEditor area? Or maybe I haven't had enough caffeine yet

Thanks 🙏 It’s very clean but I’m not sure it’s clear what it represents. I’ll wait for others to chime in

griffynh → credited kristen pol → .

This has been merged for both 1.x and 2.x

Tested on D10 on 1.x branch and one thing I noticed (which is probably still an issue for D11/2.x too)... if you have it set to push unpublished content, you don't get it because that setting isn't being honored in this code. But that's a separate bug, so we can handle it separately

I tested on D11 with translated unpublished taxonomy term without the patch and the term was pushed to quant.

On D11, when testing without the changes, the unpublished translation doesn't get pushed over, but this error shows up in the logs:

Path: /af/node/12. Symfony\Component\HttpKernel\Exception\AccessDeniedHttpException: in Drupal\Core\Routing\AccessAwareRouter->checkAccess() (line 115 of /var/www/html/web/core/lib/Drupal/Core/Routing/AccessAwareRouter.php).

kristen pol → created an issue.

That’s from the demo design system

kristen pol → created an issue.

One thing that needs updating is probably changing Vienna2025 to just an “AI Initiative” tag so it’s easier to collect issues across projects

Will update by tomorrow

Assigning to Christoph for now

kristen pol → created an issue.

fix issue number

minor rewording

add XB and add tasks

minor formatting

minor rewording

minor rewording

kristen pol → created an issue. See original summary → .

Removing "community" based on call today... the focus isn't necessarily just internal within the community, but also potential users who are outside the community

kristen pol → created an issue.

kristen pol → created an issue.

The PR needs to be updated based on my comments in GitHub

The code is updated so that Seed::seedNode() uses the translated entity in two areas, so that the correct entity data is available, e.g., published status:

• quant_cron_cron
• NodeItem::send

To test the first, we need to use cron like:

1. Do not sync upon content edit
2. Translate a node and make it published
3. Look in Quant and the content will be missing
4. Run cron and it will show up in the dashboard
5. Repeat with the translation as unpublished and you won't see the content in dashboard after running cron
6. Change the quant settings to sync unpublished content and run cron again and then it will show up in the dashboard

kristen pol → created an issue.

kristen pol → created an issue.

kristen pol → created an issue.

Thanks. @phenaproxima. This is very helpful!

Done

https://www.drupal.org/project/demo_design_system/releases/1.0.4 →

Part of new release:

https://www.drupal.org/project/demo_design_system/releases/1.0.4 →

kristen pol → created an issue.

Merged and checked it's not used elsewhere and it's okay

Before

./src/Settings/CivicthemeSettingsFormSectionBase.php:use Drupal\Core\Messenger\Messenger;
./src/Settings/CivicthemeSettingsFormSectionBase.php:   * @param \Drupal\Core\Messenger\Messenger $messenger
./src/CivicthemeConfigImporter.php:use Drupal\Core\Messenger\MessengerInterface;
./src/CivicthemeConfigImporter.php:   * @param \Drupal\Core\Messenger\MessengerInterface $messenger

After

./src/Settings/CivicthemeSettingsFormSectionBase.php:use Drupal\Core\Messenger\MessengerInterface;
./src/Settings/CivicthemeSettingsFormSectionBase.php:   * @param \Drupal\Core\Messenger\MessengerInterface $messenger
./src/CivicthemeConfigImporter.php:use Drupal\Core\Messenger\MessengerInterface;
./src/CivicthemeConfigImporter.php:   * @param \Drupal\Core\Messenger\MessengerInterface $messenger

Thanks! I'll get this merged shortly

I misunderstood this issue and thought it was for the initiative as a whole rather than just marketing. I had some minor feedback but put it in slack but I’ll try to edit this week when I’m back at my computer

lostcarpark → credited kristen pol → .

Thanks!

Postponing for now due to more pressing priorities

closing

Add credits

Moving to initiative

Moving this to the initiative

This was added as part of the AI initiative launch in June at drupal.org/ai (along with subpages)

Now that drupal.org is being used for pages for AI content, we don't necessarily need this

Documentation issue:

📌 Document new AI issue management process Active

kristen pol → created an issue.

Postponing for now due to more pressing priorities

Postponing for now due to more pressing priorities

Ones that I had proposed before in various docs are webinars on:

• Roadmap
• Funding
• Contribution
• Marketing
• Regular status updates (monthly)

This is better for Paul as he's already running with this

Updated the top of the project to point to /ai along with this project, the AI core project, and the AI ecosystem list.

Follow-up issue:

📌 Create AI contribution landing page under the d.o/ai navigation Active

@pdjohnson please provide any thoughts on this and then assign to Matthew for thoughts and then it can go back to me

kristen pol → created an issue.

I've done the first round of issue cleanup... there can be more done, but it isn't a priority:

https://www.drupal.org/project/issues/search/ai?project_issue_followers=... →

I've discussed where the new docs should live with Marcus, and we've agreed they should be part of the existing docs in GitLab:

https://project.pages.drupalcode.org/ai/1.1.x/contribute/

Note that to add images, you have to add them to the wiki first:

https://git.drupalcode.org/project/ai/-/wikis/home

which requires special access

An example docs page with an image:

https://project.pages.drupalcode.org/ai/1.1.x/agents/orchestration/

unassigning

unassigning

unassigning

unassigning

unassigning

unassigning

Change component

Change component