Rokka Io Api Platform Bridge Laravel Package

Product Decisions This Supports

• Image delivery architecture: this bridge is the integration layer between API Platform and Rokka.io, letting API resources expose Rokka-backed image URLs and transformations declaratively. It directly supports the decision to standardize image processing/CDN on Rokka rather than building URL signing, transform presets, and stack configuration in-house.
• Build vs. buy: adopting the bridge replaces custom glue code for Rokka URL generation per resource. The build alternative is a small internal library; the buy argument is faster delivery and fewer bespoke edge cases, at the cost of a niche third-party dependency.
• Roadmap / platform modernization: release 1.1.0 adds PHP 8.* and Symfony 5/6 compatibility with no indicated breaking changes. This unblocks scheduling API Platform upgrades alongside wider PHP/Symfony modernization and removes the package as an upgrade blocker.
• Use cases: headless commerce and catalog APIs, CMS/media APIs, and any API Platform service that needs responsive image variants (crop, resize, format negotiation) served through a CDN.
• Vendor and lock-in trade-off: coupling the API layer to Rokka via this bridge raises switching costs. Keep image URL generation behind a thin internal abstraction so the CDN decision remains reversible.

When to Consider This Package

Consider adoption when:

• You are already using (or committed to) API Platform for your API layer and Rokka.io as the image processing/CDN backend.
• You want config-driven, consistent image transformations in API responses instead of ad hoc URL construction scattered across resources.
• Your stack is on PHP 8 and Symfony 5 or 6 — now explicitly supported by 1.1.0 — with no legacy constraints forcing older versions.
• The team values a small, single-purpose integration over maintaining bespoke Rokka plumbing.

Look elsewhere when:

• You are not using API Platform, or are on a Laravel-only stack without Symfony/API Platform components — the bridge is Symfony-oriented and will add little value.
• Your image backend is Cloudinary, imgix, Imgproxy, or an in-house service.
• Your needs are minimal (a handful of signed URLs) and a lightweight helper would suffice.
• You require vendor-backed SLAs, guaranteed long-term maintenance, or broad community support — this is a niche package with a narrow maintainer base; treat bus-factor and upgrade cadence as risks.
• You need features beyond URL/transform integration (e.g., upload orchestration, DAM workflows).

How to Pitch It (Stakeholders)

For executives: This package is a focused integration that connects our API layer to Rokka's image CDN, so image variants are delivered consistently without custom engineering effort. The 1.1.0 release confirms it runs on current PHP 8 and Symfony 5/6, which reduces risk in our platform upgrade roadmap. The main exposure is dependency on Rokka and on a small, single-maintainer open-source package; we mitigate that by keeping image URL generation behind an internal abstraction and pinning versions.

For engineering: It is a thin, declarative bridge — configure Rokka transforms and expose them through API Platform resources rather than hand-rolling signed URLs. Upgrading to 1.1.0 is non-breaking per the release notes and enables PHP 8 / Symfony 5–6. Before adoption, verify test coverage, pin the version, and wrap usage in an adapter so a CDN swap stays feasible.