Weave Code
Social Media Image Kit Laravel Package
stillat/social-media-image-kit
Stillat's Social Media Image Kit helps Laravel/PHP developers generate social media share images, such as Open Graph cards and post previews, with tools for building and rendering customizable image templates.
Social Media Image Kit is a @statamic addon that provides a framework to help generate social media images for collection entries using Antlers or Blade templates.
Frequently asked questions about Social Media Image Kit
- What is stillat/social-media-image-kit used for?
- It is a Statamic addon delivered as a Laravel package that provides a framework for generating social media share images such as Open Graph cards and post previews. It works by rendering Antlers or Blade templates with entry data and rasterizing the result, typically through a headless browser dependency. Generated files are written to a Laravel filesystem disk, making it a fit for content-driven marketing sites that need per-entry OG images.
- How do I install stillat/social-media-image-kit in a Laravel Statamic application?
- Installation is a standard Composer require plus config publish. The real integration cost is environmental: you need a headless Chromium or Node binary, consistent fonts, sufficient memory per render, and a writable local or remote disk. Provision these in staging first and validate a single generated image end to end before building out templates.
- Does stillat/social-media-image-kit support Statamic 6 and newer Laravel versions?
- Version 1.4.0 relaxes the Composer constraint to allow Statamic 6 installs, but the provided assessment treats Statamic 6 as untested territory unless the maintainer states otherwise. The addon's core dependency is Statamic's augmentation and template rendering, which are exactly the areas most likely to shift across a major version. There is no documented per-major CI coverage in the assessment, so pin the package on your current Statamic major before combining the constraint bump with new feature adoption.
- What are the server requirements for generating social media images with this package?
- Beyond the package's PHP and Laravel constraints, the practical requirements are a headless Chromium or Node renderer, installed fonts, enough memory per render, and a writable or remote filesystem disk. Rendering can fail on font absence, memory ceilings, or timeouts, and those failures often do not surface as traditional PHP errors. Use queue workers and test memory limits in staging before relying on per-entry generation in production.
- Does stillat/social-media-image-kit use Antlers or Blade templates?
- The package supports both Antlers and Blade templates for defining image layouts. In a Statamic context, Antlers is the natural choice because templates can consume entry data directly. The rendered template is then rasterized into the final social share image.
- What is Augmented Entry support in stillat/social-media-image-kit v1.4.0?
- Augmented Entry support means templates can traverse relations and tags through Statamic's augmentation layer instead of hand-rolled lookups. That reduces custom code burden, but it is also the highest-probability source of silent visual regressions because augmented values may change shape for existing templates. Review and test any custom templates after upgrading, since failures can appear as malformed images rather than exceptions.
- What does the Recreate action do and does it run synchronously?
- The control panel Recreate action removes the need for a bespoke regeneration button or console command when you need to rebuild images. The assessment explicitly asks whether it runs synchronously in the request cycle and whether it respects Statamic permissions and throttling, so verify those behaviors in your environment. For larger sites, consider queueing regeneration rather than relying on a synchronous request.
- How is cache invalidation handled when an entry is saved or a relation changes?
- The provided assessment does not document whether invalidation is automatic, manual, or handled only through the new Recreate action. You should verify the behavior for entry saves and relation or tag changes before depending on it. If automatic invalidation is insufficient, plan your own regeneration workflow and consider CDN purges for generated files on remote disks.
- Is stillat/social-media-image-kit suitable for high-volume or serverless deployments?
- It is a poor fit for high-volume, low-latency generation paths because image synthesis is a heavy, asynchronous-by-nature operation. It is also a poor fit for headless or API-only deployments where Statamic's rendering layer is not resident, or for serverless PHP runtimes without a bundled Chromium layer. It fits best in a Laravel and Statamic monolith serving a public marketing or content site with queue workers.
- How actively maintained is stillat/social-media-image-kit and what adoption risks should I consider?
- The assessment notes single-maintainer concentration and a low bus factor, with one new external contributor on the flagship v1.4.0 feature. Version 1.4.0 is a feature release with no documented breaking changes, but it materially expands the dependency surface. Also review the license terms and whether generated output carries any redistribution constraints before adopting it.
Weaver
How can I help you explore Laravel packages today?