We’re excited to announce that a draft Drupal Site Template MVP Marketplace proposal will be released next week for public comment. This version outlines a clear Minimum Valuable Product (MVP) focused on early value, sustainability, and trust.
But first — here’s a look at what’s been shaping the direction of this proposal.
The Business Model Canvas: A Snapshot
To help align on strategy and priorities for the Site Template Marketplace, the Working Group created a Business Model Canvas—a simple tool that breaks down the core elements of how the Marketplace can deliver value and remain sustainable. The Working Group landed on an MVP  model that centers:

Primary Users: Low-code/no-code marketers and freelancer agencies
Key Value: Trusted, flexible site templates that reduce time-to-launch and lower adoption barriers
Revenue Stream: application and referral fees on sales and upsell opportunities to support Drupal Association infrastructure
Cost Structure: Low-overhead pilot with both automated and staff-supported review

What We Heard: Shared Priorities Across Surveys and Slack
More than 500 people have shared their perspectives across four surveys—and others have weighed in through Slack discussions, real-time collaboration, and open conversations.
This community and end-user input has been honest, nuanced, and incredibly generous. It has revealed clear patterns, thoughtful tensions, and strong signals of where the community wants to go. So as in advance of the MVP proposal’s release, let’s reflect back what we’ve heard so far.
1. Trust Starts with Quality, Transparency, and Previews
Both in survey responses and in Slack, the message was the same: don’t launch unless people can trust what they’re getting.
Top trust signals:

A live demo or preview (most consistently requested signal across all channels)
Clear documentation of dependencies and limitations
Visible signals of quality (badges, reviews, contributor reputation)

In Slack, people emphasized that even a great theme becomes untrustworthy if it’s hardcoded, inaccessible, or unclear about what it installs.
Show me a demo. Let me see the code. If it’s a mystery box, I won’t touch it.”

2. People Want a Marketplace That Reflects Drupal’s Open Source Values
From contributors and module maintainers to end users and evaluators, we heard a common theme: this effort should feel like Drupal.

Governance should be fair, transparent, and enforceable—not performative.
Monetization is okay—but must support the whole ecosystem, not just those selling templates.
Attribution matters. Contributors want to be credited, not cloned.

If someone else is profiting off my work, I need to at least be recognized.”

Slack also raised the importance of review pathways that aren’t vulnerable to sabotage or bias—suggesting a need for a mix of automation and paid staff to ensure fairness.
3. There’s Real Enthusiasm—for the Right Version of This
End users want this. Freelancers want this. Agencies want this.

85% of end-user survey respondents said vetted templates would increase their likelihood of recommending Drupal.
Agencies see templates as a powerful tool for demos, pre-sales, and fast-start projects.
Contributors are eager to participate—if it’s worth their time.

Key Tensions: Where We’ll Need to Find Balance
Pricing Expectations Don’t Match (Yet)

Users: Many want free or low-cost templates, especially smaller orgs and nonprofits.
Contributors: Cite $300–$1,000 as reasonable price points for a complete, maintained, accessible, and documented product.

Slack conversations added nuance: Some contributors are fine with lower prices if the marketplace generates leads or recognition. Others say without fair compensation, they simply won’t participate.
Certification: Signal or Gate?

Users want badges that help them sort and trust.
Contributors fear certification could slow things down or create an unfair playing field.

Slack participants suggested offering optional badges or tiers, not mandatory certification at launch. A common theme: start lightweight, evolve with real usage.
Monetization: Supportive or Distracting?
There’s broad support for monetization—but only if it’s done with intention.

Contributors want clear, fair revenue splits—and protection against cloned or stripped-down copies.
Users don’t want to encounter bait-and-switch upsells or gated features.
Slack conversations reinforced a desire to avoid WordPress-style chaos, emphasizing community moderation, ranking hygiene, and a meaningful DA role.

This has to feel like Drupal, not like a spammy plugin store.”

What’s Next: Your Turn
The Community public comment period will be open from 29 June 2025 through 13 July 2025. The Marketplace Working Group will meet on 15 July 2025 to review feedback and draft its final recommendation to the board for their go/no-go decision on 24 July 2025.
You will be able to share your thoughts by:

Anonymous feedback form
Issue queue
In Drupal Slack in #drupal-cms-marketplace

Thank You
Thank you to everyone who contributed through surveys, Slack, working sessions, and feedback. Your ideas, critiques, hopes, and flags are shaping this from the inside out. All of this feedback has resulted in a proposal that’s practical, community-aligned, and intentionally minimal.
This Marketplace effort is grounded in community—not just as a value, but as a working method. We’re exploring the Marketplace potential together — ideally, to create something not just to reduce friction for new users, but to grow a stronger, more sustainable Drupal ecosystem for all.
Stay tuned.