Build Filament CMS Extensions

Add new CMS behaviour through known Laravel points

This page helps developers choose the right extension boundary before adding CMS behavior.

Developers can extend Capell with Laravel packages, Filament resources, page types, fields, widgets, render hooks, routes, policies, views, config, and seeders.

The goal is focused extension: add the feature a site needs without rewriting core or leaking admin concerns into the public frontend.

A good extension boundary is easy to explain. The package owns one CMS job, declares what it touches, keeps admin behaviour in the admin, exposes public output through views or render hooks, and gives maintainers a clear install and removal story.

That boundary is healthier than patching core for every project. It also gives future users a way to judge impact before install: schema, commands, settings, routes, widgets, policies, screenshots, docs, compatibility, support, and rollback notes.

Next steps

• Review package groups before choosing a boundary.
• Create an extension when the job repeats.
• Check the glossary for package terminology.