06 Oct 2026
Drupal.org aggregator
Jacob Rockowitz: Vibing Drupal: Tale 2 - Using AI to maintain a module, exploring the AI-possible
Introduction
Adopting AI can feel overwhelming, so I am sharing a few tales from my experience creating, maintaining, and assisting with contributed Drupal modules. AI can do a decent job building a "greenfield" Drupal module from scratch, so my first tale is about using AI to build and contribute a module. For my next tale, I want to talk about using AI to maintain an existing "brownfield" Drupal module.
Growing up in NYC, I found brownfields often intimidating, with some so toxic that it can take years for backhoes and dump trucks to remove the contaminated topsoil before construction can begin. With code, a brownfield can contain technical debt, orphaned code, missing tests, etc. Simply put, a brownfield contains unknowns, which means more things can go wrong while working on it. Sometimes a brownfield is so big you need heavy machinery to maintain it, and that is exactly how I felt about using AI on the Schema.org Blueprints module.
Maintaining a large module using AI
Gradually, I have been experimenting with AI to help maintain the Schema.org Blueprints. At first, I would just throw a one-shot prompt at the AI to address a single issue, and it would do a decent job diagnosing and resolving the problem. As I became more confident steering the AI, I started asking it to create issue forks, commits, pushes, and even MRs. As I previously stated in my AGENTS.md I always have "Require me to review all changes before committing and pushing code." and most models respect this rule.
My comfort level reached a point where I am creating {module}-issue-maintenance agent skills that extend my drupalorg-issue-maintenance skills. These maintenance skills have agents to track remote issues in...Read More
06 Oct 2026 9:40am GMT
joshics.in: Drupal 12 and the End of Legacy Debt: A Forced Modernization for Enterprise Engineering
Drupal 12 and the End of Legacy Debt: A Forced Modernization for Enterprise Engineering bhavinhjoshi

Just last month, a prospective client came to Joshi Consultancy Services asking for a cheap cron script to fix a runaway disk usage issue. The reality? They were bleeding money on a deep architectural flaw in their Drupal ingestion pipeline. We see this constantly. For years, the enterprise software industry tolerated a quietly expensive habit: carrying technical debt forward.
Historically, major CMS upgrades were treated as little more than UI refreshes. Agencies seamlessly dragged deprecated code, outdated PHP environments, and fragile database structures from one major version to the next. The result? Senior engineers stuck acting as caretakers for legacy code, while CXOs bled budget on endless maintenance retainers just to keep the lights on.
With the December rollout of Drupal 12, that loophole permanently closes.
The platform is fundamentally altering the rules of engagement. Instead of merely suggesting best practices, Drupal 12 enforces strict architectural modernization right at the server level. Here is why this shift is a massive win for both engineering teams and business leadership.
The Eradication of Deprecated APIs
Spaghetti code. We all hate it. But until now, deprecated code could linger in a system for years, propped up by complex workarounds.
Drupal 12 changes this by aggressively stripping out all deprecated core APIs. The system physically rejects structural laziness. If an agency attempts to stack new logic on top of a legacy foundation, the application simply will not run. You build within clean, modern boundaries from day one. Period.
Enforcing Modern Infrastructure Floors
Previously, organizations delayed server upgrades to save short-term costs, forcing modern applications to run on aging environments.
No longer. Drupal 12 introduces non-negotiable infrastructure floors: a PHP 8.5 minimum runtime alongside raised database requirements (MySQL 8.0 / PostgreSQL 18). This isn't just backend housekeeping. By enforcing these modern tiers, the core framework guarantees a baseline of performance that cannot be compromised by budget-saving shortcuts.
Security as a Structural Guarantee
Enterprise security is too often treated as an expensive, opt-in audit layer applied long after development is complete.
By making Argon2id the default for password hashing, Drupal 12 integrates military-grade resistance against GPU-driven brute-force attacks directly into the core blueprint. For the C-suite, this is an immediate reduction in liability. Security transitions from an ongoing maintenance headache to a baseline structural guarantee.
The Business Outcome: Eliminating the Maintenance Drain
The most profound impact lands directly on the balance sheet.
For CXOs, these forced architectural boundaries solve the most expensive problem in enterprise software: unpredictability. When the core framework refuses to execute legacy PHP and automatically enforces top-tier security standards, the financial drain of technical debt is cut off at the source. Organizations can finally stop paying agency retainers to manage bloated, unmaintainable code.
Drupal 12 is not just a feature upgrade. It is a forced modernization of your engineering culture.
If your organization treats this version bump as a standard IT afterthought, you are actively funding your own future liability. Stop paying for temporary bug fixes. Engineer the blueprint first.
Are your servers, and your budgets, ready for the rollout?
06 Oct 2026 8:32am GMT
Specbee: The tools around Drupal have become simpler, complementing Drupal. Read our take on how Canvas, components, Drupal CMS, and AI are changing Drupal work.
The tools around Drupal have become simpler, complementing Drupal. Read our take on how Canvas, components, Drupal CMS, and AI are changing Drupal work.
06 Oct 2026 5:39am GMT
05 Oct 2026
Drupal.org aggregator
Freelock Blog: Beyond Bigger Servers: Keeping Websites Online Under Bot Attacks
Beyond Bigger Servers: Keeping Websites Online Under Bot Attacks

05 Oct 2026 10:00pm GMT
Très Bien Blog: WordPal: Theme Drupal with WordPress block themes
WordPal: Theme Drupal with WordPress block themes
One of the difficulty with starting a Drupal website is the lack of diversity in available themes. There has always been more choice in the WordPress world for themes. Maybe, just maybe, Drupal could use WordPress themes and get the best of both worlds?
theodore
05 Oct 2026 6:30pm GMT
The Drop Times: The Demo Is Over. Now Drupal AI Has to Become a Product.
After Rotterdam, one part of Drupal's AI story is no longer theoretical. The Northmoor University demo brought AI search, content review, translation, editing and externally connected assistants together on the same Drupal site. That made a collection of modules feel closer to a product experience, but it also exposed the next question: whether organisations can depend on the path between those pieces in production.
The stack does not yet sit at one level of maturity. Drupal AI 1.5 and Canvas are stable and covered by Drupal's security advisory policy. Context Control Center is a release candidate, while Tool API and MCP Server remain in beta. Rotterdam showed that these parts can work together. Production teams now have to decide which combinations are mature enough to trust, govern and support.
Permissions, human review and traceability are central to that decision. The demo drafts changes rather than publishing them, leaving a person to review what the AI proposes. Tool API brings access checking into executable capabilities, while MCP can expose Drupal tools to assistants outside the site. Context Control Center moves instructions and organisational knowledge toward managed, reviewed material. Taken together, those pieces point toward a production requirement that goes beyond capability: teams need to know what an agent may read, what it may change, which tools it may invoke, what context it received and who remains accountable for the result.
Provider choice and the connection between Tool API, MCP and Canvas make the remaining maturity gap visible. Drupal's provider abstraction supports different commercial and locally operated models, but workflows still need to remain testable as model behaviour, tool calling and context limits change. The Drupal AI Initiative's follow-up also draws a clear line between what Rotterdam demonstrated and what is available today: the simplified MCP approach shown on stage remains a prototype. Canvas Tools, which lets agents manipulate Canvas through Tool API, is likewise still beta and is not covered by the security advisory policy.
That does not make Drupal AI simply ready or not ready for production. Different parts of the stack already support different kinds of real use, with different levels of risk. Rotterdam instead changes what Drupal AI now has to prove: that permissions remain enforceable, context can be governed, costs and activity can be traced, providers can change without losing control, and interfaces can survive upgrades. Productisation does not mean closing the ecosystem or putting everything inside one package. It means reaching the point where an organisation can understand what an AI system will be allowed to do before deployment, and explain what it actually did afterwards.
Follow The DropTimes on LinkedIn, X, Bluesky, and Facebook, or join #thedroptimes on Drupal Slack.
Allen Jason wrote and curated this issue of Editor's Pick.
05 Oct 2026 2:30pm GMT
The Drop Times: DrupalCon Rotterdam Jobs Board Pairs Vacancies With Community Recommendations
A handwritten board at DrupalCon Rotterdam carried more than vacancy notices. Attendees could also recommend community members actively looking for their next Drupal role.
05 Oct 2026 1:16pm GMT
Salsa Digital: Drupal AI Context — first release candidate available
Drupal AI Context first release candidate The first release candidate (RC 1) of Drupal AI Context , also known as Context Control Center (CCC), is now available. This is a major milestone for the project. After five beta releases and months of community testing, refinement and expansion, RC 1 marks the final stage before the first stable 1.0 release. We're currently planning to release CCC 1.0 in about a month, subject to what we learn from testing the release candidate. There may also be an RC 2 release prior to 1.0. CCC helps Drupal sites provide governed, reusable context to AI-powered features, from brand voice and editorial standards to organisational knowledge, governance rules and other information that AI systems need to work effectively.
05 Oct 2026 12:00pm GMT
1xINTERNET blog: When the Next Flash Flood Hits, Will Your Phone Have the Right Answer?
FlashFloodBreaker partner meeting in Metz: 1xINTERNET shares digital and regional resilience insights to help improve Europe's response to extreme flash floods.
05 Oct 2026 12:00pm GMT
Gspikes: Website Migration SEO: How to Rescue One That Has Already Gone Wrong
The migration launched and traffic is falling. The eight causes in the order to check them, what Search Console tells you, how long recovery takes, and when to roll back.
05 Oct 2026 7:00am GMT
Webpro Company blog: AI translation in Drupal: keeping three languages current
An Estonian service page changes its delivery time from five days to ten. The English and Finnish pages still promise five. AI can translate the new sentence quickly, but someone must notice the change and decide when the other languages should go live. Start with service pages WebPro recommends testing AI translation on one content type first: perhaps ten service pages in Estonian, English and Finnish. Use them to check the complete journey from a source edit to a published translation. Translating a thousand pages at once says little about whether next week's changes will reach the right places. Drupal's AI capabilities received renewed attention in Rotterdam in late September. The Drupal AI initiative's updates discuss translation alongside other editorial tools. For a business, the…
05 Oct 2026 6:00am GMT
The Drop Times: Japan Drupal Association Holds Founding Assembly, Files for NPO Certification
Japan's Drupal community now has a new voluntary association with a formal NPO application under review. Its first work begins before legal incorporation is complete.
05 Oct 2026 5:22am GMT
02 Oct 2026
Drupal.org aggregator
Drupal AI Initiative: Speed, Safety, and Smarter Journeys: What Drupal AI 1.5 Means for Digital Marketing Leaders
Author: Will Huggins
In enterprise digital experience, the conversation around generative AI has shifted dramatically. Digital leaders are no longer asking whether AI can write a paragraph or spin up a page. They are asking:
- Can our AI deliver seamless customer journeys?
- Can it scale without diluting our brand voice?
- Will our IT and compliance teams actually approve it?
The release of Drupal AI 1.5 directly answers those questions.
Driven by 63 active contributors across 31 global organisations, Drupal AI 1.5 shifts the platform from one-shot text generation into an interactive, governed, and brand-safe digital experience engine.
For CMOs, Heads of Digital, and website owners, this release is not about backend developer plumbing - it is about practical marketing velocity, measurable ROI, and total brand sovereignty.
Here is a breakdown of what Drupal AI 1.5 unlocks for your digital roadmap.
1. Digital Assistants That Actually Remember the Customer Journey
Early AI chatbots suffered from digital amnesia: the second a visitor navigated to a new page or refreshed their session, their context vanished. For high-consideration purchases or complex self-service portals, this creates friction and frustrates users.
Drupal AI 1.5 introduces persistent, stateful conversation memory:
- Seamless Multi Page Engagement: Conversational assistants now securely remember previous interactions across a user's entire browsing session. If a prospect asks about product specifications on a solutions page and later opens the chat on your pricing calculator, the assistant retains the context.
- Enterprise Privacy by Default: Conversation threads are sandboxed per user session. Visitors enjoy a personalised journey, while your data protection officers can rest easy knowing customer history is never exposed across sessions or leaked externally.
- Grounded in Your Content: Rather than relying on generic model knowledge, chatbots can now be plugged directly into your site's verified content repository (Retrieval-Augmented Generation / RAG), ensuring every answer is accurate, factual, and backed by your brand's single source of truth.
The Strategic Win: You transform your website from a static brochure into an intelligent, conversational destination that guides prospects smoothly through the conversion funnel.
2. Real-Time Streaming Guardrails: Zero-Risk Brand Safety
For any marketing leader, the greatest fear with public-facing AI is reputational damage: a model hallucinating incorrect pricing, generating off-brand language, or leaking sensitive corporate information.
While traditional safety filters only check text after the entire response is completed-slowing down user experiences-Drupal AI 1.5 introduces active streaming guardrails:
- Live Stream Filtering: Guardrails now monitor the AI's output token-by-token in real time. If an external model attempts to output confidential identifiers, internal instructions, or unvetted claims, the filter suppresses and replaces the content before a single character renders in the visitor's browser.
- Semantic Topic Guardrails: Restricting an AI to approved topics used to be brittle. If a model said "coastal vacation" instead of "beach holiday," strict keyword filters would break. Version 1.5 uses intelligent semantic matching: the assistant understands intent, synonyms, and localised phrasing while remaining firmly inside your brand boundaries.
- Cost-Effective Compliance: User prompts can now be routed through dedicated, cost-free moderation channels instead of burning expensive generation tokens, protecting both your brand standards and your marketing budget
The Strategic Win: Complete brand safety. Your legal, compliance, and IT teams get auditable, proactive safeguards built into the core publishing architecture.
3. From "One-Click Prompts" to Interactive Editorial Copilots
Early CMS AI automations were rigid: an editor clicked an AI button, waited, and was forced to accept or discard whatever came back.
Drupal AI 1.5 turns AI Automators into an interactive creative partner inside the editing workspace:
- Interactive Refinement in the Edit Form: When generating campaign copy, headlines, or summaries, editors can now open an interactive refinement window. With plain-language prompts like "make this more urgent," "tighten to 30 words," or "adapt for our enterprise persona," the copy updates dynamically-while automatically preserving your overarching brand voice rules.
- Multi-Step Content Pipelines in One Click: Marketing teams can trigger automated workflows directly from a field. A single click can research a topic, draft copy, pull relevant taxonomies, and format the output-without leaving the edit screen or waiting on developer intervention.
- Vision-Aware Content Intelligence: The CMS can now "see" the imagery embedded in your articles. Multimodal vision models analyse uploaded graphics to automatically draft descriptive alt-text, optimise summaries, and ensure full accessibility compliance without manual overhead.
The Strategic Win: High-velocity content operations. AI handles the first 80% of drafting and repetitive formatting, leaving your team with complete creative control over the final 20%.
4. On-Site Search That Understands Customer Intent
If visitors cannot find the right product, resource, or service within seconds, they bounce. Traditional on-site search engines rely on exact keyword matches, frequently failing when visitors search using colloquial questions or conversational language.
Drupal AI 1.5 upgrades search into a semantic relevance engine:
- Intelligent Result Re-Ranking: Integrated directly with your site's search architecture, the AI analyzes user queries semantically and re-orders results based on actual intent, not just raw word frequency.
- Instant Answers: New question-answering capabilities can pinpoint the exact passage answering a user's question, displaying direct snippets alongside high-confidence relevance scores.
- The Strategic Win: Higher digital engagement and increased conversion rates by eliminating the "dead-end" search experience across your digital properties.
5. Total Financial & Operational Governance
One of the fastest ways to lose executive support for AI initiatives is unpredictability-unexpected API bills or black-box operations that IT cannot audit.
Drupal AI 1.5 builds transparency directly into the dashboard:
- Real-Time Token & Cost Tracking: Product owners can monitor exact token consumption (input, output, and cached reasoning) alongside live provider rate limits. You know precisely what each campaign or automated workflow costs.
- Enterprise Observability: All AI actions emit standardized monitoring metrics compatible with leading enterprise platforms (such as OpenTelemetry, Datadog, or New Relic), ensuring full auditability for platform architects.
Move Fast, Stay in Control, Own Your Destination
Proprietary digital experience platforms lock your organization into their single, closed-ecosystem AI model-charging heavy licensing premiums while limiting your flexibility. Lightweight headless tools offer AI writing widgets, but leave you without enterprise governance, multilingual depth, or data sovereignty.
Drupal AI 1.5 delivers the best of both worlds: model-agnostic freedom to choose the best AI for the job, visual campaign acceleration for marketing teams, and bulletproof architectural security.
Experience Drupal AI Today
Reading about capabilities is one thing; seeing them transform your digital operations is another.
Explore our live interactive environments to test chatbots with memory, stream-level guardrails, and interactive content workflows:
02 Oct 2026 1:49pm GMT
Drupal AI Initiative: Drupal AI after the DriesNote Rotterdam: what you can use today and what comes next

Image: DriesNote, DrupalCon Rotterdam 2026 by Paul Johnson
Author: Jeremy Chinquist
At DrupalCon Rotterdam on September 29, 2026, Dries Buytaert used his keynote to show how far Drupal has come and who it can reach next. Dries framed the keynote around three pillars that bring Drupal's strengths to more people: multilingual (reach people in more languages), JavaScript and headless (bring more developers and applications to Drupal), and AI (give people new ways to work with Drupal).

This post zooms in on the AI pillar. For the full keynote, including digital sovereignty, multilingual, headless and the new Drupal Advocacy Program, read the official recap: DriesNote Rotterdam: Drupal is Light-Years Ahead of Its Reputation. To watch the six demos from the keynote, see Proof, not promises. Watch the six demos from the DriesNote Rotterdam.
Watch the full keynote on YouTube
Exclusive interview: James Hall sat down with Dries Buytaert for the Drupal AI Initiative. Watch it on LinkedIn

Image: James Hall, Everyone TV interviews Dries Buytaert following the DriesNote
A strong start for the Drupal AI Initiative
Dominique De Cooman, Head of Partnerships for the Drupal AI Initiative, opened the conference with a short welcome and a clear message: the Drupal AI Initiative is strong and active. Dries later mentioned that over 100 people have contributed to the Drupal AI Initiative so far.
Try it now: "Drupal AI Demo: Northmoor University"
On stage, Dries showed off the demo that the Inside AI team, led by Christoph Breidert, had been developing over the past few months. "Drupal AI Demo: Northmoor University" is a complete university website that shows Drupal AI at work on realistic content. Anyone can try it today at drupal.org/ai/demo. To learn how the demo was built and what it can do, read Christoph's announcement: Introducing the Drupal AI Demo.

Five parts of the demo were highlighted during the talk:
- Find weak content and fix it. Drupal AI scans the site's programs, courses, people, news, events and policies, checks them for accuracy, tone and inclusive language, and flags weak items.
- Fix it without the expert. Editors fix the flagged content themselves instead of waiting for a specialist.
- Grounded answers, every source cited. Visitors can ask the site questions. Drupal AI answers from the site's own content and cites its sources. If the answer isn't there, it marks the question as outside the site's scope and uses the content to point to the right person to contact. It is not allowed to invent an answer.
- Drafts, not surprises. Editors can connect their own AI assistant. Asked to update every page that mentions a newly promoted professor, the assistant finds 10 pages and drafts the changes, but publishes nothing. Every draft waits for a human to review and publish.
- Stay accountable. AI guardrails, one source of truth and every interaction logged.
Did you know?
Aidan Foster also used the demo site in the presentation "Encoding Expertise: How UX Research Powers Human-First AI" to show how AI guidelines can help review a site's content.

Image: Drupal Association (DriesNote, DrupalCon Rotterdam 2026)
What this means for you: for agencies and site owners, this is the quickest way to see Drupal AI on a real site before planning a project. The guardrails matter as much as the features: the AI flags, drafts and cites, and people decide what gets published.
Building Drupal Canvas components with AI
Dries showed AI-assisted development for Drupal Canvas. Given a prompt such as "Build a content template for my articles," the AI assistant checks its work against Canvas Workbench, ESLint and the Canvas CLI. The result is a set of simple template files, pushed to the site with the Canvas CLI.
What this means for you: front-end developers can let an AI assistant write the first draft while Canvas' own tooling validates the result.

Image: Drupal Association (DriesNote, DrupalCon Rotterdam 2026)
Connecting Drupal to AI assistants
Today, exposing a Drupal module's features to AI assistants via MCP takes around 1,000 lines of code. Dries showed a prototype that brings this down to around 20 PHP attributes, using a recipe that combines the Simple OAuth, MCP Server and Tool API modules. The principle is "describe once, use in multiple places": one description of a capability serves AI assistants, workflow tools and JavaScript components alike.
In the demo, a FindImages tool lets an AI assistant look up images on the site, with FlowDrop connecting the pieces.
What this means for you: this is a prototype, not a release. For module maintainers, it points to a future where one description makes a module usable by AI assistants.

Image: Drupal Association (DriesNote, DrupalCon Rotterdam 2026)
On the roadmap: the Rosetta Sprint
The next step is the Rosetta Sprint: a four-day sprint with key maintainers to describe Drupal's capabilities once, in a form that AI agents, other systems and humans can all read. The goal is to make Drupal's data and capabilities easier to expose to AI agents, orchestration tools, frontends and more. The date and location are still to be announced.
Did you know?
Kristen Pol used the Drupal AI Demo to record the demo clips for her session "Context Control Center: Bringing AI Context to Drupal CMS." Curious how Drupal gives AI the right context? Take a look.
Talk louder about Drupal
Dries closed with a clear request: "Here is my ask: Talk louder about Drupal." Try the demo, share what you build with Drupal AI and join the Drupal Advocacy Program.

Image: Karl Hepworth (DriesNote, DrupalCon Rotterdam 2026)
Thank you, Drupal AI Partners
During the keynote, Dries thanked the Drupal AI Partners, the organizations that back the Drupal AI Initiative. Want your organization to join them? Become a partner.

Image: Drupal Association (DriesNote, DrupalCon Rotterdam 2026)
02 Oct 2026 9:57am GMT
01 Oct 2026
Drupal.org aggregator
Talking Drupal: Talking Drupal #572 - The PHP Foundation
Today we are talking about PHP, Open Source, and Sustainability with guest Elizabeth Barron. We'll also cover AI Image Classification as our module of the week.
For show notes visit: https://www.talkingDrupal.com/572
Topics
- What is the PHP Foundation
- Language Health Challenges
- Paid Core Developers
- Release Infrastructure
- Foundation Role and Perception
- Docs and Onboarding
- Elizabeth Open Source Journey
- Future of PHP Ecosystem
- Listener Elephant Question
- Ecosystem Security Hub
- Advisory Board Limits
- Modernizing Mailing Lists
- Foundation Awareness Push
- PHP Ambassadors Strategy
- State of PHP Survey
- Five Year Vision
- Community Hour Podcast
- php.net Design Refresh
Resources
- The PHP Foundation
- Derek Rethans
- xdebug
- Infrastructure
- https://github.com/derickr
- Drupal advocacy
- Link to community hour podcast
- Php 8.5
- Contribute to php article
Guests
Elizabeth Barron - thephp.foundation elizabethbarron
Hosts
Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Tim Sharp - tea-sharp
MOTW Correspondent
Martin Anderson-Clutz - mandclu.com mandclu
- Brief description:
- Have you ever wanted the images in your Drupal media library to be automatically given alt text, a rich description, and a set of tags, using AI? There's a recipe for that.
- Module name/project name:
- Brief history
- How old: created in Sep 2025 by Artem Dmitriiev (a.dmitriiev) of 1xINTERNET
- Versions available: 1.1.1, which requires Drupal 11.2 or newer
- Maintainership
- Actively maintained, latest release and commit just two weeks ago
- Security coverage
- Number of open issues: 9 open issues, 4 of which are bugs
- Usage stats:
- No usage data reported
- Module features and usage
- This recipe applies core's image media type recipe, then adds a description field and a tags field to image media, with tags in a new "Image Classification" vocabulary
- Editors get a "Generate Alt Text" button right on the image field, using the Field Widget Actions module, with a prompt written like an accessibility expert: under 100 characters, no "image of", flag logos and graphics
- On save, a vision model writes a description of up to eight sentences: colours, photo versus illustration, people, mood, and key objects, using the media name for context
- Tagging is chained off that description rather than the image itself, picking or creating up to five short, general terms, and reusing similar existing tags where it can
- It also adds bulk actions to the media admin view, so you can run description and tagging across an existing library, not just new uploads
- Description and tag filters are added to the media library, including the widget, so editors can search for "sunny summer day" right in the image picker
- The stated bigger goal is making images discoverable by RAG and other AI search, so good descriptions become a foundation for future AI features. In fact, this recipe is a dependency for the Canvas AI Image Search recipe, which is still a work in progress
- Under the hood, images get scaled to 400px wide and converted to PNG before they're sent to the model, which keeps things faster and cheaper
- One caveat: your site needs an AI provider with a default "chat with image vision" model, and the recipe checks for that when it's applied
- Also worth a look: the description prompt asks the model to describe people's age, gender, and ethnicity, and even name them if it can, so you may want to review that prompt for your privacy policies, and adjust accordingly
- Like any recipe, it provides a robust starting point for some compelling features, and every prompt and setting can be tweaked after you apply it
- Lastly, I wanted to mention that in today's Driesnote in here in Rotterdam, Dries demoed being able to use MCP to search images on his own site. A recipe like this could help you make sure the images in your media library have sufficient metadata to make that work reliably
01 Oct 2026 6:00pm GMT
The Drop Times: Bento Showcase Brings Visual Hierarchy to Drupal Views
A Drupal View does not have to end as a row of equal cards. Bento Showcase tests how far sorting, promotion, and image treatment can carry a structured content collection toward a composed page.
01 Oct 2026 11:01am GMT
Add new comment