Extension Cookbook
Learn Capell extension points from working examples.
- Version
- 1.0.0-beta.25
- Released
- 10 November 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
What it solves
The problem
Package authors cannot always see how an extension contract works in a complete example.
What your site gets
A site developer has runnable examples of released Capell extension contracts.
Questions buyers ask
- Who is the cookbook for?
- It is for package authors learning to use released Capell extension contracts.
- Can examples be run and tested?
- Yes. The package contains runnable examples and focused tests for their behaviour.
- Which contracts do examples cover?
- Examples cover released Core, Admin, Frontend, lifecycle, data, health and content-graph contracts.
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.
Add this free package to your account, then review compatibility and site impact before installing it.
This listing has no page of its own in the demo. Open the demo to see Capell running.
Works with Extension Cookbook
Before you install
Review the impact below before running the commands in a covered Capell application, starting with a non-production environment. Required dependencies are listed above.
- Admin and public surfaces
- The package declares: administration screens, frontend integration, public routes. Review the release documentation for configuration and exposure in your application.
- Data and migrations
- Database migrations are declared. The installation flow can change your database; back up data and review the release migrations before installing. Reads and writes Capell content structures required by the package; public output receives rendered content only.
- Background work
- Scheduled background work is declared. Keep the host scheduler running and check the release documentation for queue workers, frequencies and pruning configuration.
- Access controls
- Package access controls are declared. Review role grants and the host authorisation configuration before allowing users into the new workflow.
- Removal and retained data
- A verified uninstall and retained-data assessment is not available here. Removing the Composer package does not establish that its data is deleted. Confirm cleanup, retention and dependencies with the publisher before removal.
-
01
Require the package
composer require capell-app/extension-cookbook:^1.0.0@beta -
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.25 Nov 10, 2026
- Recent activity
- 13 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.25
- Approval date
- Nov 8, 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
Version history
Showing the 10 most recent of 13 approved releases-
v1.0.0-beta.25Nov 10, 2026 -
v1.0.0-beta.24Nov 2, 2026 -
v1.0.0-beta.23Oct 28, 2026 -
v1.0.0-beta.22Oct 20, 2026 -
v1.0.0-beta.21Oct 17, 2026 -
v1.0.0-beta.18Oct 9, 2026 -
v1.0.0-beta.17Oct 8, 2026 -
v1.0.0-beta.16Oct 8, 2026 -
v1.0.0-beta.15Oct 7, 2026 -
v1.0.0-beta.14Oct 4, 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?
There is no self-service refund button. Email [email protected] within 14 days of purchase with the account email, the order or receipt reference, the package and your reason. Capell reviews the recorded purchase and, where approved, submits the refund through Lemon Squeezy. Read the Refund Policy
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.