fidzu : Drupal

To better serve smaller organizations and those in a budget crunch, we've launched Tiny Services.

30 Jun 2026 3:33pm GMT

Anxiety about AI

The Drupal and broader software community are getting overly anxious about the new kids on the block… AI. I wanted to step back and explore this anxiety through the analogy of AI as the new kids on the block, or, more specifically, the new kids entering our software teams and community. It is important to view AI not as a single kid because AI consists of multiple LLMs and harnesses.

Therefore, our immediate expectation when working with AI is that there is no single way to prepare for or interact with AI that always works across all AIs. The inconsistency and unpredictability of the current state of AI, and how it impacts our work, is making people anxious, which is leading them to want tools and processes to prepare to collaborate with AI. I'm writing this post because I think people's anxiety about AI is making them overprepare.

Overpreparing for AI

A large part of the AI narrative centers on the tooling you need to use AI. I feel that most of the AI tooling is overbuilt or overplanned. At the same time, harnesses like OpenCode provide essential tools and methodologies for an LLM to write code and perform tasks. Still, a harness is just a tool for AI, like the computer and software I am using to write this post.

The tooling and planning I am concerned about involve AI-specific processes for managing and orchestrating AI agents. Many people in the software community are developing AI best practices to address the challenge of integrating AI into our software development process.

A quick aside. I think having AI best practices for Drupal as a collaborative, community-led initiative is essential to Drupal's proper adoption of agent-driven development. Before someone starts using Drupal's AI best practices, they should understand what AI is.

What exactly is AI?

I don't know...Read More

30 Jun 2026 3:13pm GMT

Drupal Canvas AI gives content teams prompt-based speed, along with governance and brand control. Here is what it does and how to use it.

30 Jun 2026 11:21am GMT

Plenty of clients arrive with a system they see as a line item to keep cheap. The real job of an agency is to help them see what that same system could become - and why it is worth investing in.

See how a Drupal development partner relationship grows from minimal support into strategic investment - five readiness signals, quick wins that prove value, the account growth curve, and a ~24% conversion lift on one real account.

29 Jun 2026 6:38pm GMT

Today we are talking about Marketing, AI, and Drupal with guest Paul Johnson. We'll also cover Curated Colors as our module of the week.

For show notes visit: https://www.talkingDrupal.com/559

Topics

• Paul's Current Projects
• Enterprise AI Summit Details
• Marketing the AI Initiative
• Partnering on Event Booths
• Drupal's Outside Perception
• What's Working Now
• Growing the Marketing Team
• How to Contribute
• Outside In Storytelling
• Case Study Examples
• AI Initiative Impact
• Roadmap and Launch Planning
• Finding New Adopters
• Where Pros Research
• Conference Pitch Story
• Local Event Playbook
• Funnel and Webinars
• Industry Guides and Demos
• SEO and AI Search
• Why Agents Avoid Drupal
• High Leverage Contributions
• Measuring AI Mentions
• Vibe Coders to Governance
• Fixing Misconceptions

Resources

• Drupal AI Initiative home page
• Slack
  • #ai-initiative-marketing
• Enterprise AI Summit Rotterdam
• AI Dev Summit Rotterdam
• Drupal AI TV
  • We've curated a selection of the best presentations, workshops and demonstrations freely available to provide a practical way to stay informed about the latest innovations in Drupal AI.
• Drupal AI Webinars playlist
• Demos
• Ryan Whitcombe
• 1xINTERNET S1xSignals free AIO GEO assessment
• All things open
• World cancer day

Guests

Paul Johnson - pdjohnson

Hosts

Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Scott Falconer - managing-ai.com scott-falconer

MOTW Correspondent

Martin Anderson-Clutz - mandclu.com mandclu

• Brief description:
  • Have you ever wanted to allow editors on your Drupal site to choose styling from a brand-approved color palette? There's a module for that.
• Module name/project name:
  • Curated Colors
• Brief history
  • How old: created in Apr 2026 by Kyle Einecker (ctrladel) of True Summit
  • Versions available: 1.0.0 which works with Drupal 10.3, 11, and 12
• Maintainership
  • Actively maintained
  • Security coverage
  • Test coverage
  • Documentation - in-depth README
  • Number of open issues: 2 open issues, neither of which are bugs
• Usage stats:
  • 27 sites
• Module features and usage
  • Curated Colors enforces brand consistency by replacing generic color text inputs or wide-open color pickers with a curated, visual swatch popover containing only pre-approved, named options
  • It streamlines rebranding by storing abstract keys (such as brand-primary) instead of raw hex values (e.g., #0678be) in the database. That means updating a brand color in the future only requires a CSS or configuration change rather than a massive data migration
  • Curated Colors is also extensible beyond colors. It functions as a generic visual variant selector. Site builders can repurpose it to let editors pick card layouts, button styles (like primary, outline, or danger), hero text alignments, or icon themes
  • Editors can pick from neatly organized groups with human-readable labels and see a live preview swatch of their selection before saving
  • Palettes are managed as exportable Drupal configuration. Each entry maps a machine key to a label, administrative hex preview, and optional custom CSS
  • The module provides a curated_color field type and an accompanying swatch-based popover widget that can be restricted to specific palette groups. It also features a native curated_color_picker Form API element and integrates with the Canvas module via SDC annotations
  • The field exposes properties like value, hex, style, and css, making it simple to output selections as classes, inline styles, or raw codes in Twig templates
  • Finally, Curated Colors includes an example submodule providing a working SDC component and sample palette templates so you can see exactly how it's meant to be used

29 Jun 2026 6:00pm GMT

A full rebuild feels like progress. More often it is the most expensive, slowest, and riskiest way to solve a problem that proper implementation would fix in a fraction of the time.

A phased CMS modernization framework for CTOs and marketing leaders: true rebuild costs, when starting fresh is justified, four evolution phases, a decision checklist, and how to sell incremental change to stakeholders.

29 Jun 2026 5:47pm GMT

Imagen

Imagen

Carlos

Ospina

·

Technical Account Manager / Drupal Advisor

Imagen

Ana

Coto

·

Senior Web Developer

29 Jun 2026 3:57pm GMT

Artificial intelligence is posing a practical question to Drupal. If AI agents can help plan, build, inspect, and change websites, how easily can they work with Drupal when faster platforms are easier to start?

The Drupal AI Initiative made that question more explicit on 25 June 2026, when it split its work into two streams: Inside AI and Outside AI. Inside AI focuses on tools used within Drupal, including assistants, page-building, and in-product workflows. Outside AI focuses on agents and external tools that need to start with Drupal, connect to it, inspect it, change it, verify it, migrate into it, or launch it.

The shift matters because AI changes how platform choices are made. Human teams may choose Drupal for structured content, permissions, workflows, revisions, and long-term governance. An AI coding agent may judge the same platform by a shorter test: whether it can install, configure, understand, and verify a working site in one session.

Dries Buytaert tested that tension directly when he asked an AI coding agent whether it would recommend Drupal for a site-building task. The agent ranked Drupal third, behind a Next.js and headless CMS stack and WordPress. It did not say Drupal lacked capability. It said Drupal carried more "session-time risk" because setup, module selection, documentation, training data, and frontend choices made the first working session harder to complete confidently.

That is the useful problem for the community to address. Drupal's AI work cannot depend only on adding visible AI features inside the CMS. It also has to make Drupal easier for external agents and agent-assisted developers to understand, call, inspect, and modify without losing the controls that make the platform valuable.

TDT has also covered this from the workflow side. A report on Drupal orchestration primitives looked at how ECA, FlowDrop, Maestro, and Drupal core are being discussed through shared workflow terms such as triggers, steps, conditions, workflows, and runs. The unresolved question is data handoff: how work moves between Drupal tools, across workflow systems, and out to agents or external automation without breaking governance.

This is where Drupal's older strengths may become newly important. Revisions, moderation states, permissions, access control, structured content, multilingual architecture, and publishing review are not only CMS features. They are the controls that external AI systems may need when generated content, configuration changes, or workflow actions have to be checked before they reach production.

The test for Outside AI will not be the terminology. It will be about whether Drupal can reduce first-session friction that leads agents to choose simpler tools, while still giving organisations control over review, rollback, audit, and publishing. That means clearer documentation, faster setup paths, reliable examples, machine-readable interfaces, and real feedback from agencies and developers using AI in delivery work.

The curated story list for this edition follows the editor's note. Readers can also follow The Drop Times on LinkedIn, Twitter, Bluesky, and Facebook, or join the publication's Drupal Slack channel at #thedroptimes.

Kazima Abbas
Sub-editor
The Drop Times

29 Jun 2026 3:31pm GMT

The last remaining reason to compile your CSS has just disappeared.

CSS Style Queries have reached Baseline support across all major browsers, and they unlock something we've wanted for years: reusable, stateful design tokens that work entirely in native CSS.

The syntax

At its most basic, style queries allow you to add CSS rules to a nested element, based on a parent's CSS variable.

29 Jun 2026 12:29pm GMT

Our 36th monthly UI Suite meeting (June 18, 2026) was a packed one. Despite the early-summer heat in Paris and a few people already on holiday, the team walked through a string of releases, demoed a brand-new starter kit, and gave a first live look at AI agents building Drupal pages on their own. Here's everything that happened.

29 Jun 2026 9:30am GMT

For Drupal teams, emerging tools now touch page building, editing expectations, translation consistency, hosting choices, and debt management. Kortrijk speakers place those shifts inside practical project decisions.

26 Jun 2026 4:04pm GMT

Drupal's workflow tools are being described less as rivals and more as complementary layers. The open question is whether shared primitives can make them compose safely for AI-driven and human-reviewed work.

26 Jun 2026 11:05am GMT

Earlier this week, in "Drupal's role in agentic workflows", I argued that Drupal's AI future has two parts: helping people with AI inside Drupal, and helping agents use Drupal from the outside.

So we are splitting Drupal's AI strategy into two workstreams. Inside AI is led by Christoph Breidert, who has been driving that work already. Outside AI, the new workstream, is led by Scott Falconer.

The easiest way to think about the difference: with Inside AI, a person uses Drupal, and Drupal uses AI to help. With Outside AI, a person uses an agent, and the agent uses Drupal.

We launched the Drupal AI Initiative one year ago, in June 2025, with a published strategy. A year later it spans 32 organizations and more than 50 contributors, shipping against a public 2026 roadmap through two paid delivery teams.

So far, most of that work has focused on Inside AI, though much of the foundation also supports Outside AI.

Outside AI will serve three kinds of users:

• Developers new to Drupal. They ask an AI agent to build a website, and the agent chooses what to build on. Agents reach for whatever they can spin up in seconds, so the opportunity is to make Drupal that easy to install, configure, and use.
• Experienced Drupal developers. They already know Drupal is the right tool, and they want agents to take on more of the work. For Drupal agencies, Outside AI should turn AI into a stronger advantage: helping teams move faster, win more work, protect profitability, and get more value from their Drupal talent.
• External agentic systems and workflow automation tools. These systems coordinate work across many tools, but when they touch content, they need a trusted system of record for workflows, permissions, revisions, and publishing. Rather than rebuilding that governance elsewhere, they should call into Drupal.

If we are successful, agents will recommend Drupal to new users, help Drupal developers move faster, help agencies win more work, and use Drupal as the trusted layer for content management and governance.

Thank you to everyone who helped bring the Drupal AI Initiative to this point. Together, the community has turned an ambitious idea into real momentum.

I'm excited about what comes next! Want to get involved? Join the #ai-initiative channel on Drupal Slack.

25 Jun 2026 3:44pm GMT

25 Jun 2026 3:26pm GMT

For Drupal teams, small technical choices often decide how maintainable a site becomes. DrupalCamp Kortrijk speakers are using that practical layer as the entry point for sessions on configuration, performance, CSS and editorial work.

25 Jun 2026 3:03pm GMT

Maintainer burnout threatens Drupal's 50,000+ contrib modules. How vibe coding with AI is becoming a lifeline for open source.

25 Jun 2026 1:38pm GMT