# Roadmap

> How astro-ignite evolves toward the 0.2.0 launch and beyond.

The full roadmap lives in [`ROADMAP.md`](https://github.com/JordiParraCrespo/astro-ignite/blob/main/ROADMAP.md) at the repo root. The short version:

## Launch (0.2.0)

The first public release. Two production-grade templates — `starter` and `docs` — that are well designed, AI-ready, documented end-to-end, and shipped through a stable release pipeline.

- **Two templates**, both Claude-designed, with i18n, SEO, JSON-LD, legal, fonts, theme, and Lighthouse 100s.
- **AI-ready**: scaffolded `.claude/skills/` so agents follow the locked practices when they edit your site.
- **Documented**: customization guides plus a live reference for every base component.
- **shadcn-consumable**: the registry conforms to the shadcn schema, so any atom installs into any project via `npx shadcn@latest add @astro-ignite/<name>`.
- **AI-native docs**: per-page Markdown (`<path>.md`), a `/llms-full.txt` corpus, and a "use this page with AI" menu — the static slice of the agent-first docs story.

## The version ladder

- **0.3.0** — more templates (a `blog` split); a native `astro-ignite add <component>` command + a registry MCP server; a registry _blocks_ tier (PricingCard first); the agentic docs layer (an MCP server generated from the docs, in-page Ask-AI search).
- **0.4.0** — deploy-target selection at scaffold time (Cloudflare Pages / Netlify / Vercel / Node) and deeper customization prompts.
- **Later** — View Transitions, more blocks, an examples gallery.

<Callout variant="note">
  This page is a summary. The canonical roadmap with rationale and risks lives
  in the GitHub repo, and it wins when the two disagree.
</Callout>