Jamie to review
Thanks! It would be great to add Paul as well even if Matthew is driving this :)
valthebald → credited kristen pol → .
It's been uploaded.
I created this and am reviewing it with the team.
kristen pol → created an issue. See original summary → .
Thanks!
It's close :) Some minor tweaks are required to make sure our numbers and included sponsors are correct.
Thanks.
It's close :) Some minor tweaks are required to make sure our numbers and included sponsors are correct.
Adding credit for work
Note that this is a follow up from Slack conversations.
Thanks for creating.
I don’t have strong opinions on this. Mainly it would be great to be able to categorize and search all recipes or agents or prompts easily.
Missed a word :)
Re-scoping this per Jamie's feedback.
I find many of the track names to be too wordy IMO, but I did a first draft. I tried to keep things to AI + 1 or 2 words for the most part:
Tracks
- Landing Page Builder
Tag =AI Landing Page
- Experience Builder AI Agents
Tag =AI XB Agents
(name changing any day now plus we use XB modules and AI component) - AI Framework Improvements - Review Agents + Looping
Tag =AI Review Loops
- AI/ Agent Testing
Tag =AI Agent Testing
- AI Ecosystem UX
Tag =AI Ecosystem UX
- AI Trial Experience and Hosting Infrastructure
Tag =AI Demos
(hosting should be separate IMO and we are calling these demos rather than trials) - AI System Monitoring and Logging
Tag =AI System Monitoring
- AI Agent Workflow Logging
Tag =AI Workflow Logging
- Views Agents
Tag =AI Views Agents
- MCP + Tools API
Tag =AI MCP and Tools API
- ECA Integration
Tag =AI ECA
- Agentic Search
Tag =AI Agentic Search
- AI Content Suggestions (AI Field Widget and CK Editor Interface into AI)
Tag =AI Field Widgets???
(people didn't understand content suggestions so what are we calling this?) - AI Image and Media Agents
Tag =AI Media Agents
- Brand Guide (Visual/ Design)
Tag =AI Brand Guide
- Accessibility Advocate
Tag =AI Accessibility Advocate
- Agentic Powered AI Search Wizard (Talk to your Data Agent)
Tag =AI Search Wizard
- AI Hosting Requirements
Tag =AI Hosting
- Brand Compliance Agent (text)
Tag =AI Brand Compliance
(HOW IS THIS DIFFERENT THAN BRAND GUIDE?) - Navigation Curator
Tag =AI Navigation Curator
- Content Crafter
Tag =AI Content Crafter
- SEO Optimizer
Tag =AI SEO Optimizer
[IS THIS NOT AN AGENT?] - SEO Agents
Tag =AI SEO Agents
- Form Designer
Tag =AI Form Designer
- Visual Assistant
Tag =AI Visual Assistant
- Bring Your Own Agents
Tag =AI BYO Agents
- Role Master
Tag =AI Role Master
- Audit Trail Agent
Tag =AI Audit Trail
- Approval Architect
Tag =AI Approval Architect
- Smart Content Tester
Tag =AI Smart Content Tester
- Demand Driver
Tag =AI Demand Driver
- ABM (Account-Based Marketing) Accelerator
Tag =AI ABM
- Campaign Strategist
Tag =AI Campaign Strategist
- Automation Architect
Tag =AI Automation Architect
- AI Governance Framework
Tag =AI Governance Framework
- Version Vault
Tag =AI Version Vault
- Custom Drupal CMS AI Agent
Tag =AI Custom CMS Agent
- GraphRAG - AI (Content Librarian)
Tag =AI Content Librarian
- Global Voice Agent
Tag =AI Global Voice Agent
- Hyper-Personalization Engine
Tag =AI Personalization
- Project Browser and AI
Tag =AI Project Browser
- Fact Finder
Tag =AI Fact Finder
- Site Shaper
Tag =AI Site Shaper
/li> - Policy Protector
Tag =AI Policy Protector
Workstreams
- Workstream 1A: Smart Content & Page Creation: Foundational - Tag =
AI Workstream 1A
- Workstream 1B: Smart Content & Page Creation: Compliance - Tag =
AI Workstream 1B
- Workstream 2: Human Control Center: Focused on Experience Builder - Tag =
AI Workstream 2
- Workstream 3A: Performance Intelligence: In-Browser PoC - Tag =
AI Workstream 3A
- Workstream 3B: Performance Intelligence: Automated - Tag =
AI Workstream 3B
- Workstream 4: Toolbox - Tag =
AI Workstream 4
I talked with Jamie and he wants to simplify this to just a tag per track and a tag per workstream so I'll do that.
And, to be clear, much of this work has been in discussion since last year and some progress has been going on behind-the-scenes since June.
Cleaned up the summary typos/formatting a bit.
Jamie and I will be driving this to support contributors from Salsa+QED42+Axelerant
Thanks, everyone
and Pierre
and lenny :)
added participants
Other approach is to just try to use any generic tags that exist already in conjunction with AI Initiative
, e.g. views, accessibility, media, etc. I haven't checked what exists yet.
I took a peek and it looks amazing 🤩
I've added suggestions and comments on the business requirements doc
Since that goes beyond just the d.o page, we could have multiple issues:
- Defining requirements
- Create form, email template, and d.o page
- Promote demo page with blog post
Draft is here:
https://docs.google.com/document/d/1jqrd8F2jyaz2ykeFuwXgS41OWhPt-n9d5V45...
@pdjohnson This isn't in the format that you use
I've reviewed and suggested some minor tweaks
Promo video is here: 📌 Create Drupal AI Vienna session promo video Active
Promoted on LinkedIn and via Slack channels.
https://www.linkedin.com/feed/update/urn:li:activity:7362173410522673152/
Thanks!
This is still assigned to Luca but is RTBC.
I assume it be assigned to someone else since he wrote much of the code?
unassigning
unassigning
unassigning
unassigning
unassigning
Blog post: 📌 AI Initiative Off Site blog Active
Thanks, everyone!
kristen pol → created an issue.
unassigning
unassigning
Cross out issue summary task
unassigning
I did a pass on the draft.
It's generally fine, but Grammarly had some minor suggestions, so I did some nitpicking.
Feel free to disregard these.
More importantly, I added a note on the part I could help present if it makes sense.
valthebald → credited kristen pol → .
Nice analysis! Including "AI" makes sense :)
Marcus might be on this one as well
kristen pol → created an issue.
remove parent
kristen pol → created an issue. See original summary → .
This is also with Frederik
kristen pol → created an issue.
This one is with Frederik as well
kristen pol → created an issue.
Marking postponed for now as we should do this right before the event.
kristen pol → created an issue.
I reviewed the script and it looks good!
Happy to do other reviews if necessary and, of course, repost/promote.
kristen pol → created an issue.
Can we not use "resource" when referring to people please? :)
Any substantial tasks can be spun out into child issues if you'd like.
And adding parent
Not sure :) but adding some more context for when we are looking at the queue list
I think this one can be repurposed and closed out. This is now part of the regular marketing activities.
Generally, we are planning one webinar per month and figure out the topic after the previous one is done :)
See process improvements:
📌 Improve Webinar Template Active
Update for findability
Assigning to Gábor as he's focused more on this side of things, though the rest of the team is helping define this as well.
Note that the details won't be public here because it needs to be a surprise :) But this is just to keep this on our radar.
I've done a first pass at tweaking wording (with suggestions of mostly as it didn't change meaning) and added various comments/suggestions. Back to Paul :) I'm happy to do a final pass at the end if it makes sense.
Lenny added some comments and I have done another round and closed off some comments I added for Val (passed them off via Slack instead)
I've updated my comment above but putting the info here too:
Please note that the PDF has been removed in order to update the details.
There will be a roadmap webinar in a couple of weeks, so the details will be shared then.
Sorry for the noise :)
Okay... I went over it pretty carefully. I made some tweaks which I did without suggestions and they didn't change any of the meaning of what was written.
There are only a small number of comments left which one requires buy-in from Dominique (the monetary amount tied to each FTE for the calculation).
The rest are ones that you can close off IMO.
Thanks!
Thanks. I’m time poor too 😆
updating tasks
Note that there is an issue to add an AI category for module categorization so that's a good thing
✨ Add a Module category called "Artificial Intelligence" Active
Doesn't help with orgs and people but does help with discoverability of ecosystem
Still need to find time to finish this :)
Although this is probably for Christoph, Paul is helping get this sorted for the webinar, so assigning to Paul for now.
Got feedback from Marcus awhile back but just need to do this
Changing title to fit with new focus
Here it is:
📌 [META] Link AI ecosystem modules to official AI core documentation Active
kristen pol → created an issue.
I think we should do the last item as a follow-up issue, so I'll create that.
Thanks, all! This is enough for us to get going :)
Now we just need to document this in a good place.
Nice proposal.
We should see if additional team members also want to be added as moderators.
If this is added, then it would be nice if we promoted anything that was promoted on LinkedIn to here as well.
Got permission from Matthew to close :) so repurposing this
Crediting Alan
Fix typo in summary
We talked about this at the last marketing meeting and it would be good if we had one or two people dedicated to this type of outreach and coordination.
I'd recommend that someone could ghostwrite this for Jamie if they jumped on a call with him for 30 minutes to talk about it.
This is still relevant, but people haven't had time to focus on it, unfortunately
We should decide if this is something that we will maintain going forward.
I'd argue that it would be nice to have something like this for ALL contributors sponsored by Drupal AI sponsors :)
Note, the comments previously assigned to Val were added to the #ai-contrib meeting this week.
I know the draft isn't ready, but I went through the doc anyway and added some comments/suggestions.
Thanks for the draft :)
I did a quick review, and suggest I do another round after tweaks are done.
In general, there are quite a number of long sentences that could be simplified and/or broken up.
That is a spam account and has been removed for removal ^
Update proposed resolution
We've decided on using the existing "priority" tag for now and see how it goes
kristen pol → created an issue.
I don’t see why this needs to wait further. The issue summary is clear and this is a no-brainer IMO
I need to switch gears the rest of the day so here's where I'm at... needs more thought and consolidation but happy to have others chime in
Note that we can also separate out the ones we will focus on now and which could be used in the future
I'm doing the analysis and will create a doc to gather comments.
Assigning to Gábor :)
matthews → credited kristen pol → .
kristen pol → created an issue.
griffynh → credited kristen pol → .
mradcliffe → credited kristen pol → .