HTML pages¶

Starting with SeaTable 6.2, a Universal App can contain a new page type: the HTML page. You upload a packaged HTML/JavaScript/CSS bundle, and SeaTable renders it as a full page inside the app.

A static bundle on its own can only display fixed content. To turn an HTML page into a real application — a custom form, a dashboard, a calculator — it needs to read from and write to the base. That data exchange runs through the seatable-html-page-sdk.

This section is written for developers. It covers how to set up a project, how to develop and package a page, and the full SDK reference.

Architecture¶

An HTML page is rendered in a sandboxed context inside the Universal App. It never talks to the base directly. Instead, the SDK provides a messaging bridge to the app, which performs the actual data operations.

flowchart LR
    A[HTML page] -->|seatable-html-page-sdk| B[Universal App]
    B -->|API| C[(Base)]
    C --> B
    B --> A

The SDK offers:

• Data APIs — list, add, update and delete rows; upload files and images.
• Event propagation — bidirectional events (mouse, keyboard, drag-and-drop) between the page and the app.

Prerequisites¶

• SeaTable 6.2 or later.
• A Universal App with an HTML page added to it.

The developer setup additionally needs Node.js and npm, and an API token generated in the base for local development. The low-code approach needs neither.

Two ways to build¶

The same kind of page can be built two ways. Pick the one that matches how you like to work — both produce the same uploadable ZIP and use the same SDK.

Where to start¶

• Low-code quickstart — build a page with a visual editor and copy-paste snippets, no toolchain.
• Developer setup — set up the project, develop locally, build and upload a page. We follow the official simple form template end to end.
• SDK Reference — installation, initialization, and the full API for rows, files and images.