Capell Inertia
Use an Inertia frontend with Capell's publishing workflow.
- Version
- 1.1.0-beta.54
- Released
- 10 November 2026
- Requires
- Api
- 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
Our frontend team cannot serve Capell pages through an Inertia theme without a bridge.
What your site gets
Our site can render public pages through an active Inertia theme and registered client adapter.
Questions buyers ask
- When does the bridge render public pages?
- When an Inertia theme is active, public pages use the configured root view, component name and adapter.
- Can teams use React or Vue themes?
- Teams can use React or Vue Inertia themes while keeping the normal Capell content workflow.
- Does the bridge store page content?
- It has no schema impact; persistence remains with Core or required packages.
Use it in your project
Connect the public page response to a registered client adapter. Choose the matching React or Vue adapter for your theme while editors keep using Capell.
Picture it on your site
For a client-driven theme, choose the React or Vue path before connecting a representative public page. Review navigation and missing-page handling with that adapter in place. Editors can keep their Capell workflow, while your developers own the client components, assets and interaction design that turn the page data into the finished frontend.
No workflow evidence published yet
No workflow screenshots are published. Use the demo or documentation to understand the extension before installing.
Connect content to your website
- Resolve Capell pages into Inertia responses.
- Configure the public root view and client adapter.
Is this right for your project?
Choose the delivery boundary
Decide whether your application needs rendered pages, a separate frontend or another service reading published content. A delivery package is useful when it makes that boundary explicit instead of asking another system to understand private editing state. Your Laravel application still owns its routes, presentation and access decisions; the published contract is what a consuming frontend should build against.
Check a real consuming application
Test one published page from end to end, including its layout, language, missing-content response and links to other pages. Compare that with an unpublished page so you can see the boundary working. Plan how the consuming application refreshes content after a change, rather than assuming that an endpoint or successful response also solves caching and deployment.
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 Capell Inertia
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: frontend integration. Review the release documentation for configuration and exposure in your application.
- Data and migrations
- The manifest declares no package migrations. This does not establish that installation or runtime operations make no data changes. May connect configured Capell content, media, or integration metadata to the named service boundaries for this package.
- Background work
- A complete jobs and scheduler assessment is not available here. Confirm background processing and worker requirements with the publisher.
- Access controls
- Access-control changes are not described here. Confirm the required roles and grants with the publisher.
- 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/inertia:^1.1.0@beta -
02
Install the extension
php artisan capell:extension-install capell-app/inertia
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.1.0-beta.54 Nov 10, 2026
- Recent activity
- 14 approved releases in the last 12 months
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 14 approved releases-
v1.1.0-beta.54Nov 10, 2026 -
v1.1.0-beta.53Nov 2, 2026 -
v1.1.0-beta.52Oct 28, 2026 -
v1.1.0-beta.51Oct 20, 2026 -
v1.1.0-beta.50Oct 17, 2026 -
v1.1.0-beta.49Oct 10, 2026 -
v1.1.0-beta.47Oct 9, 2026 -
v1.1.0-beta.46Oct 8, 2026 -
v1.1.0-beta.45Oct 8, 2026 -
v1.1.0-beta.44Oct 7, 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.