Capell Frontend
Capell Frontend delivers published pages safely with routing, site context, themes, assets, and visitor HTML.
What Capell Frontend helps you do
Paid checkout adds access to the purchasing account after payment. Add a free package to your account, then review compatibility and site impact before installing it.
Workflow screenshots
6 capturesCapell Frontend delivers published pages safely with routing, site context, themes, assets, and visitor HTML.
Public output stays free of editor state, package internals, and admin-only metadata.
Themes and packages render through this delivery layer instead of inventing their own public stack.
Use it as the public rendering boundary for every Capell site.
Review the documentation and screenshots on this page before enabling it on a production Capell site.
What changes on your site
Review the admin, public, data, scheduled, and command surfaces Capell Frontend adds when enabled.
- Frontend
- Rendering
- Cache
Install after you have checked the fit.
Confirm version compatibility, support, data access, migrations, retained data, and removal steps first. Then install the Composer package from the account that owns access.
-
01
Require the package
composer require capell-app/frontend -
02
Register the extension
php artisan capell:extension:enable frontend -
03
Clear schema cache
php artisan capell:admin:clear-schemas-cache
Evaluator scenarios
What to inspect in Capell Frontend
Switch the evaluation lens to see how different roles should assess the Capell platform foundation.
A dynamic CMS that serves like static files — what to verify
Request a busy cached page repeatedly and compare it with gated content. Public traffic should resolve from a flat-file origin path while personalized access is never frozen into the shared response.
Read more Show less
Operational evidence to check: The cache inspects its own output and vetoes itself rather than trusting the app to have stripped editor chrome, so a signed admin URL can never get baked into a shareable page. Site owners get static-file speed without paying for it in leaked private content.
Decision note: This protects the render boundary, not everything. Whatever custom code the site’s developer adds still needs its own care, so site owners do not treat it as a blanket security guarantee.
Release and download evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
0 releasesNo package release history is published yet. Check the source and documentation before installing.
Before checkout
Know who owns access and what happens next
Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.
Who processes the payment and taxes?
Lemon Squeezy hosts paid marketplace checkout and issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.
Which account owns the licence?
The signed-in customer account that completes checkout owns the licence, receipt, support history, and future install access. Use the intended organisation account before paying.
How does the site receive package access?
The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.
What happens if checkout is cancelled or expires?
No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.
What should I do if access does not appear?
Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.
No approved reviews yet. Reviews from eligible customers appear here after moderation.
