Grid82
grid82.comJoin the waitlist
BuildBuilding pages

Building Interface pages

Write, preview, type-check, and publish custom React Interface pages in the Studio workbench using the Grid82 Page SDK and UI blocks.

In the Studio, open Interface in an app’s sidebar to build, preview, and publish pages using the visual workbench or the built-in Studio assistant.

Studio Interface workbench showing Pipeline Overview preview, Manage pages button (1), and New page button (2)

The Studio Interface workbench showing the live sandboxed preview, Manage pages (1), and New page (2)
  1. Manage pages: Reorder pages, inspect version history, adjust visibleTo role visibility, switch between Locked and Template, or roll back to an earlier build.
  2. New page: Create a new React component file in the app’s interface tree.

Structure of a page file

Every page is one .tsx file exporting a default Page component, limited to six approved imports so pages render quickly, stay theme-consistent, and compile reliably:

TypeScript
import * as React from "react";
import { useTable, useView, useQuery, actions, fmt } from "@grid82/sdk";
import { Button, Card, CardHeader, CardTitle, CardContent, Badge } from "@grid82/ui";
import { PageBody, PageHeader, Toolbar, DataTable, Kanban, AddRecord, StatRow, Stat } from "@grid82/blocks";
import { Plus } from "lucide-react";

When a page needs charts or spreadsheet parsing, import them only when needed from @grid82/charts (BarChart, LineChart, AreaChart, PieChart) or @grid82/sheets (ImportDialog, readSheet, coerceRows).

Authoring workflow

  1. Key on field IDs, never display labels: Read your schema (apps.get or the Studio inspector) to get exact tbl_... and fld_... IDs. Display labels can change without breaking pages keyed on IDs.
  2. Handle loading, error, and empty states: A block given only tableId reads its rows and draws all three itself. When the page owns the read, pass rows, isLoading and error into the block (useView returns them as bind), or handle isLoading -> error -> empty data in that order.
  3. Compile and check: Every save type-checks your code against the Page SDK. Any disallowed import, missing hook field, or unknown Tailwind utility class fails before publishing.
  4. Publish: Preview the built version in the right pane of the workbench, then click Publish to push that immutable version to Runtime users.

Read the complete Page SDK reference and Page UI and blocks guide for every hook, component, and design constraint.

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.