Skip to content

Views

A view file inside an App replaces the one derived screen at its path with Components.

A view.mdx file inside an App replaces the one derived screen at its path. Every other screen keeps deriving from the Nouns.

  • apps/portal/
  • leases/[lease]/view.mdxreplaces /app/leases/{lease}

Reference

MDX with Components, under the same rules as a Page: literal props, parsed, never run.

KeyTypeHolds
titlestringThe screen title
personaslistThe Personas who see this view; others keep the derived screen

Examples

Minimal

apps/portal/leases/[lease]/view.mdx
<ThingDetail />

Leaseline

apps/portal/leases/[lease]/view.mdx
---
personas: [manager]
---
<ThingDetail fields={["unit", "resident", "endsOn", "rent", "status"]} />
<Timeline />
<VerbSheet verbs={["Lease.renew", "Lease.notify"]} />

What it builds

The SoftwareBuilder compiles it into the App's screen at that path.

  • the screen as HTML for people, JSON for native clients and Markdown for agents
  • no new route; authorization is the App's

Good to know

  • Delete the file to return to the derived screen.