Drupal

Few content management platforms cover as wide a range as Drupal, which runs everything from a personal weblog to a large community-driven site. Because its module ecosystem has already built so much, most of what a project needs can often be assembled before anyone writes a line of code.

Development does not happen on GitHub. The international Drupal community has run its own infrastructure since 2001, hosting the GitLab repository, the issue queue and the documentation, and the GitHub repository mirrors that work. Every issue there automatically creates a community-accessible fork you can contribute to.

Several long-running practices come attached to the platform.

• Module ecosystem: thousands of free and open-source modules extend the core feature set.
• Change records: every notable breaking change and new feature since 2011 is documented and searchable.
• Security advisories: a published list, available by email or RSS, maintained by a security team with a documented reporting process.
• Issue forks: contribution flows through the issue queue, where each issue gets its own fork and merge request.
• Service providers: over a thousand firms offer design, strategy, development and hosting for anyone who would rather not do it alone.

A brief introduction ships in the repository as USAGE.txt, with guides and API references on the documentation site. Anyone building commercially should also read the core license and the separate trademark and logo policy before putting the name on anything.