The Og Laravel Package

Product Decisions This Supports

• Server-side OG image generation vs. third-party SaaS (build vs. buy): The OG lets you render social share cards, blog headers, and marketing visuals directly in your Laravel app without depending on a paid image API (Bannerbear, Vercel OG, Cloudinary transformations, etc.). Useful when social previews are a growth lever and you want to avoid per-image vendor costs or external uptime dependencies.
• Feature roadmap for shareable content: Enables "share this page/article/product" features with branded, dynamic Open Graph images (title, author, price, cover art), which typically lifts click-through on social and messaging channels.
• Template-driven design system: Because layouts and boxes are PHP classes, designers/devs can codify OG templates as reusable components instead of one-off assets, supporting rapid iteration across marketing campaigns and content types.
• Scoping the upgrade to v0.8.0: The breaking changes (PHP 8.3 minimum, Intervention Image v4, modified Border::color(), Image::border(), Box::anchor(), and Layout::render() signatures) are a decision gate — treat this as an upgrade project requiring PHP runtime bump and code audit for any custom Box/Layout implementations or direct Intervention Image usage.
• Platform/runtime planning: Adoption or upgrade implies committing to PHP 8.3+ across the environments serving OG images, which may affect hosting, CI, and container images.
• Risk assessment for custom integrations: Teams that wrote custom Layout or Box classes now have a forced, small refactor — factor this into effort estimates and release timing.

When to Consider This Package

• You are on Laravel and want OG image generation without a separate microservice or SaaS contract.
• You need dynamic, templated social images driven by application data (articles, products, profiles).
• Your environment can run PHP 8.3+ and can accept Intervention Image v4 (check for conflicting intervention/image constraints or direct v2/v3 API usage elsewhere in the app before upgrading).
• You have light custom code or are willing to audit custom Box / Layout implementations for the changed return types and Border::color() string parameter.
• You want stability — note the package is pre-1.0 (v0.8.x), so expect further breaking changes; a "pin and isolate" approach is prudent.
• Look elsewhere if: you need a stable, long-term-versioned API (pre-1.0 risk), you cannot bump to PHP 8.3+, you depend heavily on a different Intervention Image major version, or your OG needs are simple enough for static templates or a managed service.

How to Pitch It (Stakeholders)

To executives: The OG is a Laravel package that generates branded social share images from our own content data, on our own infrastructure — no per-image fees and no third-party dependency. Adopting it supports marketing and growth features like richer social previews and dynamic campaign cards. The trade-off is a small platform commitment (PHP 8.3+) and an upgrade project to reach v0.8.0. Because the package is pre-1.0, we should treat it as an internal, contained integration and pin the version.

To engineering: v0.8.0 is a breaking release — it moves to Intervention Image v4, requires PHP 8.3+, and changes several public signatures (Border::color() now takes a string, Image::border() takes ?string, and the Box::anchor() / Layout::render() return types now use Intervention interfaces). Plan the upgrade as a scoped task: bump PHP, resolve intervention/image to ^4.0, and audit any custom Box or Layout classes and direct Intervention usage. The package is pre-1.0, so lock the version and isolate usage behind our own wrapper to contain future churn.