# Slate Page Layouts

> The five page zones and the list, detail, edit, and chat layouts of the Everruns UI, as full-page examples to start a redesign from.

Source: <https://everruns.com/docs/design-system/layouts/>

## The five zones

Every top-level entity screen composes the primitives in [`apps/ui/src/components/layout/page-layout.tsx`](https://github.com/everruns/everruns/blob/main/apps/ui/src/components/layout/page-layout.tsx). Only the zone contents change from page to page; no page invents a parallel shell.

1. **Breadcrumb**: `Group / Section / Name / Mode`. The group comes from the sidebar.
2. **Masthead**: a 40px icon tile with the gold 10% wash, the 28px title, a muted one-line description, an optional meta line, and the action cluster on the right.
3. **Control strip**: search on the left; status tabs and the view toggle on the right.
4. **Body**: the records, or the workspace of a detail page.
5. **Footer**: optional. It explains partial results or pagination, or links back.

The page has 24px padding and 24px between zones, on the dot grid.

## List page

Agents list: masthead with Import and the gold create action, control strip, card grid, examples row.

* The records get the full width. No facet or summary rail on list pages, and no count badge in the masthead: counts live in the status tabs.
* Genuine filters (category, provider) are toolbar controls in the control strip.
* Example discovery is one row of compact previews with an import or setup action.
* Dense registries such as Models switch the grid for [rows](https://everruns.com/docs/design-system/components/#rows).
* Detail, editing, and operational screens with richer filtering may add a contextual rail.

## Detail page

One layout reads and edits. The substance of the record is a wide primary pane; configuration is a 340px config column. The [agent page](https://github.com/everruns/everruns/blob/main/knowledge/ui/agent-page.md) is the reference implementation.

Agent detail: one tab row attached to the workspace, prompt in the primary pane, configuration in the column.

* **One tab row**, attached to the workspace with no gap. Its selection is part of the address (`?tab=`). Non-primary tabs drop the config column and use the full width.
* **Set-once settings are More rows**, each showing its current value (“None”, “Inherited”, “Not run”) and opening a side sheet. They never become extra tabs, and never become cards above the tab row.
* **Settings that do not apply are hidden, not greyed out.** When something outside Everruns owns part of the record (an external agent’s endpoint owns its prompt, model and tools), that part leaves the page and the primary pane shows what replaced it.
* **Controls are live in view mode.** Changing one enters edit mode with that change pending. Nothing saves until Save changes.
* The `#` after the name copies the record’s id. History, Manager notes, Archive, and Delete live in the `⋯` menu.
* Older detail screens that have not moved to the workspace still use titled block cards in a main column with a side rail. New detail screens use the workspace.

## File browser

Anything that is a set of files, such as a session’s workspace or a Knowledge collection, opens on the same tree and viewer from [`apps/ui/src/components/files/`](https://github.com/everruns/everruns/blob/main/apps/ui/src/components/files/). The [Knowledge pages](https://github.com/everruns/everruns/blob/main/knowledge/ui/knowledge-pages.md) are the reference implementation.

Knowledge collection, Files tab: folder tree beside the viewer, per-file controls in the viewer footer.

* **One browser, many filesystems.** `FileBrowser` and `FileViewer` take a `FileSource` (list a folder, read a file, a download URL, optional writes). A source without writes renders read-only: no New, Edit, or Delete, and a lock on each file.
* **The tree loads one folder at a time.** Folders expand on demand; never page a whole recursive listing into the tree.
* **The selection is part of the address** (`?file=`), so search results and shared links open straight to a file.
* **Per-file controls sit in the viewer footer**, not in the tree. Extraction or sync state is a status dot in the viewer header; the tree shows a dot only when a file needs attention.
* **Section tabs are paths** on pages whose tabs are whole sections (Knowledge, Sandboxes): `/knowledge/{id}/sources`, with the shell as the tabs’ layout.

## Edit mode

Edit is a mode of the same page (`?mode=edit`), not a separate layout, so the reader keeps their place.

The same page in edit mode: Edit crumb, Editing badge, the consequence line, Save changes and Discard.

1. The breadcrumb gains a final Edit crumb, and the status badge becomes the gold Editing badge.
2. The masthead states the consequence of saving.
3. The actions become navy Save changes, then Discard.
4. The prompt becomes a mono textarea in the same place, with its checks directly under it.
5. Config controls become editable: capabilities gain a remove control and an Add button.

One Save sends the whole draft. Leaving with unsaved edits asks first.

## Create page

A page that creates a record of one of several kinds asks the question a person can answer first: who will use it. The New channel page is the reference.

The kind chooser: two groups named by audience, one row per kind with a plain sentence and any prerequisite.

1. Nothing is preselected. Each kind is one row: icon, name, one sentence a newcomer understands, and what must exist first. Protocol names stay in the row, not the headings.
2. Choosing a kind keeps the same page: the masthead becomes “New Public Chat”, the chosen kind sits on top of the form with a Change type button, and the Create action appears.
3. The form is split into named sections, each with a short hint in a left column. Advanced settings with good defaults fold behind a one-line summary of their current values.
4. The rail says what happens next, so the reader knows the record starts as a draft.

## Chat

The chat is one centered column, 820px at most, shared by the transcript and the composer. Product decisions: [chat experience](https://github.com/everruns/everruns/blob/main/knowledge/ui/chat-experience.md).

A chat thread: header, user turn as a gold wash, collapsed work log, agent reply as prose, composer card.

* **Agent replies are prose.** No card, no edge rule, no avatar tile. An agent mark appears only in multi-agent sessions, where the speaker must be named.
* **User turns are a tinted block**: right aligned, at most `min(78%, 42rem)`, a gold 12% wash, no edge rule.
* **Tool activity lives in the work log**, a fold above the reply that starts and stays collapsed while the turn runs. The header carries the live signal (“Working for 12s”, with the shimmer) and keeps the error count visible while folded. Opened, it lists one row per step behind a 1px rule.
* Cards that need the person (approvals, questions, connection setup) render outside the fold so they cannot be hidden.
* Prose links entities inline with a small glyph and an underline, and names files with a mono token. No pills in prose.
* The composer is a bordered card: the text area, then attach, the model and effort chip, and send or stop in one slot on the right.

## Reuse the page composition

Standard product routes use `PageContainer`, `PageBreadcrumb`, `PageMasthead`, `PageControlStrip`, `PageMain` and `PageFooter`. List pages add `PageColumns` and `PageRail` when facets are useful. Creation and editing pages reuse the masthead and section cards; do not wrap an already card-based form in an extra card. Keep the same outer composition while data loads or a query fails.

Reports and dense operational routes use the same primitives with full-width content as needed. Chat and session workspaces retain their own reading and split-pane compositions. The older `PageShell`, `PageHeader` and `PageBody` API is retired.

Settings uses its existing destination model in both presentations: a sidebar on large screens and one destination selector on narrow screens. The form should be reachable in the first viewport rather than following a full screen of navigation.

A form field consists of its label, control, optional hint and validation message. Keep feature-specific draft state and validation in its owner; share the presentation. Changing a control on an explicit-save page must not silently adopt autosave behavior. Pending, saved and failed states must remain visible wherever autosave is used.