Statamic Aida Laravel Package

Product Decisions This Supports

• Accessibility compliance roadmap: Alt text is a non-negotiable WCAG 2.x requirement and a growing legal exposure (ADA lawsuits, EU Accessibility Act). This package turns alt-text remediation from a manual content-ops project into an automated CMS workflow, making it a candidate for an accessibility-compliance epic rather than a one-off content cleanup.
• CMS upgrade planning (Statamic 5 → 6): Release 2.2.0 adds Statamic v6 support, which removes a hard blocker from the platform upgrade path. PMs can now treat this addon as compatible with both the current and next major Statamic line, so the accessibility/SEO capability does not need to be re-solved or dropped as part of an upgrade. Practically, this is a dependency-compatibility line item in the upgrade checklist rather than a rebuild.
• SEO and content quality backlog: Descriptive alt text contributes to image search visibility and overall page quality. A PM can position this as a low-effort SEO hygiene feature that ships alongside existing image handling rather than as a standalone initiative.
• Build vs. buy: Buying or adopting an MIT-licensed Statamic addon is materially cheaper than building a custom vision-model integration, queue pipeline, and asset-field UI. The tradeoff is maturity risk: 5 GitHub stars, zero dependents, and a single-maintainer profile mean the PM should budget for due diligence, a fork/ownership contingency, and possibly internal hardening. The v6 support release is modest positive evidence on the maturity axis — the maintainer is tracking platform majors — but it does not change the bus-factor or adoption-risk picture on its own.
• Editorial workflow design: The package creates a decision point around human-in-the-loop review. PMs should decide whether generated alt text is auto-published, queued for editor approval, or used only as a draft suggestion — this affects quality, liability, and editor trust.
• Content migration and backfill: For sites with large existing asset libraries, batch generation can substantially reduce the cost and timeline of accessibility remediation. This supports decisions about migration sequencing, launch readiness, and whether to gate a relaunch on image accessibility.
• Agency and multi-site productization: For agencies managing many Statamic sites, this can become a repeatable accessibility/SEO service offering. The PM should assess whether to standardize it across the portfolio or treat it as an optional per-client add-on. Cross-version support matters here: a portfolio is unlikely to be on a single Statamic major, so v6 compatibility increases the number of client sites a single standardized setup can cover.
• Localization and multilingual content: If the AI provider supports multiple languages, this can support localized alt text at scale — a meaningful differentiator for international sites, but one that requires quality validation before committing to the roadmap.

When to Consider This Package

Consider adoption when:

• The product runs on Statamic v5 or v6 (Laravel-based), and the team wants native CMS integration rather than a separate script or middleware service. v6 support in 2.2.0 means the addon is viable for teams already planning or executing a Statamic major upgrade.
• The site is image-heavy — marketing, publishing, ecommerce, real estate, education, public sector — and manual alt-text authoring is a bottleneck.
• Accessibility compliance is a near-term requirement, audit finding, or contractual obligation, and the team needs a fast remediation path.
• A Statamic major upgrade is on the roadmap and you need to know whether image-accessibility tooling survives it — this release makes the answer "yes, with caveats."
• The team lacks ML/CV engineering capacity but is comfortable configuring an external AI provider/API key.
• A human review step can be inserted into the workflow, so AI-generated text is treated as a draft rather than ground truth.
• The organization accepts MIT-licensed, early-stage open source with a contingency plan (fork, internal maintenance, or replacement).
• The integration can be piloted on a bounded asset set before broader rollout.

Look elsewhere or defer when:

• The CMS is not Statamic — the addon is not portable to plain Laravel, WordPress, Contentful, or other stacks. Note that v6 support extends the supported range, not the supported platform.
• The organization has strict data residency, privacy, or no-third-party-AI policies, or cannot send image assets to an external vision API.
• Enterprise SLAs, security review, and long-term vendor support are mandatory; a 5-star, zero-dependent package will not satisfy procurement, regardless of version coverage.
• High-volume image processing makes per-image AI costs material, or the site needs deterministic, brand-controlled alt text at scale.
• The DAM/CMS workflow requires deep integration (rights metadata, product SKUs, complex taxonomy) beyond generic descriptive alt text.
• The team cannot tolerate AI hallucination or factual errors in alt text without a review queue — for example, regulated product imagery or medical/legal content.
• There is no clear owner for API key management, cost monitoring, and prompt/model updates.

Adoption criteria to validate before committing: which Statamic majors are actually supported and tested (v5 and v6 as of 2.2.0 — confirm both are in CI, not just declared), test coverage, queue/async behavior, batch backfill support, provider configurability, localization support, audit logging, and maintainer responsiveness. On responsiveness, 2.2.0 is a data point in the positive column.

Upgrade note: if you are mid-migration to Statamic v6, pin and verify 2.2.0 explicitly in a staging environment before relying on it — a major-version support commit is not the same as a battle-tested one, and this is a single-maintainer project.

How to Pitch It (Stakeholders)

For executives: This is a low-cost, MIT-licensed Statamic addon that automates image alt-text generation using AI. It directly supports accessibility compliance and SEO with minimal engineering effort, and it can reduce the manual editorial burden of remediating image libraries. The latest release (2.2.0) adds Statamic v6 support, which means the capability stays available through our planned CMS upgrade instead of becoming a dead end — a real reduction in rework risk for a small investment. Because it is still early-stage open source with a small community, we should frame it as a time-boxed pilot rather than a critical-path dependency: validate output quality, privacy posture, and operating cost on a limited asset set, then decide whether to standardize, fork, or replace.

For engineering: It is a Laravel/Statamic addon that hooks into the asset pipeline and calls a configurable AI vision service to produce alt text. Version 2.2.0 adds Statamic v6 support (issue #47), extending the supported platform range — confirm in CI that both v5 and v6 paths are exercised, since the release notes describe the feature but not the test coverage behind it. The integration surface remains small — configuration, API credentials, queue/async processing, and an editor review step — but we still need to verify error handling, rate limits, batch backfill behavior, and test coverage. The MIT license lowers lock-in risk and permits internal hardening if the upstream project stalls.

Recommendation: Run a scoped pilot on a representative image set with human review, measure quality and cost per image, confirm data-handling requirements, and establish an internal fallback plan. Include a Statamic v6 staging check in the pilot if the upgrade is on the roadmap. If validated, adopt as an accessibility/SEO workflow feature; if not, retain the requirements and evaluate alternatives.