Frontend Authoring
Frontend Authoring lets admins edit page titles, descriptions, and content from the live site after the page loads.
What Frontend Authoring helps you do
Active Capell Membership access covers the curated Released catalogue and lets the account opt into Beta extensions after reviewing their risk.
Workflow screenshots
6 capturesFrontend Authoring lets admins edit page titles, descriptions, and content from the live site after the page loads.
Visitors and caches only ever see ordinary HTML, so public output stays clean.
Small content fixes do not require a full admin round-trip for every tweak.
Use it when editors need lightweight live-page updates without exposing authoring chrome to the public.
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 Frontend Authoring adds when enabled.
- Frontend Authoring
- Frontend
- Editor
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-authoring -
02
Register the extension
php artisan capell:extension:enable frontend-authoring -
03
Clear schema cache
php artisan capell:admin:clear-schemas-cache
Evaluator scenarios
What to inspect in Frontend Authoring
Switch the evaluation lens to see how different roles should assess this package before installing it.
Edit the live page, keep the cache — what to verify
Correct a homepage value in place and observe cache invalidation. Only pages depending on that record should refresh, with no developer release required.
Read more Show less
Inspect this behaviour: The editing tools reach site owners through a second request tied to the editor session, so they never sit in the cached HTML a visitor gets. Saving one field clears only the cached URLs that render it, not the whole site, so it's live in seconds.
A different tool may fit when: Anything structural still needs a Laravel developer, and site owners keep one on call. This wins for text and image tweaks, not layout surgery.
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.
