Live demo

Server Renders the real page

Every byte is server-rendered HTML — the owner of rendering truth, first paint to last patch.

Runtime Tiny, plain-DOM, enhances

Three small runtimes use native addEventListener / fetch / EventSource — no React, Alpine or virtual DOM.

JS off Still the real page

Disable JavaScript and the server-rendered HTML is still there. Script is enhancement, never a mandatory second renderer.

Enhance never require Tiny plain-DOM runtimes No VDOM, no client store

Framework-Free JS

The seventh pillar is a refusal. Because the server owns rendering truth from the first byte, JavaScript is never the mandatory second renderer. The interactive, live and collaborative behaviour across this handbook runs on a handful of small, plain-DOM runtimes — not a client framework.

Enhancement, not a second renderer

Platform-UI ships three tiny runtimes — event capture, live regions, and collaboration — built on native DOM APIs: querySelector, addEventListener, fetch, EventSource. No jQuery, Vue, React or virtual DOM. They enhance server-rendered HTML; with JavaScript disabled, the HTML is still the real page. Assets, scripts and SEO live inside the same rendering system rather than becoming a parallel deployment concern.

Why it guards the other six

A mandatory client framework is precisely how "SSR" quietly becomes a client app that owns half your stack. Keeping JavaScript as optional enhancement means the server stays the single owner of rendering truth — which is the whole thesis. This pillar is the guarantee that the other six can't silently drift into a second architecture.

1<!-- Server-rendered, real HTML. JS only enhances it. -->2<button ui="button" data-ui-part="save">Save</button>

<!-- Server-rendered, real HTML. JS only enhances it. -->
<button ui="button" data-ui-part="save">Save</button>

1// The whole client side is a tiny capture-only runtime — native DOM, no framework:2document.addEventListener('change', (e) => {3    const part = e.target.closest('[data-ui-part]');4    if (part) eventRuntime.dispatch(part);   // POST /__ui/dispatch5});

// The whole client side is a tiny capture-only runtime — native DOM, no framework:
document.addEventListener('change', (e) => {
    const part = e.target.closest('[data-ui-part]');
    if (part) eventRuntime.dispatch(part);   // POST /__ui/dispatch
});

How it works

Platform-UI ships three tiny runtimes — event capture, live regions, collaboration — that use native DOM APIs (querySelector, addEventListener, fetch, EventSource) with no jQuery, Vue, React or virtual DOM. They enhance server-rendered HTML; with JS off, the HTML is still the real page. Assets, scripts and SEO live inside the same rendering system, not a parallel deployment.

Why it matters

A mandatory client framework is how "SSR" quietly becomes a client app that owns half your stack. Keeping JS as optional enhancement means the server stays the single owner of rendering truth — the whole thesis. This pillar is what guarantees the other six can't silently drift into a second architecture.