Skip to main content
Capell home
My account

We use cookies for essential features and optional analytics.

Manage cookie preferences

Choose which optional cookies Capell may use.

Essential
Always on

Required for Capell to work — login, security, page rendering.

Analytics

Anonymous usage telemetry to improve editor performance.

Marketing

Personalization for the Capell marketing site.

Cookie policy

What a package can register

Capell capability arrives as Laravel packages. A package can register migrations, admin resources, widgets, routes, and render hooks through a declared manifest, so what it adds to a site is visible rather than hidden. The contract below is what authors build against.

Declared manifest Inspectable surface Clean removal
Capell package surface showing a manifest, registered migrations, admin resources, widgets, render hooks, and a health check result.
Browse extensions See packages on the platform

Package authors need to know two things before they invest: what they are allowed to register, and what protects the sites that install their work. Capell answers both with a declared manifest contract.

A package contributes through that manifest, so migrations, admin resources, widgets, routes, and render hooks are visible rather than hidden inside the code. That makes extension impact inspectable, testable, and removable.

The contract in short

  • Register capability through a declared manifest, not hidden side effects.
  • Site owners can review what a package adds before installing it.
  • Health checks confirm an installed package behaves as declared.
  • Packages uninstall cleanly, so trying one is not a permanent commitment.

Build against that contract and your package earns trust from the teams that depend on it.

What a package may register

A package declares what it contributes through its manifest. That keeps extension honest: a site owner can see the migrations, resources, widgets, and hooks a package brings before installing it, and a reviewer can audit them.

Migrations and models Packages register migrations and models through the manifest, so database impact is declared rather than discovered later. See packages
Filament resources and pages A package can add admin resources and pages, giving editors new tools inside the existing Filament workflow. Editor path
Widgets and render hooks Packages register widgets you approve and render hooks while the project keeps ownership of public Blade and rendering. See render rules
Grouped capability Related packages can travel together as suites, making common capability sets easy to choose and review. Explore suites
Hyperreal editorial illustration: A package author at a desk.

Package Extension Proof

See what a Capell package can register, how the manifest contract works, and how review, health checks, and removability keep extensions safe.

Start with the practical question: what does the visitor or editor need to do next? Capell keeps that answer tied to the Laravel app, with shared structures for repeated pages and enough room for custom work when the project genuinely needs it.

Review, health checks, and removal

Authoring is half the story. The other half is what protects a site owner: manifests that can be reviewed, health checks that confirm a package behaves, and removal that does not leave debris behind.

Audit before you install Because a manifest declares what a package registers, the impact is visible before it ever reaches production. Review trust
Confirm a package behaves Health checks verify that an installed package is wired correctly and operating as declared. See operations
Uninstall without debris A package can be removed cleanly, so trying capability does not become a permanent commitment. See packages
Author against a documented contract Package authors follow the documented extension points, manifest, and review expectations. Read docs
Questions

Author questions?

What can a package add to a site?
Through its manifest a package can register migrations, models, admin resources, widgets, routes, and render hooks, all declared up front.
How does a site owner trust an extension?
The manifest makes a package easy to audit before install, and health checks confirm it behaves once installed.
Can a package be removed later?
Yes. Packages are designed to uninstall cleanly, so trying one does not lock a site into a permanent dependency.
Where do I start authoring?
Follow the documented extension points and manifest contract, then publish through the extensions marketplace.
Next step

Extend Capell on a contract you can trust.

If you build reusable Laravel capability, the packages overview and the extensions marketplace show how to register, review, and ship a Capell package safely.

Declared surface Register through a manifest, get reviewed, and remove cleanly.

Browse extensions See packages

Capell learning journey

Step 1 of 4: Learn

Guides for evaluating, planning, and operating Capell.

Keep moving through Extensions

Package-based extension guides.

Loading footer