Phoenix Docs

Phoenix answers drift with each release and span several Hex packages, so ground each answer in the live docs at https://phoenix.hexdocs.pm/, not memory, and link the exact page behind every claim.

Route Django, Flask or FastAPI patterns to django-docs, flask-docs or fastapi-docs. Plain Elixir language questions belong to the Elixir guides, and Ecto-only or third-party package questions to their own docs, unless the question turns on Phoenix behavior.

Workflow

1. Locate the question in references/topic-map.md, a selective index of docs entry points. Done when each part of the question maps to a section of the map, or you have noted that none fits.
2. Search phoenix.hexdocs.pm with the user's exact terms plus Phoenix vocabulary such as pipe_through, assign, LiveView, context, changeset, or mix phx.gen.auth, starting from the map's pages and the Routing rules below. Done when you hold the one page that most directly answers each part.
3. Read each page down to the relevant section. Done when you have read the passage behind every claim you will make. When a page has moved, been renamed, or stops short, say so and link the nearest authoritative pages.
4. Answer with the direct answer first, each docs link beside the claim it supports, and code examples only when the user asks or the page needs them. Mark any conclusion that joins several pages as Inference:. Done when every claim cites a specific page, not the docs home.

Routing