- What does the mia/statamic-image-renderer addon do?
- It is a Statamic addon that wraps Glide image transformations in a single Antlers tag so you can output responsive img and picture markup with generated srcsets. Instead of repeating transformation and markup logic across templates, you pass an asset plus options like sizes, lazy loading, and presets. It targets the presentation layer of a Statamic site rendering HTML server-side, not a general-purpose Laravel image library.
- How do I install mia/statamic-image-renderer in a Statamic project?
- Install it with Composer and let Statamic's addon auto-discovery register it, then use the provided Antlers tag in your templates. There are no schema changes or service-level rewrites required, so the install itself is quick. The larger prerequisite is having an image manipulation backend such as Glide plus a cached derivative store already configured.
- Which Statamic and Laravel versions does the addon support?
- It is described as compatible with Statamic v4 and v5, running inside a Laravel application, but there is no public CI matrix proving support across exact version combinations. Because the package has no dependents, there is no ecosystem signal that a specific Statamic and Laravel pairing works. Pin the package version in composer.json and verify it against your own locked versions before merging to main.
- Does it generate image derivatives itself or rely on Glide?
- The addon wraps Glide transformations rather than replacing them, so it depends on an existing image-derivative strategy such as Glide, a CDN, or a custom asset container pipeline. That backend and its derivative cache are where most of the real integration work lands. Confirm how derivatives are produced and stored in your environment before rolling it out broadly.
- Does the addon support srcsets, sizes, and lazy loading?
- Yes, generating srcset output, accepting sizes attributes, and supporting lazy loading are core parts of its stated purpose. This lets you produce cleaner responsive image markup without repetitive template logic. When piloting it, compare the generated srcset and sizes output against your current approach to validate the contract.
- Can I define custom image presets with this addon?
- Custom presets are a supported feature, letting you standardize transformation sets and reuse them across Antlers templates. Presets help keep markup consistent and reduce repeated width and format options in every tag call. Start with a small set of presets on one low-traffic template before expanding to the rest of the site.
- Does it support WebP, AVIF, and CDN-offloaded images?
- Format and CDN support ultimately depends on the underlying Glide-compatible derivative service and asset container configuration, not the tag alone. Whether you get WebP or AVIF output, signed URLs, or remote asset containers should be verified empirically in staging. Run a representative template through your CDN and asset container setup and inspect the emitted markup and generated files.
- Where are generated images stored and how is the derivative cache invalidated?
- Generated derivatives are written and cached by the underlying Statamic or Glide asset pipeline, so storage location and invalidation behavior follow that configuration. This is the main technical question to answer during integration rather than an install-time concern. Test derivative cache behavior against a staging asset container, including what happens when source images change.
- Can I use mia/statamic-image-renderer in a headless or plain Laravel app?
- It is a poor fit for vanilla Laravel projects and for headless Statamic setups that serve JSON, because responsive image markup is produced client-side in those architectures. The addon's value depends on server-side Antlers rendering of img and picture elements. If your front end is a SPA or API-first, the benefit largely disappears.
- Is the package actively maintained and safe to adopt in production?
- Adoption risk is higher than code risk: the addon has roughly eleven stars, zero dependents, a single-agency maintainer, and a last release around June 2024, so compatibility drift against newer Statamic and Laravel majors is unproven. The functional blast radius is small because image rendering failures are typically cosmetic rather than data-integrity or security issues. The MIT license lets you vendor or fork it if upstream stalls, but you should pilot it template by template and add a smoke test that asserts on srcset output in your own CI.