Storyblok Bundle Laravel Package

Product Decisions This Supports

• Headless CMS build vs. buy: whether to standardize on Storyblok for content delivery and use a thin framework integration instead of building content management in-house.
• Integration layer: buy vs. build: this bundle is glue code (DI configuration, webhook routing, content/webhook handler wiring). The decision is whether ~a few hundred lines of internal glue is worth outsourcing to a third-party 0.x package.
• Exit cost / lock-in modeling: the bundle is a thin layer over Storyblok's HTTP API, so switching to a maintained SDK or hand-rolled client later is a contained cost — useful input for vendor risk scoring.
• Framework fit: note this is a Symfony bundle, not a Laravel package. If our stack is Laravel-first, this informs a "reuse" vs. "adapt via storyblok/php-client" decision for the roadmap.
• Editorial workflow roadmap: the WebhookHandlerInterface auto-configuration fix directly supports webhook-driven cache invalidation, preview rebuilds, and publish-triggered pipelines — the plumbing behind "editors publish, site updates."

When to Consider This Package

Consider it when:

• The application is Symfony (the package is a bundle; adoption in Laravel requires forking or bypassing the bundle layer).
• Storyblok is already the chosen CMS and you want typed webhook handling plus container wiring rather than raw HTTP calls in controllers.
• You can pin the version and tolerate pre-1.0 churn — 0.4.x means the public API is not yet stable and minor bumps may break you.
• You want a small, auditable dependency rather than a larger CMS framework.

Look elsewhere when:

• The stack is Laravel or framework-agnostic PHP — use the Storyblok PHP client and a local service class instead.
• You need vendor-backed support, a security-response SLA, or a long-term maintenance guarantee.
• Your content model is simple enough that a plain REST client with a caching layer is cheaper than an integration bundle.
• You require SemVer stability for a multi-year product surface.

How to Pitch It (Stakeholders)

Executives: A small open-source glue library for Symfony applications that use Storyblok as their CMS. Release 0.4.1 is a maintenance release — CI dependency bumps plus one bug fix that makes custom webhook handlers register automatically. No new features, no breaking changes, no migration cost for anyone already on 0.4.0. The strategic takeaway is unchanged: this is a convenience dependency, not a platform commitment, and it is replaceable at low cost if the project stalls.

Engineering: 0.4.1 raises the floor on developer experience — WebhookHandlerInterface implementations now wire themselves into the container, removing manual service tagging that was an easy source of silent misconfiguration. Treat the project as pre-1.0: pin the exact version, read the changelog before minor bumps, and keep our own Storyblok client calls behind an interface so a fork or replacement stays a one-file change.

Risk note: single-maintainer, sub-1.0, CI-only release cadence in this version. Acceptable for internal tooling; require an exit plan if adopted for a customer-facing product.