Statamic Responsive Images Laravel Package

Product Decisions This Supports

• Media performance as a product requirement. This package makes responsive srcset/sizes, modern formats (WebP/AVIF), and LQIP placeholders the default for Statamic-managed imagery. That directly supports Core Web Vitals goals (LCP, CLS) without asking editors to understand image formats — a strong lever if page-speed targets are tied to SEO, conversion, or paid-acquisition quality scores.
• Build vs. buy for image delivery. It is a thin, MIT-licensed layer over Statamic's native Glide pipeline. For a Statamic property, this replaces a custom responsive-image component or a third-party image CDN for basic needs — a cheaper decision than adopting Cloudinary/imgix when you only need breakpoint variants, art direction, and modern formats.
• Art direction as a content-operations capability. The responsive fieldtype lets editors choose different images and ratios per breakpoint (lg:src, lg:ratio, breakpoint-scoped quality) instead of shipping one crop to every viewport. This is a product decision about editorial control vs. design consistency: more editor agency, more brand-governance process needed.
• Headless/API roadmap. GraphQL support exposes a responsive field and self-augmenting fieldtype data, so the decision to go headless or build a separate front end doesn't force a parallel image pipeline. Reduces rework if the front-end strategy changes.
• Infrastructure cost and caching posture. The README recommends image_manipulation.cache: false so only browser-requested variants are generated. That's a real tradeoff decision: lower storage and server cost, but slower first-load conversions and a warm-up dependency on Glide's internal cache. The responsive:regenerate command and queue support exist for the cached path, so you can choose per environment.
• Scope control on asset containers. excluded_containers and queue configuration let you roll out to high-traffic image surfaces first rather than reprocessing every asset container at once.
• Accessibility and content hygiene. Alt text and HTML attributes flow through the tag, and changelog history shows sustained fixes around alt tags and invalid attributes — useful evidence if you're tracking accessibility conformance.

When to Consider This Package

Adopt when:

• The stack is Statamic 4.0+ and imagery is rendered through Antlers or GraphQL. If you're not on Statamic, this package has no role in your architecture.
• Editors need art direction (different crops/ratios/assets per breakpoint) rather than a single downscaled image.
• You want WebP/AVIF and placeholder generation without a DAM or image CDN contract.
• You accept Glide as the transformation layer and can tune cache behavior per environment.
• The team is small enough that a config-driven addon beats maintaining custom Twig/Blade responsive markup.

Look elsewhere when:

• You need a DAM, governance, rights management, or per-asset approval workflows — this is a rendering addon, not an asset platform.
• You require enterprise support, SLAs, or a large reference base. At ~115 stars and zero dependents, community proof is thin; treat Spatie's broader maintenance record as the quality signal, not adoption.
• You need advanced focal-point/crop intelligence or automated subject detection — crop focus is supported, but this isn't a smart-cropping product.
• You're on older Statamic versions or a non-Laravel CMS; the compatibility surface is narrow and version support has been dropped in the past.
• Your traffic profile makes on-demand Glide generation unacceptable and you can't run the regeneration/queue path — a dedicated image CDN may be the safer operational bet.
• You already have a standardized media pipeline (e.g., laravel-medialibrary) that this would duplicate.

How to Pitch It (Stakeholders)

For executives: A low-cost, MIT-licensed addon that makes our Statamic site serve correctly sized, modern-format images automatically. It targets page-speed and mobile experience — the metrics tied to search ranking and conversion — without a new vendor contract or a custom build. Risk is contained: it's configuration and templating, reversible, and from a well-known open-source vendor. Main caveats are a small public user base and a deliberate tradeoff between storage costs and first-load image latency.

For engineering: Drop-in Composer package for Statamic 4+. Provides a responsive fieldtype, a responsive Antlers tag, breakpoint-scoped parameters (ratio, src, quality, glide), WebP/AVIF toggles, LQIP placeholders, configurable Tailwind-style breakpoints, GraphQL fields, and a responsive:regenerate command with queue support. It composes with Glide rather than replacing it, so existing presets and glide:* parameters still apply. Plan for cache configuration (image_manipulation.cache), queue selection, and container exclusions; publishable views cover markup customization. Known-issue surface from the changelog is small and actively patched — alt attributes, numeric width/height, AVIF attribute leakage, placeholder failure handling, and absolute-URL configuration.