Drupal Clarifies Marketplace and Community Pathways for Site Templates
Drupal has introduced a dual-pathway model for site templates, distinguishing between curated Marketplace offerings and openly contributed community projects.
The approach separates production-ready solutions from experimental work while maintaining a link between the two. Marketplace templates are designed as reviewed, reliable starting points built on Drupal CMS, whereas community templates are published as general projects without formal approval requirements.
According to a post by Pamela Barone on Drupal.org, Marketplace templates undergo evaluation against standards covering security, accessibility aligned with WCAG 2.2 AA guidelines, performance, and code quality. These templates are also expected to include structured documentation, ongoing maintenance commitments, and user support provisions.
The Marketplace model currently limits participation to Drupal Certified Partners and individual contributors identified as Ripplemakers. It also introduces a commercial layer, enabling template creators to generate revenue while contributing to the sustainability of the Drupal Association through revenue sharing.
Community site templates follow a more open model. Contributors can publish templates directly as general projects on Drupal.org without undergoing review. These templates may be built using either Drupal CMS or Drupal Core and are not required to meet Marketplace-level standards.
This flexibility allows contributors to explore alternative implementations and test ideas that may not fit curated criteria. It supports a broader range of approaches and lowers the barrier to entry for participation in the Drupal ecosystem.
The two pathways are connected through a progression model. Community templates that align with Marketplace requirements over time may be considered for inclusion in the curated catalogue, allowing experimental work to evolve into production-ready offerings.

