Filament Peek
Filament Peek shows unsaved page and Layout Builder edits on your live theme through a private, expiring, signed link.
What Filament Peek 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 capturesFilament Peek shows unsaved page and Layout Builder edits on your live theme through a private, expiring, signed link.
Editors and reviewers can check draft state before publishing without exposing those changes to visitors.
Nothing is written to content until someone saves in the normal editor flow.
Use it when content teams need confidence before a change goes live.
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 Filament Peek adds when enabled.
- Preview
- Filament
- Publishing
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/filament-peek -
02
Register the extension
php artisan capell:extension:enable filament-peek -
03
Clear schema cache
php artisan capell:admin:clear-schemas-cache
Evaluator scenarios
What to inspect in Filament Peek
Switch the evaluation lens to see how different roles should assess this package before installing it.
Filament Peek: evidence for the site owner role
Preview a long heading at phone, tablet and desktop sizes before publishing. Wrapping problems should be visible through the real theme while the live page remains unchanged.
Read more Show less
Inspect this behaviour: The device presets render their unsaved edit through the real theme at each width, so what site owners approve is what visitors get on their actual screen. It's signed and private, which means site owners review the draft without any of it reaching the live page.
A different tool may fit when: The value shows up on pages where a mistake would actually embarrass site owners. When an edit is small and forgiving, a plain preview button does the job without the extra step.
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.
