Reference

Project File Structure

Detailed map of important Vista folders and how runtime, routes, and docs content connect to each other.

Updated: 2026-09-18

Generated app files (after CLI)

txt

txt
auth.ts                              -> VistaAuth config (vista g auth)
middleware.ts                        -> fail-closed /account guard
app/signin/page.tsx                  -> credentials POST + OAuth
app/account/page.tsx                 -> gated session page
app/agents/<name>/agent.ts           -> vista g agent
.env.example                         -> AUTH_SECRET and provider keys

Runtime-Facing Files (this docs site)

txt

txt
app/root.tsx                -> global shell
app/index.tsx               -> home route
app/docs/layout.tsx         -> docs shell (sidebar + TOC)
app/docs/[...slug]/page.tsx -> docs article resolver
app/api/*                   -> REST + typed API entry

Docs Content Files

txt

txt
content/docs/categories.ts                 -> category registry
content/docs/**/<doc>.md                   -> doc section data
content/docs/index.ts                      -> allDocs collector
lib/docs.ts                                -> slug resolver + navigation helpers

Typed API Files

txt

txt
app/api/typed.ts                          -> typed router entry
app/api/routers/index.ts                   -> compose procedures
app/api/procedures/*.ts                    -> query/mutation handlers

What to Keep Stable

  • Do not rename /docs/<category>/<slug> contract once public links exist.
  • Keep docs category IDs stable; they are used in navigation generation.
  • Prefer app-local utilities before extracting framework-level helpers.

See Also