> ## Documentation Index
> Fetch the complete documentation index at: https://supastack.dev/llms.txt
> Use this file to discover all available pages before exploring further.
> For the full documentation corpus in one file, fetch: https://supastack.dev/llms-full.txt

# Product documentation

The dedicated docs app that ships with the kit.

## Before you begin

Open your downloaded supastack project in Visual Studio Code using File → Open Folder, then choose Terminal → New Terminal. The repository root is the folder containing package.json, apps and packages. Run the command below there and leave its terminal open. If a command is not recognized, finish the tool installation guide before continuing.

Read the platform tutorial first. A server is the app process that answers browser or phone requests. Web reads apps/web/.env.local, Expo reads apps/mobile/.env.local, and database migration commands read root .env. The no-database /dashboard demonstration is separate from real /auth accounts, which need migrated Postgres. A phone or desktop-only checkout needs a separately running Web backend.

[Install the tools and get the code](https://supastack.dev/docs/web/before-you-start.md)

[Learn commands, files and configuration](https://supastack.dev/docs/web/terminal-basics.md)

[Complete the Web first-run tutorial](https://supastack.dev/docs/web/ship-in-5-minutes.md)

```
corepack pnpm --filter @supastack/web dev
```


## Setup and configuration

apps/docs is the buyer-facing documentation surface for the product you build — separate from this kit documentation. It renders your product's own guides with navigation, per-page anchors, and search, and runs as its own workspace app on port 3001 in development.

Keep its content typed and versioned in the repository alongside the features it describes; a doc that drifts from the code is worse than a missing page.

```
apps/docs/        Product documentation app
  content/        Guide sources and nav order
  app/            Routes, layout, search
```


## Implementation workflow

Model your product's docs on the kit's own structure: a getting-started path, one page per feature area, and reference pages for configuration and APIs. Reuse the kit's guide format so tooling (search index, copy-as-Markdown) keeps working.

Link tasks to pages: when you ship a feature, update the matching guide in the same change.


## Verification and troubleshooting

Build the docs workspace, click through every nav entry, run a search for each new term you introduce, and check anchor links after renames. Treat broken doc links like broken routes.


## Next

[Feature flags and announcements](https://supastack.dev/docs/web/feature-flags.md)