Create a Filament CMS Extension

Package the CMS work that repeats

This page helps package authors prepare an extension another team can evaluate before installing.

A Capell extension should do one useful job and explain its impact clearly: migrations, models, admin screens, widgets, routes, public output, support path, and compatibility.

Build it like normal Laravel code, then document what it touches before asking another team to install it. A good package listing should make install impact obvious before the Composer command appears.

Before submission, a package should be understandable without reading every source file. Include a clear README or overview, a capell.json manifest where applicable, install and uninstall notes, migration impact, screenshots, settings, compatibility, permissions, support expectations, and examples that show the package in a realistic Capell site.

A marketplace listing is not just marketing. It is due diligence for the maintainer who has to decide whether the package belongs in production.

Next steps

• Review extension points before packaging behavior.
• See extension suites for grouped package paths.
• Read account access for verified domains and licences.