> ## Documentation Index
> Fetch the complete documentation index at: https://archie.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Every route your blueprint describes becomes a generated screen. Browse them, check how your theme lands on real content, and edit them directly.

Every route your [blueprint](/docs/features/blueprint/overview) describes gets a generated screen. Screens is where you browse all of them, check how your [theme and design values](/docs/features/design/theme) land on real content, and make direct edits before you build.

## What's in this section

<CardGroup cols={3}>
  <Card title="Views" icon="table-cells-large" href="/docs/features/design/screens/views">
    Screen, Grid, Pages, and Sitemap — four ways to look at your generated screens.
  </Card>

  <Card title="Navigation" icon="compass" href="/docs/features/design/screens/navigation">
    Switch screens, check devices and dark mode, track generation progress, filter by user type.
  </Card>

  <Card title="Editing a screen" icon="pen-to-square" href="/docs/features/design/screens/editing">
    Click into any element to change it directly, or describe the change in chat.
  </Card>
</CardGroup>

## Where screens come from

Screens are generated automatically from your blueprint — one per route. Beyond the modules you defined yourself, Archie also generates screens for the **core services** it builds in automatically, like User Management, Payment Processing, and Notifications. See [Views → Sitemap](/docs/features/design/screens/views#sitemap) to see the full structure at once.

## FAQ

<AccordionGroup>
  <Accordion title="A screen shows 'Needs regeneration' — what does that mean?">
    The screen's content is out of sync with a change elsewhere — usually a blueprint edit made after that screen was generated. Use **Regenerate Prototype** to bring it back in sync.
  </Accordion>

  <Accordion title="Do changes to a screen affect the real app, or just the prototype?">
    Screens work on the generated prototype. When you build, the state of your screens becomes the starting point for the actual [frontend](/docs/features/frontend/overview) — you can keep adjusting afterward with the visual editor, chat, or code.
  </Accordion>
</AccordionGroup>