- What does tfd/statamic-aida do?
- It is a Statamic addon that automates image alt text generation using AI to improve accessibility and SEO. It integrates through Statamic's addon lifecycle and can expose configuration and commands. The provided overview and evaluation focus on generating alt text for assets rather than being a standalone Laravel library.
- How do I install tfd/statamic-aida in a Laravel Statamic app?
- Install it with composer require tfd/statamic-aida, then publish its config and set the required API key in the environment. The evaluation notes the expected effort is hours, not sprints, because the integration surface is small. Verify the package's service provider registration and any per-container enablement steps in the README.
- Does tfd/statamic-aida support Statamic 4 and Statamic 5?
- The package is a Statamic addon, and addons commonly break across Statamic majors, so you must check the Composer constraints against your installed major. The evaluation explicitly flags verifying Statamic 4 versus 5 and the Laravel and PHP floor before adoption. Do not assume compatibility from the package name alone; test in staging first.
- How are API keys and AI providers configured for Statamic Aida?
- The expected setup is to publish the addon config and store the API key in the environment rather than committing secrets. The evaluation's key open question is whether the AI provider is abstracted or hardcoded and where keys are stored. Confirm in the README and config whether multiple providers or models are supported.
- Does tfd/statamic-aida generate alt text synchronously on upload or via a queue?
- The evaluation says this must be confirmed because it determines whether an API outage can become a CMS outage. A queued implementation should respect Laravel queues, retries, and backoff; a synchronous one adds latency to asset uploads. Check the addon's event listeners and job usage before production.
- Will tfd/statamic-aida overwrite existing image alt text I wrote manually?
- The evaluation flags overwrite behavior as a write-path risk because replacing editorial alt text can destroy manual work. The safe pattern is to generate only when alt text is empty or to require a review and approval state before publish. Verify the addon's behavior on asset save and upload events before enabling it broadly.
- Can tfd/statamic-aida bulk backfill alt text for existing Statamic assets?
- The evaluation lists bulk backfill as a key question and recommends treating historical asset backfill as a separate step from new uploads. A good implementation would provide an idempotent command and cache results by image hash to avoid duplicate spend. Check whether such a command exists and how it handles retries and cost limits.
- Does Statamic Aida support multi-site and localized alt text?
- Alt text quality depends on language, so multi-site support matters if you publish in more than one locale. The evaluation asks whether alt text can be localized per site, but the provided context does not confirm the implementation. Test with a multi-site asset container and verify where the generated value is stored.
- How does tfd/statamic-aida handle SVG, PDF, and animated GIF assets?
- Vision models may not handle every asset type well, so unsupported types should be skipped cleanly rather than producing misleading alt text. The evaluation explicitly asks how asset types are handled. Review the addon's type checks and test representative files before enabling it across a container.
- What are the production risks of using AI-generated alt text in Statamic?
- The dominant risks are vendor maintenance, AI provider API changes, cost per image, and accessibility correctness because a confidently wrong description can be worse than none. The package has MIT licensing but little production validation and no automatic quality gate. Run a contained pilot on one low-traffic asset container, inspect output, and add editorial review before scaling.