Statamic Imageboss Laravel Package

Product Decisions This Supports

• Feature delivery for media-heavy pages: 0.4.0 adds animation support and default center focal points, which directly improves hero images, campaign landing pages, and editorial art direction without custom crop logic. This is a customer-visible quality improvement, not just plumbing.
• Editorial velocity / time-to-publish: automatic ImageBoss cache purging on asset reupload removes a manual CDN step from the publishing workflow. That is a measurable reduction in editorial friction and a good argument for consolidating image handling into the CMS rather than a separate DAM/CDN workflow.
• Build vs. buy for image infrastructure: the package is thin glue between Statamic and ImageBoss. It supports a “buy the CDN, build only the integration” decision and keeps internal engineering effort focused on differentiated product work rather than responsive image transformation pipelines.
• Roadmap scoping: the 0.4.0 requirements bump — PHP 8.3+, Statamic 5–6, Laravel 12 minimum — makes this a fit only if the platform roadmap already includes those upgrades. If not, adopting it creates a forced upgrade dependency.
• Risk and maintenance posture: the package is still pre-1.0. The secret → token config rename is a reminder that minor releases may include breaking config changes. Useful signal for deciding whether to standardize on it now or pilot it behind a feature flag.

When to Consider This Package

Consider it when:

• You are on Statamic 5 or 6, Laravel 12+, and PHP 8.3+, or those upgrades are already planned.
• You use or are willing to adopt ImageBoss as your image CDN and want native Statamic asset integration rather than hand-rolled URL signing and transformation logic.
• You need focal point control, animated image support, and automated cache invalidation as part of the editorial workflow.
• You want a small, tested integration rather than owning a custom image transformation service. The 0.4.0 test suite expansion and Pest v4 upgrade are modest but positive maintenance signals.

Look elsewhere when:

• You are on Laravel 11, PHP 8.2, or older Statamic — 0.4.0 drops support, so this is not adoptable without a platform upgrade.
• You need a stable 1.0 API contract. Pre-1.0 releases can rename config keys (secret to token) and change requirements; budget for migration work or pin versions.
• You want a CDN-agnostic image abstraction. This package is ImageBoss-specific; if vendor flexibility matters, evaluate Glide, Imgix, Cloudflare Images, or a custom transform layer instead.
• You do not already have an ImageBoss subscription or are unwilling to add a vendor dependency for image delivery.

How to Pitch It (Stakeholders)

For executives: This is a small integration package that makes image delivery faster and more consistent for editorial teams. The 0.4.0 release adds animation support, sensible default focal points, and automatic CDN cache clearing when assets are reuploaded — reducing manual steps and improving publishing speed. The main cost is not the package itself; it is the platform requirement: PHP 8.3+, Laravel 12, and Statamic 5–6. If we are already planning those upgrades, this is a low-effort operational improvement. If not, it should wait.

For engineering: Thin Statamic wrapper around ImageBoss URL signing and transformation. 0.4.0 adds animation support, center-default focal points, and cache purging on asset reupload. It also renames the config key secret to token, drops Laravel 11 and PHP 8.2, and requires Laravel 12 minimum. Test coverage was expanded and Pest upgraded to v4. Still pre-1.0, so treat config/API stability as provisional and pin versions in production.