Section Overview
The shortest path from fresh scaffold to a trustworthy local Semitexa runtime: install, boot, understand the module map, bind a real host, and reach the first tenant boundary.
Support Semitexa
Built for developers who prefer control over magic.
Your support helps keep it fast, open, and evolving.
Module Structure
Use the minimal version to understand the request path itself. Use the extended version to understand how Semitexa turns that path into a guided demo module with SEO, navigation, and source-backed context.
Minimal Stack
This is the narrow path that needs to exist for any simple feature page: transport in, use case out, response rendered.
Payload owns the route contract, path params, and request boundary.
Handler owns the use case and produces one typed resource.
Resource owns the outgoing response, metadata, and render context.
Template owns presentation only and stays declarative.
Extended Stack
Once the route works, the demo layers on a catalog, curated navigation, SEO defaults, grouped learning order, and source-linked explanations.
Catalog service assembles sections, groups, and navigation layers.
Shell context adds SEO defaults, nav mode, and shared demo metadata.
Section pages explain the learning order and group live routes by responsibility.
Preview templates make the module feel like a product, not a stack of loose samples.
Responsibility Map
The demo becomes easier to learn when every layer keeps one job and the module description says that out loud.
Onboarding Pages
Open these pages in order if you want the shortest path from a fresh install to a realistic Semitexa local setup.
Start Here
Create the project, review the baseline env contract, and bring up the Semitexa runtime the supported way.
Start Here
Register .test domains through the built-in local-domain helper instead of relying on ad hoc host setup.
Start Here
Establish one default tenant context early so tenant-aware behavior is visible before the rest of the application grows.
Start Here
Configure the minimal Locale contract so translations and locale-aware rendering become explicit early.
Start Here
Use the Semitexa AI console as a command translation surface over real operator commands.
Start Here
Understand why Semitexa keeps transport, use case, and rendering as separate explicit responsibilities.