Laravel Ai Docs Laravel Package

Product Decisions This Supports

• Build vs. buy for AI-facing documentation. laravel-ai-docs turns a Laravel app's markdown docs into a structured, machine-readable surface for AI assistants and agents. The decision this informs: do we hand-roll an llms.txt / context endpoint, or adopt a maintained package? A single-maintainer package with a small, steady release cadence favors buy — unless AI docs are a core product surface.
• Docs information architecture. v1.5.0 adds folder labels sourced from index.md group front matter (#19). This is a content-modeling decision, not just a rendering one: it lets us group docs into named sections declaratively in markdown rather than in config or code. That makes docs taxonomy a content-owner responsibility instead of an engineering one — worth weighing when deciding who owns the docs repo.
• Roadmap signal on AI discoverability. The cadence (v1.4.0 → v1.5.0) shows incremental refinement of the output format and navigation rather than new integration surfaces. If our roadmap depends on AI doc features not yet present (per-version snapshots, auth-scoped docs, per-audience context slices), this release does not shorten that gap — plan to build on top rather than wait.
• Feature scoping for internal tooling. If we expose docs to AI coding assistants or in-product help, folder grouping directly affects retrieval quality and how agents cite sections. Treat it as a small quality win that reduces the case for a custom docs pipeline.
• Use cases it plausibly serves: AI assistant context for internal Laravel apps, customer-facing developer docs, in-repo documentation served to agents, and support-deflection content consumed by LLM tools.

When to Consider This Package

Adopt when:

• Docs already live as markdown inside a Laravel repo and need to be exposed to AI tools without a separate documentation platform.
• You want low-configuration, convention-driven structure — front matter and folder index.md files rather than a database or CMS.
• The docs surface is internal or secondary — an aid to developer experience, not a revenue-critical, SLA-bound product.
• You can accept a single-maintainer dependency and are comfortable pinning versions and watching releases.

Look elsewhere when:

• You need versioned docs, multi-locale routing, search, or auth-scoped content — a dedicated docs platform or a custom build is a better fit.
• AI documentation is a core product differentiator requiring roadmap influence; a small package's release cadence won't track your priorities.
• Your content lives in a CMS, Notion, or a separate docs site rather than in-repo markdown.
• You require enterprise support, security review guarantees, or long-term maintenance commitments.

Note: v1.5.0 is an additive, non-breaking change with a documentation update. No migration, deprecation, or config change is implied — existing adopters can upgrade without product-side work.

How to Pitch It (Stakeholders)

For executives: We're evaluating a small Laravel package that publishes our markdown documentation in a form AI assistants can read reliably. The latest release adds named folder grouping via index.md front matter, which improves how AI tools navigate and cite our docs — a quality improvement we get for free from the maintainer rather than funding ourselves. Cost is low; the main risk is dependence on a single maintainer, which we mitigate by pinning versions and keeping content in standard markdown so it stays portable.

For engineering: Drop-in, convention-based, no infrastructure. Docs stay as markdown in the repo; structure is expressed through front matter, so content owners can reorganize sections without code changes. v1.5.0 is additive and non-breaking — safe to upgrade. Before committing, validate that the package's output format and grouping match our retrieval needs, and confirm we're comfortable with the maintenance profile of a single-author dependency. If we later need versioned docs, auth-scoped content, or search, expect to extend or migrate — so keep content in plain markdown to preserve that exit.