Weave Code
Filament Peek Laravel Package
capell-app/filament-peek
Adds a Peek action to Filament resource edit pages so editors can preview a record's front-end page in a modal or new tab without leaving the panel, including unsaved changes and device presets. Handy for content-heavy sites where layouts need checking before publishing.
Private expiring previews of unsaved Capell page and Layout Builder changes.
Frequently asked questions about Filament Peek
- How do I install capell-app/filament-peek in a Laravel Filament application?
- Install it with Composer using composer require capell-app/filament-peek:^1.0, then register the plugin in your Filament panel provider. Publish and review the package config if the README instructs it, and confirm the exact registration snippet and any asset publishing steps from the repository docs. Run the install in a branch first and inspect lockfile changes before deploying.
- Which Laravel, PHP, and Filament versions does Filament Peek support?
- Filament Peek is built for Laravel applications that use Filament admin panels, but the exact PHP, Laravel, and Filament constraints must be confirmed from the package composer.json for the release you install. If your application runs an older Filament major, pin to the last known-compatible release instead of forcing the latest patch. Always run Composer dependency resolution in a non-production branch to verify compatibility.
- How does the Peek action preview unsaved changes on a Filament edit page?
- The plugin adds a Peek action to Filament resource edit pages that opens the record's front-end page in a modal or a new tab without leaving the panel. The preview is rendered from the current form state, so unsaved edits to Capell pages and Layout Builder content can be checked before saving or publishing. This is useful for content-heavy sites where layout and page changes need visual verification.
- Are previews of draft or unpublished pages protected from unauthorized access?
- The package is described as providing private, expiring previews, but you should verify how preview routes and signed URLs are generated in your own application. Confirm that preview endpoints require authenticated panel access and that draft or unpublished records are not reachable through guessable public URLs. Review the plugin's route middleware and any expiry settings before exposing previews to editors in production.
- Does Filament Peek work with CSP and X-Frame-Options when previews open in a modal?
- Modal previews typically render the front-end page in an iframe, so your Content Security Policy frame-ancestors directive and X-Frame-Options headers must allow embedding from the Filament panel origin. If your application sends a strict deny or sameorigin policy that does not match the panel host, the preview will fail to load inside the modal. Test the modal and new-tab modes separately, since the new-tab fallback is less affected by iframe restrictions.
- Is it safe to upgrade Filament Peek from v1.0.45 to v1.0.49?
- v1.0.49 is a patch-level release from v1.0.45, so semver signals low breaking-change risk, but the supplied release note only links to a changelog. Read the full changelog and confirm nothing changed in the areas of authentication, preview routes, or iframe behaviour. Upgrade in a branch with comoser require capell-app/filament-peek:^1.0 and regression test the editor preview workflow before promoting it.
- Do I need to run migrations or publish config and assets for Filament Peek?
- This is an admin-panel preview plugin, so it should not require database schema changes, but you should still confirm from the README whether a config file or front-end assets need publishing. If a config file is published, review the preview URL, route, and expiry settings before rollout. Verify the v1.0.45 to v1.0.49 changelog for any new publish or configuration steps.
- Can editors preview pages using device presets such as mobile or tablet?
- Yes, the plugin includes device presets so editors can check how a page's front end looks at different viewport sizes inside the preview. This helps catch responsive layout issues in Capell page and Layout Builder changes before publishing. Preset behaviour should be validated against your own front-end breakpoints during editor acceptance testing.
- How should I test Filament Peek before rolling it out to production editors?
- Register and configure the plugin and its preview endpoint in a staging environment first, then test authenticated preview, draft and unpublished access, iframe embedding, CSP compatibility, and asset loading. Run an editor pilot with representative content types to validate the modal and new-tab workflows. Roll out to production only after the staging checks pass, keeping a Composer lock rollback available.
- What are the alternatives to Filament Peek for previewing Laravel CMS content?
- Alternatives include building a custom preview route with signed URLs and your own Filament action, or using other Filament preview packages that offer similar modal iframe workflows. A custom implementation gives full control over auth, CSP, and draft handling but requires more plumbing for routes, iframes, and session handling. Filament Peek is mainly a buy-versus-build choice for teams that want a focused preview workflow without custom admin UI work.
Weaver
How can I help you explore Laravel packages today?