29 Jun 2026

feedDrupal.org aggregator

Droptica: From cost to asset: growing a Drupal support client into a development partner

Partenaire développement Drupal : coût à l'atout | Droptica

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

Talking Drupal: Talking Drupal #559 - Marketing Drupal

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

Resources

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

29 Jun 2026 6:00pm GMT

Droptica: Don't rebuild, evolve: a phased CMS modernization framework

Modernisation CMS vs. reconstruction : cadre par phases | Droptica

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

A Drupal Couple: We used our own plugins and skills to rebuild our site, here is the story

We used our own plugins and skills to rebuild our site, here is the story

Imagen
Screenshot of the adrupalcouple.us site
We pointed the plugins and skills we built ourselves at our own site, and rebuilt the whole thing, brand and all, in about a week of supervised time. Here is what that was actually like: what the tools did well, where they were confidently wrong, and where a human had to step in. These tools will hand you something that looks finished, and whether it is actually good is a separate question. Holding those two together turned out to be the part we could not hand off.
Drupal
Drupal Planet
AI
theming
Human-in-the-Loop
DaisyUI
design system
accessibility

Add new comment

29 Jun 2026 3:57pm GMT

The Drop Times: Drupal Aims to Reduce AI Agent Friction

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

Dripyard Premium Drupal Themes: Why CSS Style Queries Are a Bigger Deal Than You Think

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

UI Suite Initiative website: UI Suite Monthly #36 — Beta 5, Recipes, and AI That Builds Your Pages

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

26 Jun 2026

feedDrupal.org aggregator

The Drop Times: DrupalCamp Kortrijk Speakers Preview Drupal Canvas, AI, Localisation, and Hosting

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

The Drop Times: Drupal Orchestration Spec Maps ECA, FlowDrop and Maestro

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

25 Jun 2026

feedDrupal.org aggregator

Dries Buytaert: Launching Drupal's Outside AI workstream

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:

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

Drupal AI Initiative: Drupal AI Initiative: introducing Inside AI and Outside AI

By the Drupal AI Initiative

A year ago, we launched the Drupal AI Initiative with a published strategy and a bet that AI would matter enormously to Drupal's future. Today the initiative spans 32 organizations and more than 50 contributors, shipping against a public 2026 roadmap.

As the work has grown, it's become clear that our AI strategy needs to cover two distinct areas. While innovation and product development remain core goals across everything we do, we are organizing our day-to-day execution into two workstreams: Inside AI, led by Christoph Breidert, and Outside AI, a new stream led by Scott Falconer.

The unified AI initiative leadership team - made up of the existing initiative members - will continue to shape our overarching roadmap, while Christoph and Scott ensure that vision is executed. We will outline this leadership team and other key supporting roles in an upcoming post.

The core difference: Inside AI brings AI tools into the Drupal interface to assist the people using it. Outside AI makes Drupal the platform external AI agents reach for and act on.

Inside AI

Inside AI is AI inside Drupal, for the people using it: assistants, in-product workflows, page-building, and the rest of the user-facing surface. This is the work the initiative has been driving for the past year, and it continues against the 2026 roadmap already in flight.

Outside AI

Outside AI is AI outside Drupal, acting on Drupal. A person, agency, host, or developer is using an external agent or builder tool, and that agent needs to start with Drupal, connect to Drupal, inspect Drupal, change Drupal, verify Drupal, migrate into Drupal, or launch Drupal.

What's next

You'll see public roadmaps from both streams. Inside AI continues against its existing 2026 roadmap; Outside AI will publish its own outcomes and milestones, with a first proof of direction targeted for DrupalCon Rotterdam. Where both streams need the same capability, the answer is usually one shared Drupal contribution, not two parallel builds.

Get involved

The initiative is open, and both streams need contributors - whether you write code, test against real agent workflows, work on documentation, or bring a use case from your own agency or organization.

Not sure where to start? Come say hello in Slack and we'll help you find a first contribution.

25 Jun 2026 3:26pm GMT

The Drop Times: DrupalCamp Kortrijk Speakers Preview Configuration, Performance, CSS and Editorial UX

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

Acquia.com - Drupal Blog: Vibe Coding Drupal: A Force Multiplier for Contrib

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

Droptica: Text in images and SEO: why image-based content kills visibility - and how to fix it

Texte dans les images SEO : corriger le contenu image | Droptica

When a CMS is too hard to use, teams paste text into graphics and upload them as images. The page looks right - but search engines and AI answer engines cannot read that content at all.

See what image-based content costs you in SEO, GEO, accessibility, and day-to-day management - and how structured Drupal components fix it page by page.

25 Jun 2026 11:06am GMT

LakeDrops Drupal Consulting, Development and Hosting: Three Players, One Direction: ECA, FlowDrop, and Maestro

Three Players, One Direction: ECA, FlowDrop, and Maestro

Three musicians playing instruments in a wheat field

Jürgen Haas

ECA, FlowDrop, and Maestro all draw boxes and connect them with arrows, so people keep asking whether three Drupal workflow modules means a split community. Not quite. Dries Buytaert, Randy Kolenko, Shibin Das, and I are writing a shared orchestration design spec, disagreeing productively in writing. One axis explains all three: how much state a run carries. ECA reacts statelessly to any Drupal event across the whole request surface. Maestro holds a durable process that can wait days for human approval. FlowDrop spans the axis with a typed, inspectable dataflow graph that runs sync, async, or stateful from one definition, and Shibin is refining it toward strictly serializable data, ideal for building complex AI agents. Nothing is frozen. The word "orchestration" itself is contested in the spec glossary. Composition already ships: maestro_eca_task lets a Maestro process hand off to ECA. The bigger vision, ECA reacting to content, calling a FlowDrop AI flow, then routing through Maestro for human approval, is a picture we are building toward, not a release. But bridges are the start, not the finish. The real work is building a shared foundation, common primitives and APIs so the three tools stop reinventing the same concepts under different names. The spec's vocabulary synthesis shows the embarrassing similarity: Trigger, Step, Condition, Workflow, Run. The keystone is a defined contract for handing data between steps and between tools, one that works beyond Drupal's border for AI agents and external systems. Three tools is the right number because the stateless-reactive and instance-stateful ends pull architectures in opposite directions. Specialization beats a mediocre merger.

25 Jun 2026 11:00am GMT

Droptica: Zero-training CMS: delivering Drupal that content editors use immediately

CMS sans formation: Drupal dès le premier jour | Droptica

If your CMS needs a two-hour training session before anyone can use it, the CMS has a UX problem. The fix is not better training. It is a system that doesn't need any.

See the Drupal admin UX patterns, staging-first handover approach, and how Edenred Polska's marketing team started building production pages with no formal training at all.

25 Jun 2026 9:22am GMT