stephenmcd/mezzanine

CMS framework for Django

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 22 minutes ago
Added to GitGenius on September 14th, 2026
Created on May 29th, 2010
Open Issues & Pull Requests: 65 (+0)
GitHub issues: Enabled
Number of forks: 1,606
Total Stargazers: 4,816 (+0)
Total Subscribers: 244 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 56.2 days
Mean response time: 333.8 days
90th percentile: 2122.4 days
Tracked items: 7

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 7
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 745 days
Stale 30+ days: 6
Stale 90+ days: 3

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (6)
  • needs triage (6)
  • docs (1)
  • released (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Mezzanine is a CMS framework for Django that provides integrated content management functionality out of the box rather than relying on a collection of separate modules.

Mezzanine addresses the need for a content management system built on Django that combines the ease of use of platforms like WordPress with the flexibility of a framework. It bundles most CMS features directly into the core platform, including hierarchical page navigation, WYSIWYG editing, a blog engine, ecommerce capabilities through its Cartridge module, drag-and-drop form building, scheduled publishing, and multi-language support. This integrated approach means developers get a cohesive system where components work together seamlessly rather than assembling functionality from disparate third-party applications.

Mezzanine suits teams already invested in Django who want a full-featured CMS without building one from scratch. It works well for sites requiring blogs, product catalogs, forms, and traditional content management workflows. The platform is designed to be hackable, encouraging developers to extend and customize the codebase rather than working within rigid constraints. It integrates with third-party Django applications, supports custom content types through an API, and includes built-in features like SEO-friendly URLs, user accounts with email verification, comment systems, Disqus integration, and social sharing. The project has been translated into multiple languages and includes a themes marketplace.

Development activity shows consistent maintenance with automated testing and release workflows in place. The codebase follows the Black code style standard, indicating attention to code quality and consistency. The project maintains a dedicated security reporting channel separate from general support, suggesting a mature approach to handling vulnerabilities. Community support is organized through a dedicated mailing list for questions and feature discussions.