Extension Cookbook
Learn Capell extension points from working examples.
- Version
- 1.0.0-beta.22
- Released
- 20 October 2026
- Requires
- Layout Builder
- Licence
- Free
Price Free
Check access and installationCheck compatibility before using this Beta extension
Beta does not mean production-ready. Review compatibility, support, site impact, and likely upgrade work before enabling it.
Check your application before checkout
Use it in your project
Use the cookbook when building a package and you need a concrete starting point. Follow a supported contribution from registration to the focused test that proves it.
Picture it on your site
When adding a package contribution, choose the example nearest to the actual responsibility you need to extend. Follow its registration and focused test before adapting it to your project. A working example saves discovery time, but it still needs your package-specific behaviour, public-output checks and maintenance decisions before it becomes production code.
No workflow evidence published yet
No workflow screenshots are published. Use the demo or documentation to understand the extension before installing.
Build on Capell Foundation
- Explore examples for Core, Admin and Frontend extensions.
- See lifecycle, data and health contracts exercised in tests.
Is this right for your project?
Less repeated CMS work
A shared foundation is valuable when the same content needs to appear in several places without being maintained several times. Decide which records should be shared and which belong to a particular site before you wire up the first form. Editors gain a consistent place to make corrections; developers retain responsibility for the fields and relationships used by their application.
A clear handover
Walk through one everyday task with the person who will own it after launch. Check who can create and change records, how those changes reach the public site, and what happens to existing references when a record is removed. That gives you a useful acceptance test and a clearer handover than simply confirming that the package installed.
Marketplace listings can describe install impact and data access.
This installs as a Composer package. Check its removal guidance and retained-data policy before uninstalling it.
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.
Explore the available extensions on the demo site.
Works with Extension Cookbook
Before you install
Run the commands below in your Capell application. Required dependencies are listed above. After installing a theme, select it for your site in Admin.
-
01
Require the package
composer require capell-app/extension-cookbook -
02
Install the extension
php artisan capell:extension-install capell-app/extension-cookbook
Release and review evidence
Release activity stays visible
These dates come from approved package releases, so you can see the release trail before installing.
- Latest approved release
- v1.0.0-beta.22 Oct 20, 2026
- Recent activity
- 10 approved releases in the last 12 months
Review evidence for this release
Developer example package reviewed with no defects found; its public page lists only example titles and exposes no internal paths, identifiers or configuration.
Review reduces risk, but it is not a permanent security guarantee.
- Reviewed version
- 1.0.0-beta.22
- Approval date
- Oct 16, 2026
Areas reviewed
- Strict, maintainable PHP
- Presentation-only public views
- Actions and typed boundaries
- Clean anonymous public output
- Authorisation and input safety
- Declared package boundaries
- Manifest and migration integrity
- Compatibility and interoperability
- Meaningful behavioural tests
- Security and supply-chain checks
- Performance and operational behaviour
- Theme delivery quality where applicable
- Marketplace claims matched to behaviour
- AI-assisted analysis with human accountability
Accepted limitations
- The package exists to demonstrate extension points, so its example content is reference material rather than a production feature.
Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.
Release notes and maintenance evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
10 releasesv1.0.0-beta.22Oct 20, 2026v1.0.0-beta.21Oct 17, 2026v1.0.0-beta.18Oct 9, 2026v1.0.0-beta.17Oct 8, 2026v1.0.0-beta.16Oct 8, 2026v1.0.0-beta.15Oct 7, 2026v1.0.0-beta.14Oct 4, 2026v1.0.0-beta.13Oct 1, 2026v1.0.0-beta.12Sep 29, 2026v1.0.0-beta.11Sep 23, 2026
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 is the seller and hosts paid marketplace checkout. Any VAT due is calculated and added by Lemon Squeezy at checkout, and Lemon Squeezy 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 Capell licence, support history, and future install access. Capell surfaces a link to the tax receipt issued by Lemon Squeezy. 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.
How do I request a refund?
Use the order link on the Lemon Squeezy receipt and request the refund through the Lemon Squeezy order receipt. If the receipt or order link is unavailable, contact Capell support so the payment and access record can be traced.
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.