- How do I install and configure daun/statamic-asset-thumbnails?
- Install the addon with Composer, then publish its configuration file if the package provides one. Define your reusable thumbnail presets in config and reference those preset names from your templates. The addon is designed as a lightweight Statamic addon with no external service required, so setup is mainly Composer and config.
- Does this package work with both Antlers and Blade templates?
- Yes, the package is described as template-friendly for both Antlers and Blade. You define thumbnail presets and request them from templates instead of manually building image variant URLs. This keeps image sizing consistent across both templating approaches.
- How do thumbnail presets work and can I define custom sizes?
- Thumbnail presets are reusable configuration entries that define dimensions and fit or crop behavior. You create presets for the image sizes your site needs and reference the preset by name in templates. This avoids hand-building URLs and keeps responsive image workflows consistent.
- Are generated thumbnails cached and reusable?
- Yes, the addon is designed to keep generated thumbnails cacheable and reusable. Once a thumbnail has been generated for an asset and preset, it can be served again without recreating the variant manually. This helps avoid repeated image processing work in templates and the control panel.
- Does it require an external image service such as Imgix or Cloudinary?
- No, the overview states that it is a lightweight setup with no external service required. Thumbnails are generated and served through the Statamic addon itself. That makes it a simpler option if you want preset-based thumbnails without adding a third-party image CDN.
- Which Statamic and Laravel versions are supported?
- The provided context does not list a specific Statamic or Laravel version matrix. Check the package composer.json and README for the supported Statamic, Laravel, and PHP constraints before adopting it. Because it is a Statamic addon, confirm compatibility with your Statamic major version first.
- How does the addon handle missing assets or failed thumbnail generation?
- The release notes indicate that version 1.2.1 adds guarding for missing assets, which should make missing-asset behavior safer than earlier releases. The exact behavior, such as logging, skipping, or throwing an exception, should be verified in the README and by testing your templates. Review any existing error handling if you depend on specific exception types.
- Can I use it with Statamic asset containers on local disks or S3?
- The addon works with Statamic’s asset container structure, so it is intended to fit normal Statamic asset workflows. Actual storage and caching behavior depends on how your containers and filesystem disks are configured. Test generation and serving against your target disk, especially for remote storage such as S3.
- Is this addon suitable for production use and how should I test it?
- It is designed to be lightweight and cacheable, which suits typical production image workflows. Before deploying, test thumbnail generation with representative assets, including large images and missing files. Confirm that your cache and filesystem permissions allow generated thumbnails to be written and served correctly.
- What are alternatives to this addon for generating thumbnails in Statamic?
- Alternatives include Statamic’s built-in image manipulation features, manually defined asset variants, or an external image CDN such as Imgix or Cloudinary. This addon is aimed at teams that want reusable preset names in Antlers and Blade without an external service. Choose based on whether you need local caching, CDN delivery, or more advanced transformation features.