{"title":"Guides","description":"Amber V2 guides, reviewed replacements, and stable framework references","section":"","version":"v2","path":"guides","canonical_url":"https://amberframework.org/docs/v2/guides","markdown_url":"https://amberframework.org/docs/v2/guides.md","inherited":false,"content_markdown":"# Guides\n\nV2 keeps framework concepts that still apply—controllers, requests, responses,\nsessions, routing, cookies, testing, and other stable APIs. An unchanged page\nhas no badge. **New** and **Updated** badges identify material written or\nrevised for V2.\n\nPages built around removed components are excluded rather than inherited.\nGranite and Jennifer point to Grant replacements; legacy bundled-CLI commands\nremain retired; assets and the standalone Amber CLI use their V2 guides.\n\n## How to apply an example\n\nEvery code-bearing V2 guide now provides one of two placement contracts:\n\n- a walkthrough labels each block with the exact **File**, **Files**, or\n  **Run from** location and says whether to create, edit, replace, or inspect it;\n- an API reference begins with **Where the examples go**, mapping declarations,\n  usage fragments, configuration, views, and generated output to their normal\n  application directories.\n\nPaths are relative to the application root—the directory containing\n`shard.yml`—unless a guide says otherwise. Treat `public/` as browser-served\napplication files only when the guide labels them as source; never hand-edit a\ndirectory labeled as generated output.\n\n## Supported beta core\n\n- [Build a Pet Tracker](pet-tracker/) — the canonical first app, from routes to HTML, JSON, CSS, and browser-native JavaScript\n- [Web template](web-template/) — exact output of Amber CLI 2.0.6\n- [Asset Pipeline](assets/) — CSS, JavaScript, images, fonts, SRI, and immutable caching\n- [Grant](models/grant/) — the default relational model layer\n- [Migrations](models/grant/migrations/) — authored Micrate SQL and safe release workflow\n- [Schema API](schema-api/) — typed request parsing and validation\n- [WebSockets and live pages](websockets/) — server-rendered documents with channel-driven ES module updates\n- [Background jobs](background-jobs/) — queues, retries, delayed work, work stealing, and capacity boundaries\n- [Adapters](adapters/) — framework adapter concepts and extension points\n\n## Preview ecosystem material\n\n- [Native application template](native-preview/) — macOS, iOS, and Android preview\n- [Gemma](uploads/) — separate attachment project\n\nPreview pages describe work that can be evaluated, but they are not part of the\nclean web-template compile guarantee. The Asset Pipeline is part of that\nguarantee; add native and attachment projects deliberately.\n\n## Use the docs with an assistant\n\n[AI assistants](ai-assistants/) explains how to give ChatGPT, Claude, or Gemini\nthe current V2 source set. It also provides a single Markdown knowledge bundle\nand a tested Custom GPT instruction contract. The assistant should cite these\npages, preserve exact file locations, and name beta boundaries rather than\nsilently filling gaps from older Amber versions.\n\n## Maintaining a V1 application\n\nAmber 1.4.1 documentation remains available from the version selector. Choose\nthat version when maintaining an existing V1 application. V2 uses badges only\nwhere a page is new or materially updated and uses replacement links where the\npath changed."}