Live demo

1 · Require One package

composer require semitexa/platform-ui — brings primitives, the grammar compiler, skins and runtimes.

2 · Nothing to build Self-registers

Primitives, components, Twig helpers and assets register through the module system. No Node, no bundler.

3 · Render It just paints

{{ primitive('button', …) }} renders server-side, styled by the active skin. The bundle + runtimes auto-require.

composer require No build step Assets auto-required

Install Platform-UI

Getting Semitexa UI is adding one package. It brings the primitive registry, the sx-* / ui-* grammar and its CSS compiler, the skin token system, and the three tiny runtimes — all server-side. No Node build, no client framework to bootstrap.

1composer require semitexa/platform-ui

composer require semitexa/platform-ui

What registers itself

Through the module system, the package self-registers:

Primitives & components — resolvable by canonical name (platform.button) or alias (button).
Twig helpers — primitive(), component(), ui_part(), theme_skin_css().
Assets — the per-route CSS bundle and the runtimes are required automatically the moment a page renders a primitive or component.

A skin's tokens.css is loaded last so it wins the cascade. There is nothing to wire by hand.

One package, no build pipeline, means the UI layer shares the operational story of the rest of the server: deploy PHP, render HTML. No separate frontend deployment, no bundler config, no client-framework version to track. Next: render your first component.

1# add the package2composer require semitexa/platform-ui

# add the package
composer require semitexa/platform-ui

1{# …then in any template, the helpers are already available: #}2{{ primitive('button', { text: 'It works', tone: 'brand' }) }}

{# …then in any template, the helpers are already available: #}
{{ primitive('button', { text: 'It works', tone: 'brand' }) }}

How it works

composer require semitexa/platform-ui. The package self-registers its primitives, components, Twig helpers (primitive(), component(), ui_part(), theme_skin_css()) and assets through the module system. A skin's tokens.css loads last so it wins the cascade; the per-route CSS bundle and the runtimes are required automatically the moment a page renders a primitive or component.

Why it matters

One package, no build pipeline, means the UI layer shares the operational story of the rest of the server: deploy PHP, render HTML. There is no separate frontend deployment, no bundler config, and no client-framework version to track.