Daily Digest
Daily Digest – 27 June 2026
2026 Capabilities Progress
- Page generation — UX meetings refined the canvas building interface with generation locks, visual feedback during page creation, and simplified model selection to balance quality and cost tradeoffs [3]. Translation workflow compatibility issues were identified and are under investigation [5].
- Context management — Significant progress toward beta 3 release on July 6: improved context listing with merged scope/use case columns and cascading filters [19][25], warnings for unpublished parent contexts [14][23], and work to inject context into rich text editor AI tools [15][22]. Community testing recruitment and QA preparation are underway [9][10][11][16][18].
- Background agents — No direct progress today.
- Design system integration — UX discussions covered canvas building progress, with the interface now providing visual placeholders during generation [3], though no code changes were in progress today.
- Content creation and discovery — Infrastructure work continues on vector database configuration validation to enable automated setup verification for search functionality [1][2]. A searchable directory of AI modules is being designed to help site builders discover content creation tools [4].
- Advanced governance — Context management now warns editors when sub-contexts have unpublished parents, preventing configuration errors [14][23]. Discussion continues on moderation status inheritance between parent and child context items [13].
- Intelligent website improvements — No direct progress today.
- Multi-channel campaigns — No direct progress today.
Shipped
- Context Control Center fixed code quality display issues — The project resolved errors that prevented code quality checks from displaying correctly in the version control interface [8][21].
- Context Control Center improved parent-child publishing warnings — Editors now see a warning when editing a published sub-context whose parent context is unpublished, preventing configuration errors [14][23].
- Context Control Center streamlined context discovery interface — The context listing page merged use cases and scope columns and replaced filters with a simpler two-dropdown design to help users find context items more quickly [19][25].
Ongoing
- AI module adding vector database configuration validation — A new automated check is under review to verify that at least one vector database provider is properly configured, reducing setup errors [1][2].
- Context Control Center preparing beta 3 release for July 6 — Quality assurance planning, codebase security and performance reviews, community tester recruitment, and release coordination are underway [9][10][11][16][18][20].
- Context Control Center integrating with rich text editor AI tools — Work is in progress to allow context injection into CKEditor AI requests, pending changes in a related module [15][22].
- Context Control Center aligning context item display format — The full view of context items is being updated to match the standardized entity display approach [17][24].
- Canvas investigating translation workflow failure — A critical error affecting translation job requests using the TMGMT module has been identified and assigned for investigation [5].
- Canvas consolidating repository structure — A substantial merge request with over 6,800 lines of changes is in draft to consolidate code into the Canvas repository [7].
AI (Artificial Intelligence)
The project saw continued development activity this period. Work is underway to improve configuration validation capabilities. Specifically, a new configuration action is being developed to verify that at least one vector database provider is installed and properly configured in the system, without requiring administrators to know which specific provider is present. This addresses a practical need: when setting up search functionality, the system currently cannot automatically detect whether any suitable database backend is ready, forcing users to manually verify setup details. The enhancement will streamline deployment and reduce configuration errors by allowing automated checks to confirm the environment is ready.
An associated merge request containing this functionality remains open for review. No code was merged during this period, reflecting ongoing development work typical for this stage of the module.
How can I help on this project?
- Ensure the team has access to code reviewers who can evaluate and merge open contributions in a timely manner.
- Clarify strategic priorities for upcoming releases to help contributors focus effort on the highest-value features.
Contributors: Artem Dmitriiev (a.dmitriiev)
Drupal AI Initiative
The Drupal AI Initiative held two user experience meetings during the period, focusing on interface design and ecosystem organization. The June 22 meeting reviewed progress on AI-assisted canvas building, where the interface now locks during generation to prevent editing conflicts and provides visual feedback through placeholder boxes and progress indicators. Quality and cost tradeoffs are being surfaced through a simplified model selection interface.
The June 15 meeting discussed a new searchable directory of AI modules and recipes designed to help site builders discover and evaluate tools. The directory will distinguish between initiative-maintained components and community contributions, with tiered support indicators to help users assess maturity and backing.
Both meetings signal ongoing work to make AI capabilities more discoverable and usable for non-technical site builders, which supports broader adoption of the initiative's deliverables.
How can I help on this project?
- Champion clarity on support tiers and maintenance commitments for AI modules to help users make informed decisions about which tools to trust in production.
- Ensure resources are available to maintain the ecosystem directory as a strategic onboarding tool for new adopters.
Drupal Canvas
Activity this period centered on issue identification and dependency maintenance. A translation-related issue was reported involving errors when attempting to translate content using the TMGMT module. The issue appears when requesting translation jobs and results in a system failure. The problem has been identified and assigned for investigation.
On the maintenance front, a dependency update was opened to bring accessibility testing tools up to date. This type of routine update helps ensure the module continues to work reliably with current versions of its supporting libraries.
A larger draft merge request remains in progress, representing ongoing work to consolidate code into the Canvas repository. This is a significant effort involving over 6,800 lines of changes.
How can I help on this project?
- Consider prioritizing translation functionality testing, particularly for organizations using multilingual content workflows, to prevent similar issues from affecting production environments.
- Ensure adequate resourcing is available to complete the repository consolidation work, which represents a substantial structural change to the project.
Contributors: **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Ben Mullins (bnjmnm)
Context Control Center (CCC)
The project made progress toward its beta 3 release, targeted for 6 July 2026. A new context listing page received user experience improvements: the use cases and scope columns were merged into a single column with ordered pills, and the filter system was replaced with a cascading two-dropdown design that makes it easier to find context items by scope. A warning now appears when editing a published sub-context whose parent context is unpublished, helping authors avoid configuration errors. Code quality checks were addressed, resolving display issues in the version control interface.
Preparatory work for beta 3 is underway: quality assurance planning, codebase security and performance reviews, and release coordination are in progress. The project is also recruiting community testers and updating onboarding materials with session videos, documentation links, and instructions for providing feedback. Integration work continues to allow context injection into rich text editor AI tools, though this depends on changes in a related module.
Three issues were closed during the period: Fix eslint errors in GitLab UI even when pipeline is green, Add warning on subcontext edit form if parent is unpublished, and UX improvements on new context listing page.
How can I help on this project?
Support community testing recruitment by promoting the beta program through your networks or allocating time for staff participation. Ensure the team has dedicated time in the week leading up to 6 July for quality assurance and release tasks. Consider prioritizing resourcing decisions that affect post-beta 3 planning.
Contributors: Jesse Hofmann-Smith (jessehs), Kristen Pol (kepol) [2], Matt Glaman (mglaman) [1]References
[1] Config action to verify if any vector database is there and it is setup
[2] Issue #3586517: Check if any Vdb provider is setup
[3] Drupal AI UX meeting 22 June 2026
[4] Drupal AI UX meeting 15 June 2026
[7] Draft: #3492065 move to canvas repo
[8] Fix eslint errors in GitLab UI even when pipeline is green
[9] CCC beta3 QA
[11] CCC beta3 codebase review (pre-release)
[13] [Discuss] Moderation status of subcontext vs parent context items
[14] Add warning on subcontext edit form if parent is unpublished
[15] Inject context into ai_ckeditor requests
[16] CCC beta / pre-rc1 community testing
[17] Align context item full view with bundle-less entity
[18] Add CCC beta tester info to the project page
[19] UX improvements on new context listing page
[20] Gather CCC contribution stats for code and non-code contributions for release notes
[21] Issue #3576093: Fix lint errors in GitLab UI even when pipeline is green.
[22] Issue #3581955: Add EventSubscriber to inject context into ai_ckeditor tools.
[23] Issue #3586297: Add warning on subcontext edit form if parent is unpublished.
[24] Issue #3586261: Align context item full view with bundle-less entity.
[25] Issue #3586274: Merge Use cases/Scope columns and add cascading scope filter
Shipped
- ai_context eslint errors fixed — Resolved lint warnings in GitLab UI that appeared despite passing pipelines [8][21].
- ai_context subcontext warning added — Form-level warning now displays when editing a published subcontext with an unpublished parent [14][23].
- ai_context listing page UX improvements — Consolidated Use Cases and Scope columns into a single Scopes column with cascading filters [19][25].
Ongoing
- AI module VDB provider verification — Config action to check if any vector database provider is configured without specifying plugin name [1][2].
- Canvas TMGMT translation WSOD — AssertionError on ComponentInputsMapping when requesting translation jobs with canvas_dev_translation enabled [5].
- ai_context CKEditor context injection — EventSubscriber to inject context into ai_ckeditor tool requests under review [15][22].
- ai_context beta3 release preparation — QA, codebase review, and release tasks underway for beta3 target 6 July 2026 [9][10][11].
- ai_context bundle-less entity alignment — Context item full view being updated to match bundle-less entity refactor [17][24].
AI (Artificial Intelligence)
Activity in the AI module over the past 24 hours focused on configuration validation improvements. Work continued on Config action to verify if any vector database is there and it is setup, which extends the existing verifySetupAi config action. Currently, the action can check for a specific vector database provider using the vdb_provider_is_setup payload, but cannot verify that any configured VDB provider exists without specifying a plugin name. The related MR !1660 remains open for review, adding this capability to support use cases where any properly configured vector database provider is sufficient for creating a Search API server.
No merge requests were merged and no commits were pushed during this period.
How can I help on this project?
- Review MR !1660 to provide feedback on the config action logic for detecting any configured vector database provider.
- Test the proposed changes against different VDB provider configurations to ensure the verification works as expected.
Contributors: Artem Dmitriiev (a.dmitriiev)
Drupal AI Initiative
The Drupal AI Initiative saw documentation and planning activity this period, with meeting notes published for both the Drupal AI UX meeting 15 June 2026 and Drupal AI UX meeting 22 June 2026. The June 22 meeting covered Canvas AI build-state UX improvements, including component-by-component generation with canvas locking during builds, build controls (stop and stop-and-undo), and a quality/cost/speed model selection dial. The June 15 meeting focused on the AI ecosystem page in the AI Dashboard module, which provides a searchable, filterable list of AI modules and recipes for site builders and developers, with plans to integrate GitLab API search to discover additional modules requiring drupal/ai.
No merge requests were merged and no commits were pushed during this period. Development activity appears focused on design and coordination work rather than code changes.
How can I help on this project?
Review the UX meeting notes to understand current design direction and join upcoming meetings to contribute to planning. Explore the AI Dashboard module code to help implement the GitLab API search feature for discovering AI-related modules. Test existing AI functionality and report bugs or UX friction points.
Drupal Canvas
A translation-related issue surfaced during the reporting period. When requesting TMGMT translation jobs with Canvas 1.7.0 on a fresh Drupal CMS Haven install, an AssertionError: assert(!$data instanceof ComponentInputsMapping) in assert() when requesting tmgmt translation job was reported. The white screen of death occurs with canvas_dev_translation enabled, and the issue appears related to how component tree and input settings are configured, though previous configuration options are no longer available. The issue remains open and under investigation.
On the dependency front, fix(deps): update npm minor and patch was opened to update @axe-core/playwright from 4.11.1 to 4.11.3 along with other npm package updates. Additionally, a draft merge request titled Draft: #3492065 move to canvas repo remains open with 6,856 diff lines, indicating a significant repository reorganization effort in progress.
How can I help on this project?
Review the open dependency update MR to ensure compatibility. Investigate the TMGMT translation assertion error by reproducing it with canvas_dev_translation and identifying which component configuration triggers the ComponentInputsMapping assertion failure.
Contributors: **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Ben Mullins (bnjmnm)Context Control Center (CCC)
Three merge requests landed during the reporting period, addressing UI polish and developer experience ahead of the upcoming beta3 release. Fix eslint errors in GitLab UI even when pipeline is green was merged to resolve lint warnings displayed in the GitLab test summary despite passing pipelines. Add warning on subcontext edit form if parent is unpublished was merged, introducing a form-level warning when a published subcontext has an unpublished parent, following discussion in the now-closed moderation status issue.
The most substantial change merged was UX improvements on new context listing page, consolidating the Use Cases and Scope columns into a single Scopes column with ordered pills, and replacing the standalone filters with a cascading scope filter mechanism. The first dropdown selects scope name (defaulting to All scopes), while the second dropdown dynamically filters values.
Preparation for the beta3 release (target 6 July 2026) is underway, with open issues for QA scripting, codebase review, and the release itself. An open merge request for Inject context into ai_ckeditor requests remains under review, introducing an EventSubscriber to bridge ai_context with ai_ckeditor's direct provider calls.
How can I help on this project?
Review MR !116 for ai_ckeditor context injection, which adds an EventSubscriber to handle scope-matched context items. Help finalize MR !198 aligning context item full view with the bundle-less entity refactor. Contribute to beta testing by following setup instructions and reporting findings.
Contributors: Jesse Hofmann-Smith (jessehs), Kristen Pol (kepol) [2], Matt Glaman (mglaman) [1]
References
[1] Config action to verify if any vector database is there and it is setup
[2] Issue #3586517: Check if any Vdb provider is setup
[8] Fix eslint errors in GitLab UI even when pipeline is green
[9] CCC beta3 QA
[11] CCC beta3 codebase review (pre-release)
[14] Add warning on subcontext edit form if parent is unpublished
[15] Inject context into ai_ckeditor requests
[17] Align context item full view with bundle-less entity
[19] UX improvements on new context listing page
[21] Issue #3576093: Fix lint errors in GitLab UI even when pipeline is green.
[22] Issue #3581955: Add EventSubscriber to inject context into ai_ckeditor tools.
[23] Issue #3586297: Add warning on subcontext edit form if parent is unpublished.
[24] Issue #3586261: Align context item full view with bundle-less entity.
[25] Issue #3586274: Merge Use cases/Scope columns and add cascading scope filter