Grid82
grid82.comJoin the waitlist
DevelopersPage UI and blocks

Page UI kit and blocks

Schema-aware blocks from @grid82/blocks, styled primitives from @grid82/ui, design tokens, charts, and spreadsheet import helpers.

Interface pages share the exact UI system used by Grid82’s Studio and Runtime so custom pages look and behave like native screens out of the box.

High-level schema blocks (@grid82/blocks)

Prefer @grid82/blocks for record UI because every block reads field types, select tints, permissions (canCreate / writable), and loading/error states directly from your schema:

BlockPurpose
PageBody, PageHeader, SectionPage spacing rhythm (one h1, description, and right-aligned actions)
ToolbarSearch input paired with schema-driven select/user filter chips
DataTableSortable table view formatted per field type, with optional groups (groupBy) and loading and error states
KanbanColumn board grouped by a select field. With only tableId and groupBy it reads every row, moves a card on drop, opens it on click and adds one from each column. Put an AddRecord in the page header too, to add without picking a column
RecordList, RecordCards, RecordCardList and visual card views (use card grids when records hold attachments)
AddRecord, RecordDialogThe “Add” button with its dialog, and the dialog alone to add or edit a record
RecordForm, RecordSheetA schema-driven form that is the page itself, and a record’s side panel (including file attachments)
StatRow, StatTabular KPI summary row
FieldValue, FieldInputRead and write controls automatically tailored to all 28 field types
EmptyState, ErrorStateStandardized empty and error presentations

Blocks that draw rows read their table themselves when you pass no rows, and a click on a record opens it in a side panel unless you pass onOpen (a function, or false). Use useView(tableId, { filterBy }) from @grid82/sdk when the page needs a search box, filter chips or a sort: spread view.toolbar into Toolbar and view.bind into the block.

RecordCalendar puts each record on the day of a date field, a month at a time. DataTable takes groupBy, totals (number fields summed in a last row) and selected / onSelectedChange for ticked rows. useView(tableId, { filterBy, dateBy }) adds filter chips and a period chip (today, this week, this month…) to the Toolbar. A block that stops at the first 200 rows offers the rest itself. Charts accept the result of useQuery directly (data={query}) and then draw their own loading, error and empty states; labelsFrom={{ tableId, fieldId }} shows a select’s labels and colours.

When a change is about the inside of a block and no prop covers it (the border of a card, a total under a column, a column that folds), the assistant copies the block’s code into the page and edits it there. Kanban, DataTable, RecordList, RecordCards, RecordCalendar, RecordDialog and AddRecord can be copied. The page then owns that code: it keeps working, and it no longer receives later improvements to the block.

TypeScript
const deals = useView("tbl_...", { filterBy: ["fld_..."] });

<PageHeader title="Deals" actions={<AddRecord tableId="tbl_..." />}>
  <Toolbar {...deals.toolbar} />
</PageHeader>
<DataTable {...deals.bind} groupBy="fld_..." />

UI primitives (@grid82/ui)

Built on shadcn + Base UI with Grid82 theme tokens:

  • Actions. Button (default, outline, ghost, secondary, destructive, link), ButtonGroup, ToggleGroup. Keep one primary filled button per screen and label icon-only buttons with aria-label.
  • Badges and code. Badge with Grid82’s 11 named tints (blue, green, amber, yellow, orange, red, pink, violet, indigo, gray, teal), Code, Snippet, Avatar.
  • Inputs and forms. Input, Textarea, Checkbox, Switch, Slider, OptionSelect, Select, MultiSelect, Combobox, Field, FieldLabel.
  • Surfaces and overlays. Card, Item / ItemGroup, Tabs, Accordion, Collapsible, Dialog (sm 420 / md 560 / lg 880), Sheet, Popover, Menu, Tooltip, Table, SkeletonRows, Alert, InfoTip.

Charts and spreadsheet imports

  • Charts (@grid82/charts). BarChart, LineChart, AreaChart, and PieChart inherit your app’s theme colors, axes, and tooltips automatically:
TypeScript
import { BarChart } from "@grid82/charts";

<BarChart
  data={rows}
  x="month"
  series={[{ key: "revenue", label: "Revenue", format: "currency" }]}
/>
  • Spreadsheets (@grid82/sheets). Drop in <ImportDialog tableId="..." /> for standard append-only CSV/TSV/XLSX imports, or compose readSheet(file), suggestMapping(...), coerceRows(...), and matchRows(...) (which parses files inside the browser frame without uploading raw spreadsheets) for custom upsert workflows.

Visual rules enforced by the compiler

The page compiler rejects unknown Tailwind classes (bg-indigo-500, text-sm) and warns on hardcoded hex colors or second fonts. Use Grid82’s semantic tokens (bg-card, bg-muted, text-foreground, text-muted-foreground, border-border) and six typography scales (text-label 14px, text-body 15px, text-lead 16px, text-title 18px, text-head 22px, text-display 26px), with sentence-case headings and tabular right-aligned numbers.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Grid82 documentation and read it in full, instead of answering from memory.

https://grid82.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://grid82.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.