Dygo Pages And Studio

---
name: dygo-pages-and-studio
description: Define dygo App Pages and metadata-driven Studio experiences for Business Apps. Use when an App needs a Page, navigation entry, renderer choice, or Studio presentation beyond default Entity routes.
---

# dygo Pages And Studio

Use metadata to select `entity-index` or a sibling Vue file. Do not place UI implementation inside Page metadata.

## Start

Read `docs/pages.md`, `docs/studio.md`, and the Page-related parts of `docs/app-model.md` and `docs/dir.md`. Confirm which Page features exist now.

## Rules

- Keep the Page bundle app-owned under the documented `pages/` path.
- Use `dygo generate page <app>/<page>` to create YAML, Vue, and access files.
- Use `renderer: vue` with a sibling `<page>.vue` file under `apps/<app>/pages/<page>/`. Studio globs every App's Page Vue files into the host. Studio Home lives at `apps/studio/pages/home/`.
- Use `renderer: entity-index` when a Page should show the entity list UI without a sibling Vue file.
- Let Studio own rendering, layout, permissions, loading, errors, and shared interaction patterns.
- Prefer normal Entity and Record surfaces when they solve the task.
- Studio lists App Pages in the sidebar except Home. Home stays on the Studio home control.
- Add a Page only when it represents a useful business Space or cross-Entity entry point.
- Keep navigation labels and actions in dygo vocabulary.
- Do not encode arbitrary frontend code, SQL, or unvalidated behavior in metadata.
- Put Vue UI in `<page>.vue` beside the YAML. Do not implement a separate App frontend bundle contract.

## Check

Validate Page metadata through the current project validation path. Confirm that boot data, navigation, route resolution, permissions, and renderer registration agree.