drupal

Introduction

Maintaining a DDEV add-on is more than a one-time task. As DDEV evolves, so should your add-ons. This guide will help you stay in sync with recent changes and keep your add-ons up-to-date, reliable, and aligned with current standards.

As part of preparing this guide, I also updated all official DDEV add-ons to reflect the latest recommendations and improvements.

Recommendations for Add-on Maintainers

Here are some high-level practices to follow:

• Take inspiration from the official add-ons, see how they're structured and follow similar practices
• Keep an eye on updates in ddev-addon-template
• Track changes in DDEV releases
• Configure your add-on repository settings
• Add the ddev-get topic to your GitHub repository if it should be discoverable by the wider community. (If your add-on is currently just an experiment or a fork, wait until it matures to add the topic.)
• Write a clear description and include relevant keywords to improve discoverability
• Use #!/usr/bin/env bash instead of #!/bin/bash at the top of your command scripts, it's more portable and works better across different environments.
• Ensure your add-on cleans up after itself: both ddev add-on get and ddev add-on remove should be idempotent. All files added via project_files and global_files must include a #ddev-generated stanza to support proper removal
• Remember to publish a new release after any update (unless it's just a README.md change)

I'm currently working on a script to streamline the update process. It's a work in progress and available here. I'd appreciate any feedback!

What's New in the DDEV Ecosystem

DDEV development is moving fast, and new features are introduced regularly. Here are some recent updates you should be aware of:

ddev get Deprecation

The classic ddev get command is deprecated in DDEV v1.23.5 and replaced by ddev add-on get.

Huge thanks to @GuySartorelli for implementing this feature, and also for proactively updating many add-on README.md files. You've likely already seen a pull request for your add-on!

Better Testing with Bats Libraries

While all add-ons use the Bats framework for testing, many are still missing Bats libraries that simplify assertions and test writing.

Consider adopting these libraries to enhance test clarity and maintainability.

Example:

• https://github.com/ddev/ddev-addon-template/blob/main/tests/test.bats

Issue and PR Templates

Make sure your add-on includes:

• Issue templates
• Pull request template

These improve the quality of contributions and bug reports.

Recommending DDEV Version Constraints

Your add-on should encourage users to keep DDEV updated. The current recommendation is to add this stanza to install.yaml:

This ensures compatibility and resolves known issues, such as those related to the Mutagen Problem Report.

Add-on Badges

The old maintained badge required yearly updates, which became a maintenance burden, especially for contributors with many add-ons. It's now replaced by a last commit badge.

To improve visibility and engagement on the DDEV Add-on Registry, add the registry badge to your README.md.

Example:

• https://github.com/ddev/ddev-addon-template/blob/main/README.md

Advanced Customization with Flags

Starting with DDEV v1.23.5, you can now use ddev dotenv set to manage environment variables more cleanly. This allows your add-on to read custom environment variables defined in .ddev/.env.* files, and use them inside your docker-compose.*.yaml configuration.

This feature is especially useful for advanced setups where flexibility and dynamic configuration are needed.

Example:

• https://github.com/ddev/ddev-adminer#advanced-customization
• https://github.com/ddev/ddev-adminer/blob/main/docker-compose.adminer.yaml

Making Small Changes to Docker Images

If your add-on needs a customized Docker image, the typical approach is to create a separate Dockerfile and configure your add-on to use it. However, for minor tweaks, you can take advantage of the dockerfile_inline option in your docker-compose.*.yaml file.

This approach lets you define a small Dockerfile directly in the YAML, avoiding the overhead of maintaining a separate file.

Examples:

• https://github.com/ddev/ddev-solr/blob/main/docker-compose.solr.yaml
• https://github.com/ddev/ddev-opensearch/blob/main/docker-compose.opensearch.yaml

MutagenSync Annotation for Commands

With DDEV v1.24.4, custom commands can now use the MutagenSync annotation.

You should use this annotation if your host or web commands modify, add, or remove files in the project directory. It ensures that file sync is handled correctly when Mutagen is enabled, preventing unexpected behavior or sync delays. (It does no harm and causes no performance issues if Mutagen is not in use.)

Example:

• https://github.com/backdrop-ops/ddev-backdrop-bee/blob/main/commands/web/bee

Support for Optional Compose Profiles

The same DDEV v1.24.4 release introduced support for optional docker-compose profiles, which can be used by add-ons to offer more flexible configuration.

Example:

• https://github.com/ddev/ddev-mongo/blob/main/docker-compose.mongo.yaml
• https://github.com/ddev/ddev-mongo/blob/main/commands/host/mongo-express

Repository Configuration Best Practices

To keep your add-on repository tidy, safe, and aligned with community standards, consider adjusting the following GitHub settings:

General Settings

Go to Settings → General in your repository:

• Uncheck features you don’t use, such as Wikis, Discussions, and Projects
• Enable Allow squash merging with Pull request title
• Disable Allow merge commits and Allow rebase merging
• Enable Always suggest updating pull request branches
• Enable Automatically delete head branches

Branch Protection Rules

Go to Settings → Rules → Rulesets:

1. Click New ruleset → New branch ruleset
2. Set Ruleset name to main
3. Under Enforcement status, select Active
4. Under Targets, click Add target → choose Include default branch
5. Under Rules, enable:
   • Restrict deletions
   • Require a pull request before merging (set Allowed merge methods to only Squash)
   • Block force pushes
6. Click Create to apply the ruleset

Conclusion

Keeping your add-on current means less work for users and fewer issues for you to manage. Use this guide as your checklist and stay in sync with the DDEV ecosystem.

Have questions, suggestions, or something cool to share? Join the conversation in our Discord, open an issue, or reach out via email. Your feedback helps improve the tools we all rely on.

If DDEV is helping you or your organization, please consider supporting its ongoing financial sustainability. Every bit helps keep the ecosystem growing and maintained.

Happy maintaining!

In a move to empower the Drupal community, DXPR is providing free access to AI models through the release of DXPR Builder 2.7 “Baby AI.” This initiative allows developers and content creators to leverage the power of advanced AI tools without additional costs or complex integration.

By integrating top vendors including OpenAI's GPT-4o, Google Gemini 2.5 models, Anthropic's Claude 3.7, Grok 3 by XAI, Perplexity AI, and state-of-the-art EU based models by MistralAI. 

DXPR ensures that every Drupal user can experience enhanced content creation and management. This free access underlines our commitment to fostering innovation and creativity within the Drupal ecosystem.

These AI providers are integrated in "DXAI" — our own AI platform that ties it all together to provide superior web content writing capabilities.

Quick Tour of DXAI in CKEditor 5

1. Slash command: Type /write a blog post about future Drupal 12 release (or any prompt) in an empty paragraph.
2. Watch it stream: DXAI writes live, so you can stop, continue, or tweak on the fly.
3. One-click refine: Select any text → choose “Improve clarity”, “Shorten”, “Change tone”, or your custom commands.

"Shown don't Tell" — DXAI in 3 GIFS

1. Adding a new AI text to the DXPR Builder  page

Demo of writing new text in DXPR Builder landing page, the AI is aware of all contents around the new text and therefore requires only a very basic prompt.

2. Adding a new AI text to the DXPR Builder  page

Demo of rewriting a text section in a different tone of voice. The tone of voice dropdown is managed with a Drupal Taxonomy.

3. Writing a new text from scratch.

The DXAI AI server integrates with state-of-the-art AI providers including Perplexity AI which is used for web research, fact checking, and preventing hallucinations.
 

Where to Configure DXAI

Site builders can enable DXAI under /admin/dxpr_studio/dxpr_builder/ai_settings (run update.php first). Key options:

• Select primary and fallback AI vendors
• Set token limits per role
• Map taxonomy terms to command and tone menus

UI Refresh: Faster, Friendlier, Fully Accessible

2.7 ships a modernized editor chrome with clearer icons, higher contrast, and full keyboard / screen-reader compatibility. Mobile editing is smoother too—perfect for last-minute tweaks on the go.

Improved Drupal 11 Integration

• Resolved JavaScript crashes in the editor chrome
• Aligned media dialogs with new core markup
• Verified compatibility with Drupal 11’s CKEditor 5 update stream

Other Highlights

• Marquee element: Add scrolling announcements with fade edges and reduced-motion support.
• Saved templates UI: Filter by layout and see thumbnails at a glance.
• Inline editing upgrades: Edit buttons, alerts, progress bars, and more without opening popup windows (AI supported everywhere).
• Drupal Media Library & Acquia DAM integration: Browse all your assets in one place.

How to Get “Baby AI” for Free

1. composer require 'drupal/dxpr_builder:^2.7'
2. Grab a free product key—no credit card, free forever for smal sites.
3. Enable the DXPR Builder AI Agent module and run update.php.
4. Configure DXAI settings, assign permissions, and start prompting!

Roadmap Sneak Peek

Today’s release is just the first step. Coming soon:

• One-prompt landing pages: Describe your offer; DXAI designs and writes a complete page in DXPR Builder.
• Clone from URL / PDF / image: Rebuild existing designs in minutes with structured, editable content.
• Conversational refinement: DXAI will chat with editors to clarify goals, add citations, and align with strategy.

We Need Your Feedback

Because the AI beta is free, the only thing we ask in return is insight. Share your triumphs, glitches, and wish-list items on the issue queue or in our commercia support system. 

Ready to Build Smarter Drupal Experiences?

Test the Live Demo  |  Learn More About DXPR Builder

Happy building—and happy writing—with DXPR Builder 2.7 “Baby AI”!

Category

How do you find your niche and become a Drupal Core maintainer?

There are still roughly 23 subsystems of Drupal Core without maintainers. These gaps need to be filled. 

While some people may be daunted by this task, rather than trying to learn everything in Core, Daniel explains why it is more valuable to become an expert in one area. This was how he became a Drupal Core maintainer for Layout Builder.

In this video, you will learn about:

• The steps Daniel took to reach Core maintainership.
• Why he chose Layout Builder as his niche.
• How to identify areas in Drupal Core that need maintainers.

Watch the video

Drupal modules are primarily maintained in Git repositories controlled by the Drupal Association on Drupal.org. Before the DA added support for semantic versioning in March 2020, our modules had version numbers like 7.x-1.0 or 8.x-2.1, with the first portion identifying Drupal API compatibility and the second identifying the major and minor version of the module.

However, with modern Drupal (Drupal 8+), a module can support multiple major versions so long as it does not depend on any deprecated APIs in Drupal, its dependencies, or PHP itself. Using the Drupal version number in module version numbers means many of our releases that support Drupal 9, 10, or 11 still start with 8.x-, never mind the fact that we don't support Drupal 8 at all any more.

Semantic versioning allows us to use branch names and tag releases for our various modules based on their own lifecycles. We don't need a new branch for each new major version of Drupal, and we can distribute more predictable updates to end users through Composer with major, minor, and patch versions of our modules.

When we first switched to semantic versioning, we created new branches based on the minor version. Thus, we went from an 8.x-2.x branch off of which we tagged releases to a 3.0.x branch. We never quite knew when to tag a patch versus a minor release in this scenario (i.e., 3.0.1 vs. 3.1.0) and created a situation where we'd have more branches to maintain than we really cared to (3.0.x, 3.1.x, 3.2.x, etc.).

We determined instead to start creating branches named only for the major version (3.x, 4.x, etc.) with release tags that still primarily use minor versions (3.0.0, 3.1.0, 3.2.0, etc.). This will permit us to focus on maintaining a single branch for each module until we need to introduce breaking changes while accommodating the occasional need to backport bug fixes to previous minor versions.

As the digital landscape evolves, organizations relying on Drupal 7 (D7) face a pivotal decision: opt for Extended Support or embark on a migration to Drupal 10 (D10)?

Both options have their pros and cons, depending on your timeline, budget, and long-term digital strategy. Let’s break it down so you can make the best decision for your organization.

Option 1: Extended Support – A Temporary Safety Net

Extended Support ensures your D7 site remains secure and functional beyond the official end-of-life deadline, giving you extra time to plan a migration.

Benefits of Extended Support:

• No rush – Your site remains secure, with critical security updates and patches, without having to migrate immediately
• Budget flexibility – Spread out costs instead of making a big investment all at once
• Strategic breathing room – More time to evaluate your business goals and plan a migrations in the future

Drawbacks of Extended Support:

• Not a permanent fix – In the long run you’ll need to migrate
• Potential rising costs – Maintaining older technology can become more expensive over time
• Limited innovation – You won’t benefit from the latest features and improvements in D10

Option 2: Migrating to Drupal 10 – The Future-Proof Solution

Migrating to D10 is a long-term investment in security, performance, and innovation. While it requires upfront effort, it ensures that your digital platform is modern, scalable, and ready for future growth.

Benefits of Migration to D10:

• Future-proof technology – Stay ahead with the latest security updates and performance enhancements
• Better User Experience (UX) – New features, improved accessibility, and a more flexible design
• Long-term cost efficiency – Reduce maintenance costs for outdated technology

Drawbacks of Migration to D10:

• Upfront investment – Migration requires planning, resources, and budget allocation
• Complexity – The process can be challenging, especially for highly customized sites
• Learning curve – Teams may need time to adjust to the new system

Dropsolid: Your Partner in Both Extended Support & Migration

At Dropsolid, we understand that not every organization is ready to migrate immediately. That’s why are part of the Drupal 7 EOL program.

What sets us apart?
Only 3 companies globally qualify for the EOL program and offer Extend Support for D7. We are the only partner in Europe, with offices in Europe and the US. This makes us the go-to-expert in the region for maintaining your D7 site securely while you work on a seamless transition to D10.

At the same time, we know that migration is inevitable—and when you’re ready, we can evolve your D7 and can help you migrate to D10 too.

What we offer:

• We keep your D7 site secure with ongoing updates and maintenance
• Migration to D10: customized migration roadmap, tailored to your business needs, covering everything from technical setup to team training
• Future-proof growth: our roadmap ensures that your site isn’t just D10-ready, but also DXP-ready, seamlessly integrating with your existing tools

Find all info about our related services here.

Key considerations: How to Decide?

When choosing between Extended Support and Migration to Drupal 10, ask yourself:

• What’s your timeline? Do you need more time, or are you prepared for transition?
• What’s your budget? Can you invest in migration now, or do you need to spread costs over time?
• What are your long-term goals? Do you want to future-proof your site, or is short-term maintenance enough for now?
• How complex is your current setup? A highly customized site may require extra planning before migrating.

Final Verdict: Should You Extend or Migrate?

• If you need more time to plan and budget, Extended Support can provide a temporary solution.
• If you’re ready to future-proof your digital platform, migrating to D10 is the smart choice.

Either way, Dropsolid has your back—whether it’s keeping your current site secure or guiding you through a seamless migration. Let’s make the right move together.

Ready to explore your options? Get in touch with us today!

Preamble

I began my last blog post, "My Drupal, AI, and Schema.org Manifesto," with an introduction that helped me to start discussing the use of AI in my daily Drupal work. This introduction reveals that I feel overwhelmed about where to begin exploring integrating AI with Drupal.

A Drupal AI module and ecosystem exist that have accomplished remarkable feats. I am eager to delve into the implementation and extensibility of the Drupal AI module; however, diving immediately into the code is daunting and could hinder my need to familiarize myself with using AI and comprehending how it works. Therefore, I am returning to the basics and revisiting one of my first Drupal achievements: building a module… using AI.

Hypothesis

AI will soon replace basic Drupal tasks, including creating simple modules. When this happens, the definition of entry-level development skills will evolve. AI will not eliminate jobs; instead, it will enhance workers' productivity and efficiency. Therefore, I want to explore how capable AIs are at building a Drupal module. I also want to explore if AI can help a new Drupal developer create their first module.

Theories

Below are some theories I want to explore and keep in mind.

• Keep it simple and small.
  AIs can comprehend vast amounts of data and relationships - we cannot.
• Provide a lot of context.
  AI performs significantly better when given as much context as possible. This ensures that both people and machines understand each other.
• Failure is part of the process. 
  Assume there will be mistakes and dead ends. An iterative approach leads to a better solution and understanding.

Goals

I've already used the word 'overwhelmed' a few times, and to keep my exploration and experimentation from...Read More

In the DrupalCon Atlanta Driesnote and follow-up blog post, Dries laid out a bold vision:

Site Templates combine Drupal recipes, a theme, design elements, and default content to give users a fully functional website right from the start."

He also posed a big question to the community: Should we build a Marketplace for these templates—and if so, how?

In just the first couple weeks of conversation, hundreds of community members have weighed in across Slack, blog comments, and BoFs. From enthusiastic endorsements to thoughtful concerns, the input is rich, complex, and deeply-rooted in the spirit of Drupal.

This post captures what we’re hearing so far.

The Opportunity

Many in the community agree: the lack of easily accessible, visually appealing starting points is one of Drupal’s largest barriers to adoption. A Site Template Marketplace could:

• Lower the barrier to entry for site builders and small organizations
• Give developers a fast, “wow-worthy” way to spin up sites in hours, not weeks
• Highlight the full potential of Drupal CMS + Experience Builder
• Generate new opportunities for agencies, makers, and module maintainers
• Strengthen the Drupal Association’s sustainability with shared revenue

As one commenter put it:

Every sold theme means a new Drupal site, likely a happy user... and the community gets something back."

What Would Make the Marketplace Useful?

In our first weekly Slack Prompt (#1), we heard:

• Fast paths to beautiful results: Templates you can install, customize, and deploy in days—not weeks.
• Tiers of complexity: Lightweight starter kits, robust enterprise templates, and everything in between.
• Paths for free and commercial use: A mix of free, contributed templates and paid offerings with premium support or assets.
• Rewards for collaboration: Incentives that elevate templates built by multiple contributors or agencies working together.
• SaaS-style options: Templates bundled with hosting, updates, or paid support for non-technical audiences.

I wanna grab something from the marketplace, put it together in 2–3 days max, and blow people’s minds." —Community member

The Questions We're Hearing Most

Across Slack and the blog post, several themes of inquiry and caution have emerged:

1. Legal Clarity & Licensing

• What parts of a Site Template can be sold under Drupal’s GPL license?
• Will template buyers be able to redistribute what they purchase?
• Can we enable commercial distribution while staying true to open source values?

Dries has addressed this nuance, noting that:

Assets like images, fonts, and demo content are not code and are not derived from Drupal. These elements… can use other licenses, including commercial ones."

2. Quality, Curation, and Trust

• How might we prevent a flood of low-quality or AI-generated templates?
• What might the minimum standards be for a “Marketplace-worthy” template?
• Will there be community reviews, security checks, and update requirements?

Many worry about the “freemium wasteland” effect—where flashy templates lack depth, break easily, or are quickly abandoned.

3. Revenue, Incentives, and Equity

• How might we compensate module maintainers when their code is included in paid templates?
• Should the marketplace allow non-fiat options like contribution credits?
• How might we incentivize the initial wave of templates while avoiding a “race to the bottom” on pricing?

Seeing others earn money by building on that work without recognition can be disheartening... But when it happens on Drupal.org, we have an opportunity to do better." —Dries

4. Experience & Accessibility

• Templates must support non-technical users: installable from the CMS UI, not just Composer.
• The Marketplace should integrate with Project Browser and potentially with hosters.
• Examples, walkthroughs, and support channels are key for adoption.

5. Governance & Structure

• Where might the Marketplace live? Drupal.org? Drupal.com? A subdomain?
• What rules, vetting, and governance structures might protect quality and community trust?
• Should a rollout be phased—starting with free templates first?

Additional Ideas from the Community

• Use contribution credits or sweat equity as alternative currency
• Add a “Marketplace-ready” badge system for contributors
• Offer lead generation or support links for template maintainers
• Allow template variation/extension patterns for maintainability
• Define the relationship between templates, themes, and recipes
• Rethink terminology: “Site Templates” vs. “Experience Kits” or “Project Starters”

Drupal has always had functionality. What it’s lacked is themes—and that’s what makes users fall in love with a CMS."

What’s Next?

This is just the beginning. Over the next few months, the Marketplace Working Group will continue to:

• Collect input via weekly Slack prompts, community surveys, and live feedback sessions
• Map feedback to the F-V-U-D-E model (Feasibility, Viability, Usability, Desirability, Ethics)
• Explore different models for governance, monetization, and sustainability
• Share out summaries like this one every few weeks to keep the community involved

We’re on track to make a go/no-go decision in Q3 2025, and your participation is essential in shaping that outcome.

How Can You Get Involved?

There are many ways to plug in and volunteer—whether you have 5 minutes or a few hours a week:

• Share your thoughts - Reply to the weekly Slack prompts in #drupal-cms-marketplace
  1. What would make the Drupal Marketplace useful to you?
  2. What might prevent you from using or contributing to the Marketplace?

1. Take a survey - Survey #1: Shaping the Drupal Marketplace: Contributor Perspectives targeted at Agencies, Drupal Contributors and Drupal Certified Partners

• Join a real-time session - Help shape decisions in live 50-min community calls
• Become a volunteer - this work is open to all community members—no special technical background required. Many roles are great fits for folks who enjoy facilitation, organizing, writing, or user-centered thinking.
• Spread the word - Invite others to share feedback or join a session

Over the past few weeks, the Marketplace Working Group and volunteers have been busy laying the foundations for the months ahead. As a reminder, our goal is to determine whether a Drupal Site Template Marketplace can be designed in a way that is trusted, inclusive, sustainable, and viable—and to reach a go/no-go recommendation before DrupalCon Vienna.

From Idea to Critical Assumptions

Over the past few weeks, the Marketplace Working Group has been focused on a key early step: identifying the assumptions that must be true for a Drupal Site Template Marketplace to succeed.

Rather than moving directly into planning and building, we are working transparently with the community to surface and stress-test our most critical assumptions before making any final decisions.

In this update, we’ll share where we are now—and where we still need your help to validate what matters most.

Why Focus on Critical Assumptions?

The Marketplace is an exciting idea, but it brings with it real risks. Some assumptions, if wrong, could seriously harm Drupal’s ecosystem, community trust, or financial health. We’ve identified the early critical assumptions—those with:

• High impact if we’re wrong, and
• High uncertainty based on what we know today.

Rather than ignoring or minimizing these risks, we are bringing them forward, openly and early, so the community can engage with them directly.

Critical Assumptions Emerging So Far

From the emerging community feedback (Survey #1: Shaping the Drupal Marketplace: Contributor Perspectives, slack prompts, and deep discussion in this thread), several high-risk assumptions have emerged:

1. There will be enough demand for site templates to sustain a marketplace.

If we build it, will they come? And will they pay?”
Without real demand, the Marketplace won’t achieve its goals—and may strain community resources without impact.

How we’ll validate: Ongoing surveys to Drupal users and agencies; testing via Drupal CMS starter templates; scenario-based surveys during Real-Time Collaboration (RTC) sessions.

2. High-quality templates will be created and maintained.

We need to avoid a freemium wasteland of abandoned templates.”
Success depends on attracting contributors with design and UX skills—and ensuring long-term maintenance.

How we’ll validate: Contributor surveys about incentives, motivations, and barriers; prototype pilot tests; deeper exploration in RTC sessions.

3. The operational complexity of running a marketplace is manageable.

The DA can’t afford to build and maintain a marketplace that requires millions to operate."
The Marketplace must be financially and operationally sustainable from day one.

How we’ll validate: Modeling operational costs; evaluating automation options; benchmarking against other marketplaces.

4. A commercial element can be introduced without undermining open source values.

Commercialization must not erode what makes Drupal different.”
If done poorly, a commercial marketplace could fragment the ecosystem, damage trust, and alienate contributors.

How we’ll validate: Community consultation on licensing models; exploring models for attribution, revenue sharing, and code stewardship.

5. Governance structures can maintain trust and quality at scale.

If trust fails, the marketplace fails.”
The Marketplace must earn and maintain user and contributor trust through clear standards, quality controls, and transparent processes.

How we’ll validate: Testing community expectations through surveys; prototyping governance models; pilot feedback loops.

Important Tensions Emerging

Through open discussion, several important tensions have also surfaced:

• Open Source vs. Monetization:
  Balancing the spirit of FOSS with the need for financial sustainability.
• Support Expectations:
  Clarifying who provides support for templates—and setting fair boundaries.
• Future Risks:
  Avoiding the slippery slope toward undermining Drupal collaborative ecosystem model or a poor signal-to-noise ratio from low quality or unsupported templates.

We recognize that these are not easily solved with a single conversation. They will require ongoing community engagement, transparency, and iteration.

Where We Are Now

Here’s what’s been accomplished so far:

• Roadmap finalized for how we'll reach a go/no-go decision.
• Volunteer team onboarded, and we're beginning weekly coordination around community engagement.
• Community framing completed, based on early signals from surveys, Slack prompts, and discussions.
• Critical assumptions identified through our Week 2 Assumption Slam.

What’s Next

Over the coming weeks, we’re moving systematically through key questions:

• Contribution Value: What would make it worthwhile for someone to contribute a template?
• Governance & Trust: What signals would make users feel confident using a marketplace template?
• Ecosystem Fit: How can the marketplace align with, not compete against, existing agency and contributor models?
• Contributor Experience: What support is needed to help contributors succeed?

Each week, we’ll continue to validate assumptions, evolve our thinking, and ensure that what we’re building—if we build it—is something the community truly wants and can stand behind.

Thank you to everyone who has already shared feedback, challenged assumptions, and raised important questions. Your voices are helping shape this work.

Stay tuned—and stay involved.

How You Can Get Involved

1. Respond to weekly Slack prompts.
   This week: What would make it worthwhile for you to contribute a template?
2. Join our upcoming Real-Time Collaboration (RTC) session
   First session: 1 May 2025 at 15:30  UTC about Co-creating Value and Incentives
3. Share your perspective on the surveys when they open.
   How could a Drupal Site Template Marketplace Help You? for Agencies and potential End Users of templates.
4. Bring forward your own assumptions and risks we may have missed.