Social Images Statamic Laravel Package

Product Decisions This Supports

• Dynamic social/OG image generation: Lets the product render per-page share images (articles, products, landing pages) programmatically instead of maintaining static image assets, directly supporting SEO and social distribution roadmap items.
• Build vs. buy: This release reinforces the "buy" case — the maintenance burden (headless Chrome rendering, rate-limit handling, template engine integration, import/export, external asset loading) is non-trivial. Adopting the package offloads rendering infrastructure and edge-case handling to the vendor.
• Feature enablement: Code templates that can once again pull stylesheets, fonts, and images from external addresses (restored in core 1.1.1) unlock branded, design-consistent share images without bundling every asset locally.
• Operational reliability decisions: The fix for renders stuck showing "queued" after a rate-limit-then-failure means dashboards/status surfaces are now trustworthy — relevant if you plan to expose render status to editors or surface queue health to ops.

When to Consider This Package

Adopt when:

• You run a Laravel/Statamic stack and need dynamic, template-driven social images at scale.
• You can host headless Chrome on your server (the package renders templates via a server-side browser).
• You want Antlers-based templating so designers/editors can own image layouts without engineering involvement.
• You need external asset loading (fonts, styles, CDN images) in templates — now functional again post-1.1.1.

Look elsewhere when:

• Static, hand-designed images are sufficient (the infrastructure cost isn't justified).
• You cannot run a headless browser in your hosting environment.
• You need strict, low-latency rendering under heavy traffic without tolerating rate-limit queuing behavior.
• Security-sensitive surfaces: code templates render via Chrome on your server, and Antlers does not escape by default — per the new docs, you must escape any content authored by third parties. Teams unable to enforce that discipline should weigh the risk carefully.

How to Pitch It (Stakeholders)

For executives: This is a low-risk patch release (bug fixes + docs) on a package that automates social share image generation — improving social click-through without ongoing design labor. No breaking changes; safe to adopt or upgrade.

For engineering: v1.1.2 is a maintenance release. It bumps social-images-core to 1.1.1 (restoring external stylesheet/font/image loading in code templates, plus import/export and text fixes), corrects a UI/status bug where failed-after-rate-limit renders showed as "queued," and adds a security-relevant documentation note: because templates render in server-side Chrome and Antlers doesn't escape output, any third-party-authored content must be escaped. Flag this in your template authoring guidelines before exposing code templates to non-engineers.