Proposal Calls for Drupal.org Module Families to Improve Module Selection

A growing number of contributed modules that address similar needs has prompted a proposal to introduce "Module Families" on Drupal.org. The concept would group related projects on dedicated comparison pages, helping users evaluate competing solutions using structured ecosystem data.

The proposal was published by David Dowell in a blog post on Timbers Dev. It addresses a long-standing challenge within Drupal's contrib ecosystem: users often have access to project information such as install counts, release histories, maintainer activity, and issue queues, yet still struggle to determine which module best fits a specific use case.

The proposal arrives as Drupal CMS, Recipes, Drupal AI, and Canvas continue to shape how new users evaluate Drupal. Dowell argues that curated module selections and opinionated workflows increase the need for clearer information about alternative solutions and their relative strengths.

Under the proposal, Drupal.org would introduce Module Family pages that group related projects and display comparison data, including active installations, release history, maintainer counts, security advisory coverage, maintenance status, Drupal CMS inclusion, migration paths, and recommended use cases. Maintainers could also explain how their projects differ from others in the same family and whether collaboration or consolidation has been considered.

Dowell highlights several areas where overlapping solutions can create evaluation challenges, including bulk media upload modules, calendar projects, slider and carousel integrations, and Olivero dark mode implementations. The proposal argues that these projects often serve distinct needs, but the differences are not always apparent in existing Drupal.org project listings.

Additional suggestions include ecosystem badges such as "Included in Drupal CMS," "Most Installed in Family," "Actively Seeking Co-Maintainers," and "Recommended for New Projects." According to the proposal, these signals could provide users with clearer context while remaining evidence-based and transparent.

The proposal does not advocate reducing the number of contributed modules or requiring projects to merge. Instead, it argues that better visibility into overlapping solutions could improve module discovery, surface collaboration opportunities, and make Drupal easier to evaluate while preserving the flexibility that characterises the contrib ecosystem.