Statamic Imageboss Laravel Package

Technical Evaluation

• Architecture fit: This is a Statamic 5–6 addon targeting Laravel 12+ and PHP 8.3+. It fits teams already on a current Laravel/Statamic stack. It is not compatible with Laravel 11, PHP 8.2, or older Statamic versions.
• Integration feasibility: Moderate. The addon integrates ImageBoss URL signing and image transformation behavior into Statamic assets. New features are additive, but the secret → token config rename and platform minimums require planned migration.
• Technical risk: Breaking changes in 0.4.0 include dropping Laravel 11 and PHP 8.2, plus renaming the signing secret to token. Automatic cache purging on asset reupload introduces an external ImageBoss dependency and possible failure modes. Expanded tests and Pest v4 upgrade improve confidence but do not eliminate migration risk.
• Key questions: Are we already on Laravel 12, PHP 8.3+, and Statamic 5–6? Where is the ImageBoss secret/token configured across environments? Does cache purge require additional ImageBoss API permissions or rate limits? Is purge synchronous or queued? Do default center focal points change existing image rendering? What is the rollback path if signed URLs break after deployment?

Integration Approach

• Stack fit: Suitable only after confirming PHP 8.3+, Laravel 12+, and Statamic 5–6. Teams on older runtimes should pin a pre-0.4.0 release or defer adoption until the platform upgrade is complete.
• Migration path: Upgrade Laravel/PHP/Statamic first if needed. Then upgrade the package, rename secret to token in config/env, clear config caches, and verify signed ImageBoss URLs. Validate asset reupload cache purging in staging before production.
• Compatibility: 0.4.0 explicitly drops Laravel 11 and PHP 8.2. Statamic compatibility is documented as 5–6. The ImageBoss account/token remains a runtime dependency. Pest v4 and test refactors are development-only changes.
• Sequencing: 1) inventory current Laravel/PHP/Statamic versions; 2) upgrade platform dependencies; 3) upgrade package to 0.4.0; 4) migrate config from secret to token; 5) test URL signing, animation support, and focal-point defaults; 6) test reupload cache purging; 7) deploy with rollback to the prior package version if URL generation or purge behavior fails.

Operational Impact

• Maintenance: The package has active releases and improved test coverage, but 0.4.0 narrows runtime compatibility. Teams must track Laravel, PHP, and Statamic upgrade cycles more closely.
• Support: Operationally requires ImageBoss credentials, token rotation procedures, and awareness of cache purge behavior. Support may need access to ImageBoss logs or metrics when purge or signing failures occur.
• Scaling: Image transformation is offloaded to ImageBoss, which can help scaling, but automatic cache purging adds external API calls on asset reupload. Animation support and focal-point defaults should be reviewed for payload and rendering impact.
• Failure modes: Missing or incorrect token breaks signed URLs; cache purge failures can leave stale images or disrupt reupload flows if synchronous; unsupported Laravel/PHP versions fail installation; ImageBoss outages affect image delivery. Default focal points should be regression-tested against existing layouts.
• Ramp-up: Low-to-moderate for Statamic developers, moderate for operations due to the config rename and external cache-purge behavior. Provide an internal runbook covering token rotation, purge verification, and rollback.