Statamic Picturesque Laravel Package

Product Decisions This Supports

• Responsive media delivery without a build step. Picturesque gives Statamic content teams a first-party way to render <picture>/srcset markup from CMS-managed assets — useful for decisions like "do we hand-roll image partials, adopt a CDN/imgix-style service, or standardize on a package?" It supports the "build vs. buy vs. package" call by making the package option concrete and low-cost.
• Art direction and multi-source layouts. The headline of v2.2.0 — restoring comma-separated sources — directly re-enables passing multiple image fields/asset sets into a single tag invocation. That unblocks design-led features such as mobile/desktop hero variants, editorial art direction, and dark-mode or locale-specific imagery, which are otherwise awkward to express in templating.
• Regression recovery as a roadmap input. The "bring back" framing signals a prior capability had been removed (likely in the 2.x line) and is now reinstated. For a PM, this is a signal to check whether any shipped features or customer sites relied on the old syntax and were quietly degraded — a candidate for a support/comms task, not a new feature launch.
• Migration posture for the 2.x track. A minor bump (2.1.1 → 2.2.0) with a single restoration change is a low-risk upgrade decision; it supports staying current on the addon rather than pinning, provided you verify template syntax on a staging site.

When to Consider This Package

Consider it when:

• You are on Statamic 3/4+ (Laravel) and want responsive image markup generated from CMS fields without adding a JavaScript image pipeline or a paid image CDN.
• Your editors need to supply multiple sources (e.g., separate mobile and desktop assets, or per-breakpoint fields) and have the tag assemble the <picture> element — the restored comma-separated syntax in v2.2.0 is the specific capability to validate against your templates.
• You value a small, single-purpose addon over a broad asset-management suite, and your team is comfortable owning the surrounding responsive-image strategy (breakpoints, formats, caching).
• You are already on 2.1.x; upgrading to 2.2.0 is a low-effort way to regain lost functionality. Confirm on staging that comma-separated arguments parse as expected in your existing Antlers/Blade templates.

Look elsewhere when:

• You need automatic format conversion (AVIF/WebP) with on-the-fly transforms at scale — that is generally a CDN or image-service concern, not this package's job.
• You are on Statamic 2 or a non-Statamic Laravel app; the tag syntax and asset model are Statamic-specific.
• Your templates depend on the 2.1.x single-source behavior and you have not scheduled a regression pass — verify before upgrading rather than assuming the restored syntax is additive.
• You require a vendor with a formal support/SLA commitment; this is a community addon, so plan for in-house ownership of upgrades.

How to Pitch It (Stakeholders)

For executives: This is a small, free addon that lets our Statamic CMS produce modern responsive image markup — the <picture> element with multiple sources and srcset — directly from content fields, without a new vendor contract or a front-end build pipeline. The v2.2.0 release restores a capability (comma-separated sources) that lets editors designate different images for different contexts, such as mobile versus desktop. It is a minor, low-risk upgrade and a cost-avoidance play against paid image-CDN tooling.

For engineering: Upgrade from 2.1.1 to 2.2.0 is a patch-level risk profile — one PR, restoring the comma-separated sources argument in the Picturesque tag. Two asks: (1) run a template regression pass on any picture tags using multi-source syntax, since the feature was previously removed and may have been worked around; (2) confirm our breakpoint and format strategy still lives where we expect it (in templates/config, not in the package), so we are not implicitly coupling to this addon's internals. Keep an eye on whether the restoration changes argument parsing for existing single-source usages before rolling to production.