Section Overview
UI Rendering & SSR
15
live features
One rendering story from handler to HTML: page data, page regions, and live updates stay in the same server-driven model instead of splitting into frontend and backend template logic.
Support Semitexa
Built for developers who prefer control over magic.
Your support helps keep it fast, open, and evolving.
Core Idea
One rendering story, not two
Semitexa treats server rendering, page regions, and live updates as one coherent system. The goal is to stop splitting template logic into a backend version for first paint and a different frontend version for everything interactive.
Handlers shape explicit response data once, so templates stop reverse-engineering random arrays and view state.
Slots and deferred regions reuse the same rendering model as the page shell, so “dynamic UI” does not become a separate frontend architecture.
When the data changes, the server re-renders the truth as HTML. The interface stays simple because the rendering philosophy stays simple.
Conceptual Path
Read the section as a progression: start with the rendering model, then move through delivery, and only then into the live surfaces that reuse the same server-owned story.
SSR Foundation
8UI Rendering & SSR
SSR Philosophy
Semitexa SSR is one continuous rendering architecture: page, slots, deferred regions, live refresh, and interactive components stay inside one server-owned story.
UI Rendering & SSR
Resource DTOs
A Resource DTO is the one typed source of presentation data: handlers shape it once, templates consume it everywhere, and no view has to dissect random arrays.
UI Rendering & SSR
Slot Resources
Each page region is its own resource pipeline with the same template system as the main page — no scattered partial glue, no mystery wiring.
UI Rendering & SSR
Components
Reusable, attribute-registered UI components — discovered automatically from the classmap.
UI Rendering & SSR
SEO
Set title, description, and Open Graph tags from your handler — no template hacks needed.
UI Rendering & SSR
Asset Pipeline
Declare assets with glob patterns in assets.json — served, versioned, and injected automatically.
UI Rendering & SSR
Component Script Assets
A Semitexa SSR component can own its optional enhancement asset, so behavior travels with the component instead of leaking into page-level glue.
UI Rendering & SSR
Script Injection
Deferred blocks carry their own JS — injected once when the block arrives, never duplicated.
Deferred Delivery
2Reactive UI
5UI Rendering & SSR
Live Widgets
The server re-renders a live slot on a cadence and pushes it down the page's own SSE connection — SSR-first, no SPA runtime, and no polling anywhere.
UI Rendering & SSR
Reactive Report
Background work updates an SSR-first slot in place, so the UI feels live without falling back to SPA state orchestration.
UI Rendering & SSR
Reactive Import
Background batches keep moving, and the page reflects server progress as live HTML instead of a client-managed progress app.
UI Rendering & SSR
Reactive Analytics
Independent analytics jobs can light up one dashboard progressively, while the page stays server-rendered from the first byte.
UI Rendering & SSR
Reactive AI Task
Submit a task and watch the AI pipeline stages reveal one by one as the cron job processes it.