- How do I install statamic-imagehotspots in a Laravel application?
- Install it with Composer using composer require darinlarimore/statamic-imagehotspots. It is a Statamic addon, so it registers itself through its addon service provider and you do not need to add anything to config/app.php. Your application must already run Statamic on top of Laravel, since the package depends on Statamic's fieldtype and Control Panel APIs. After installing, add the Image Hotspots fieldtype to an asset container blueprint to start placing markers.
- Which Laravel and Statamic versions does statamic-imagehotspots support?
- Version 2.2.1 is built to work with Statamic 5, including releases before 5.73, Statamic 5.73 and newer, and Statamic 6, which means it runs on whichever Laravel versions those Statamic releases require. Because release notes and composer.json constraints can drift apart, always check the declared constraints in the package's composer.json before committing to an upgrade. If you are planning a Statamic 6 move, install this patch first so addon issues are separated from platform issues.
- How do I add clickable hotspots to an image field in a Statamic blueprint?
- Create or edit a field in the relevant asset container blueprint and choose the Image Hotspots fieldtype. Editors then open an asset in the Control Panel and drag markers onto the image, attaching tooltip or field content to each one. The saved data includes each hotspot's coordinates plus its metadata, which is what your templates later read. No separate settings screen or database table is involved.
- How do I render image hotspots in an Antlers template?
- The fieldtype exposes the hotspot coordinates and metadata to your Antlers views, so you loop over the hotspots and output each marker positioned over the image, with the tooltip content rendered inside it. Coordinates are stored relative to the image, which keeps marker positions aligned when the image scales on smaller screens. You control the marker markup and styling, and the addon's configurable marker styling options let you adjust the default appearance without rewriting the whole template.
- Does statamic-imagehotspots work with Statamic 6?
- Yes. Version 2.2.1 resolves the asset container blueprint route defensively, using the older statamic.cp.blueprints.asset-containers.edit route name where it exists and the newer name on Statamic 5.73+ and Statamic 6. It also removes the unused @statamic/cms npm dependency, which is a build hygiene change rather than a functional one. There are no schema or configuration changes, so it is a straightforward patch-level update.
- Is it safe to upgrade statamic-imagehotspots to 2.2.1 in production?
- The change is small and self-contained, so the practical risk is low. Update on a staging or low-traffic environment first, then confirm the asset container fieldtype still renders and that its blueprint edit link navigates correctly on your current Statamic version. No data migration or asset republish is expected, though a vendor:publish sanity check on any published views or config is cheap insurance. Rolling back is just a version pin in composer.json.
- Can hotspot tooltips render custom HTML content?
- Yes, tooltips and popovers accept custom HTML or content pulled from other fields, which is what makes the fieldtype useful for product callouts, annotated diagrams, and infographics. Because that HTML is rendered in the front end, treat hotspot content with the same trust level as any other editor-supplied rich content in your Statamic site. If non-trusted users can edit entries, sanitize the output or restrict the field to roles you trust.
- How is statamic-imagehotspots tested across Statamic 5, 5.73+ and Statamic 6?
- The multi-version compatibility claim is only as strong as the automated proof behind it, so check whether the repository runs a CI matrix covering Statamic 5.x below 5.73, 5.73+, and 6.x before you depend on all three bands. The route resolution itself should be an explicit allowlist of known route names rather than a broad existence check, since a broad check can mask genuine misconfiguration. Unit tests can cover the route lookup logic, but the Control Panel drag-and-drop behaviour generally still needs manual verification in a real Statamic install.
- What are alternatives to using a hotspot fieldtype for interactive images in Statamic?
- You can build a custom fieldtype yourself, which gives full control but means owning the Control Panel JavaScript and the coordinate storage format. Another option is placing an image map or hotspot library inside a Bard or HTML field and hardcoding the marker data, which is quicker to start but pushes maintenance onto content editors. The addon's value is that it keeps hotspot authoring inside the Control Panel and exposes clean coordinate data to Antlers, so evaluate alternatives against how much editor workflow you are willing to give up.
- Who maintains statamic-imagehotspots and how stable is it long term?
- The addon is maintained by Darin Larimore as a single-maintainer package, so plan for typical open-source risk: pin the version, watch releases, and be ready to fork if needed. The main recurring maintenance concern is coupling to Statamic's internal Control Panel route names; version 2.2.1 tolerates the two known asset container blueprint route names, but a future upstream rename could break it again. Treat each Statamic major upgrade as a prompt to retest hotspot authoring in the Control Panel rather than assuming compatibility.