Hotspots Widget
Place accessible details and secure lazy targets over a local image.
Check compatibility before using this Beta extension
Capell Membership can install it, but Beta does not mean production-ready. Review compatibility, support, site impact, and likely upgrade work before enabling it.
What Hotspots Widget 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 capturesPlace accessible details and secure lazy targets over a local image.
It is built for teams that need frontend.public static and frontend.interactive across filament admin without turning the project into one-off application code.
Editors get a focused Capell workflow that feels native to the site instead of another disconnected tool to learn.
Developers keep the behaviour inside a reviewed package boundary, with clear install impact, support context, and upgrade expectations.
Use the documentation tab, screenshot gallery, and related extensions on this page to decide how Hotspots Widget fits before enabling it on a production Capell site.
What changes on your site
Review the admin, public, data, scheduled, and command surfaces Hotspots Widget adds when enabled.
- Frontend.public Static
- Frontend.interactive
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/widget-hotspots -
02
Register the extension
php artisan capell:extension:enable widget-hotspots -
03
Clear schema cache
php artisan capell:admin:clear-schemas-cache
Evaluator scenarios
What to inspect in Hotspots Widget
Switch the evaluation lens to see how different roles should assess this package before installing it.
Evaluator scenarios have not been published for this page yet.
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.
