Capell Core
Capell Core is the shared Laravel CMS model for multi-site, multilingual Capell content.
What Capell Core 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 Core is the shared Laravel CMS model for multi-site, multilingual Capell content.
It owns pages, layouts, themes, media, translations, settings, and the extension points other packages plug into.
Teams build Capell features as packages on top of this model instead of forking core behaviour.
Use it as the foundation every Capell site and package depends on.
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 Core adds when enabled.
- Cms Core
- Pages
- Media
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/core -
02
Register the extension
php artisan capell:extension:enable core -
03
Clear schema cache
php artisan capell:admin:clear-schemas-cache
Evaluator scenarios
What to inspect in Capell Core
Switch the evaluation lens to see how different roles should assess the Capell platform foundation.
Test Capell Core with a site owner
Change a page several times and reconstruct an earlier state from its event history. The record should retain who changed what while the site remains owned Laravel code rather than a lapsed subscription.
Read more Show less
Expected evidence: That append-only history means site owners can see who changed what and reconstruct any prior version, which is database-of-record territory most CMSes never touch. No subscription can lapse and take that record with it, and three years out site owners are not hostage to anyone's pricing change.
Choose a lighter option when: Owned code still needs hands. Site owners keep a Laravel developer for upgrades and installs, and if teams want a truly zero-maintenance hosted product this is not that trade.
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.
