Support Docs Reports
Get unstuck.
The support model is deliberately simple while the marketplace is early: docs for common paths, author links for extension questions, reports for trust issues, and GitHub for the registry itself.
Choose the right route.
There is no one inbox for every problem because the marketplace, EmDash core, and each extension have different owners. Start with the closest surface.
Installing plugins
Use the install guide when a plugin bundle, registry URL, capability prompt, or marketplace connection is unclear. Open the install guide →
Site ownersPlugin-specific help
Start on the plugin detail page. Authors can list a support URL, repository, homepage, funding page, and version history. Browse plugin listings →
AuthorsPublisher help
For registration, bundle upload, GitHub releases, review states, and version lifecycle, use the contributor docs first. Read contributor docs →
EveryoneSecurity concerns
Report suspicious listings from their detail pages, and use the security policy for audit behaviour, scanner rules, and escalation. Read security policy →
EveryoneCommunity concerns
Use the community report form for Code of Conduct issues, moderation concerns, impersonation, or project behaviour that does not belong to a single listing. Open community report →
EveryoneMarketplace status
Check live health signals for catalog pages, API responses, badge rendering, feeds, audit queues, and bundle downloads. Check status →
ContributorsProject issues
Use GitHub when the marketplace app, public docs, API contract, or contributor workflow itself needs a fix. Open GitHub issues →
What to expect.
- 01
No central forum yet
Support is routed through docs, author-provided links, listing reports, community reports, status pages, and GitHub issues while the ecosystem is small.
- 02
Authors own extension support
The marketplace reviews bundles and keeps public metadata honest. Feature questions and plugin-specific bugs belong with the extension author.
- 03
Security gets a different path
Security, abuse, impersonation, licensing, and abandoned-listing reports should use the report flow from the affected listing whenever possible.
Need the project maintainers?
If the problem is with emdashcms.org itself rather than a specific extension, open an issue with the exact page, request, or workflow that failed.