SEMITEXA · INTERFACE LAYER

One server-owned rendering story, from first paint to live collaboration.

Page, slots, deferred regions, live refresh and interactive components never leave the server. Watch the same architecture turn static HTML into token-driven, reactive UI — no second frontend.

Explore Layers View Source Start Here

Token-driven skins Server-owned rendering Framework-free JS

Live UI Surface

interactive UI demos wired into this site

5 sections

3 nav layers

3 high-signal demos

What you are looking at

$ read the rendering thesis
$ watch one skin repaint everything
$ edit a shared form, live, in two tabs

Start here

The one idea, then the proof

Read the rendering thesis first, then watch the same architecture turn static HTML into token-driven, live, interactive UI.

Install Platform-UI Add the platform-ui package to get the primitive registry, grammar compiler, skin tokens and tiny runtimes. Server-side, no build step, no client framework. One continuous rendering architecture Not SSR for the first paint and a second frontend for the rest: page, slots, deferred regions, live refresh and interactive components share one server story. Token-driven UI: skins as data Visual identity is data, not code. Every primitive reads the active skin's --ui-* tokens, so the same templates render in any palette with zero component CSS. Live regions: deferred and reactive slots A page region is a resource with its own pipeline. Mark it deferred and it streams in as server HTML; add an interval and the server keeps re-rendering it.

Core concepts

How the interface layer is built

The two foundations the rest of the handbook rests on: one server-owned rendering story, and a token-driven component substrate.

Philosophy

Concepts

The thesis the rest of this handbook proves: page, slots, deferred regions, live refresh and interactive components all stay inside one server-owned rendering story — no second frontend, no presentation-boundary leaks. Start here; everything else is an application of these principles.

8 features

Design substrate

Foundations

What every component is built on: the --ui-* token contract that makes skins a data concern, and the sx-* / ui-* attribute grammar that composes layouts. Change a token or a skin and the whole UI repaints — no per-component CSS.

6 features

Full catalog

Every capability on show

The complete index — onboarding, rendering concepts, design foundations, the component library, and the composition patterns that make them live.

Onboarding

Get Started

The shortest path from nothing to a working, themed, interactive Semitexa UI: install the kit, render your first component, theme the site by swapping tokens, and ship an interactive component — each step a few lines, no client framework.

4 features

Philosophy

Concepts

8 features

Design substrate

Foundations

6 features

Building blocks

Components

The actual building blocks, by category: primitives (button, input, badge…), form controls with signed server-side validation, and contract-driven data display. Everything reads the active skin's tokens, so the moss palette here applies with zero component-level CSS.

6 features

Composition recipes

Patterns

How the building blocks compose into live behaviour: the signed interactive-HTML event runtime, deferred and reactive regions over one SSE stream, and real-time collaboration — each a configuration choice on the same architecture, never a second system.

4 features

High-signal demos

These walkthroughs show Semitexa UI at its most convincing: live deferred regions, contract-driven grids pushed over SSE, and real-time co-editing.

Live regions: deferred and reactive slots Live grid: push over SSE Shared live form