AboutMarketplaceOpen source
emdashcms.org is the public marketplace and project hub around EmDash CMS. It is where people discover extensions, publish work, inspect trust signals, follow changes, and find the right support route.
The clearest way to understand the project is to separate the CMS from the public registry that helps people extend it.
Use the core project home when you need the framework, runtime setup, product docs, or upstream CMS source.
Use emdashcms.org when you need plugins, themes, install guidance, publishing docs, catalog data, support routes, or marketplace status.
There is no central support forum yet. Use docs for install help, author links for extension questions, reports for listing concerns, and GitHub for this marketplace app.
The goal is not just a list of downloads. A useful CMS ecosystem also needs docs, review trails, contribution paths, policy, and data that tools can read without scraping pages.
Public plugin and theme listings with metadata, author signals, version history, install counts, downloads, and audit status.
Plain developer-to-developer guides for the CMS model, plugin manifests, capabilities, installation, and comparisons.
Contributor docs and a dashboard for authors to register extensions, upload bundles, and follow review outcomes.
Security policy, scanner rules, fail-closed review, listing reports, moderation notes, and public transparency counts.
Contribution paths for authors, reviewers, testers, moderators, docs maintainers, and people improving the registry itself.
A public plan for what exists now, what should improve next, and what the site will not claim before the ecosystem earns it.
OpenAPI, Atom feeds, badges, llms.txt, and MCP tools for EmDash sites, search engines, and coding agents.
The repository is public, so the public site should be careful about claims, explicit about ownership, and easy to verify.
- 01
Honest about scale The marketplace is young. It should not pretend to have the size, support load, or institutional machinery of an older CMS ecosystem.
- 02
Trust before volume A smaller catalog with declared capabilities, inspectable reviews, and report paths is better than a larger catalog people cannot audit.
- 03
Public by default Source, docs, audit policy, issue work, status signals, and generated marketplace indexes should be linkable and inspectable.
- 04
Security gets a real path Security, abuse, impersonation, licensing, and abandoned-listing concerns belong in the report flow and security policy, not buried in generic support copy.
emdashcms.org is MIT-licensed and built in public. If something looks wrong, start from the page closest to the problem so the report lands with the right context.
Marketplace app, tests, migrations, API code, audit pipeline, and deployment scripts.
Review rules, scanner behaviour, trust tiers, revocation, and escalation routes.
Open a plugin or theme detail page to report security, abuse, licensing, or quality concerns.
Public counts for audit outcomes, reports, deprecations, and catalog health.
What exists now, what comes next, and what the project will not claim early.