---
title: "Building Interface pages"
description: "Write, preview, type-check, and publish custom React Interface pages in the Studio workbench using the Grid82 Page SDK and UI blocks."
canonical: "https://grid82.com/docs/build/building-pages"
updated: "2026-11-20"
---

# Building Interface pages

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)](/docs/images/app/studio-interface-workbench.webp)

_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:

```tsx
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](/docs/developers/sdk/page-sdk) and [Page UI and blocks guide](/docs/developers/sdk/page-ui-and-blocks) for every hook, component, and design constraint.
