rendering

• SSR Philosophy

  Semitexa SSR is one continuous rendering architecture: page, slots, deferred regions, live refresh, and interactive components stay inside one server-owned story.

• 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.

• 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.

• Components

  Reusable, attribute-registered UI components — discovered automatically from the classmap.

• SEO

  Set title, description, and Open Graph tags from your handler — no template hacks needed.

• Asset Pipeline

  Declare assets with glob patterns in assets.json — served, versioned, and injected automatically.

• 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.

• Script Injection

  Deferred blocks carry their own JS — injected once when the block arrives, never duplicated.

• Deferred Blocks

  SSR renders the shell first, then expensive regions stream in as real HTML over SSE — no SPA handoff and no client-side page rebuild.

• Block Isolation

  Two identical blocks on the same page run independently — scoped DOM, scoped JS, no conflicts.

• 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.

• App Shell

  A multi-page admin feels like one application by marking which regions change per page — the framework derives the chrome-less variant and ships the client that asks for it.

• Reactive Report

  Background work updates an SSR-first slot in place, so the UI feels live without falling back to SPA state orchestration.

• Reactive Import

  Background batches keep moving, and the page reflects server progress as live HTML instead of a client-managed progress app.

• Reactive Analytics

  Independent analytics jobs can light up one dashboard progressively, while the page stays server-rendered from the first byte.

• Reactive AI Task

  Submit a task and watch the AI pipeline stages reveal one by one as the cron job processes it.

• UI Primitives

  The atomic ui="..." vocabulary -- button, input, label, field-shell, surface, badge -- and the attribute-driven runtime behind it.

• UI Composition: UiPart and UiSlot

  How a component declares the primitives it is made of, how part props resolve, and how bind, slots and inputProps behave.

• UI Events and Transport

  Declaring events with UiOn, the signed render-time manifest, the capture-only frontend runtime, the HTTP dispatch endpoint and the SSE push channel.

• UI Forms

  Composing platform.form, the authoritative submit pipeline, per-field signed projection and the playground.

• UI Grammar Reference

  The attribute grammar a component author writes: what each attribute means and where it is allowed.

• UI and SSR Integration

  How platform-ui primitives and components sit on top of the SSR module.

• Twig Template Cache

  How the Twig cache behaves under long-running workers and when you need to clear it.