Skip to content
nexisv1.3.3Build with Nexis

Practical curriculum · 10 lessons

From first route
to enterprise release.

Build a correct mental model first, then add precise browser boundaries, secure Actions, application-owned identity policy, and production operations.

How to use this track

Learn the contract. Build the feature. Prove the output.

Foundation

Routes, semantic components, static paths, metadata, and the initial HTML contract.

Builder

Signals, resumable events, request-local data, Actions, and native-first forms.

Enterprise & Operations

Application identity, authorization, security layers, hosting, performance, tests, and release evidence.

CURRICULUM

Every lesson contains code, practices, and a lab.

00

Follow the production Workbench first

Use one verified sequence from an empty folder to a production artifact before selecting deeper feature guides.

01

Start with a route, not a client app

Create the smallest useful Nexis page, understand the initial HTML contract, and keep the first route entirely static.

02

Write components with stable boundaries

Compose static sections, define readonly props, and isolate a component only when it owns a coherent responsibility.

03

Model pages, static paths, and render modes

Map source files to stable URLs, generate known dynamic content safely, and select a rendering mode from data requirements.

04

Use resumability and Signals without rerendering

Add a minimal lazy handler, bind a Signal directly to the target DOM node, and keep state ownership explicit.

05

Load data and mutate it through secure Actions

Deduplicate request-local loads, build native-first forms, validate server input, and keep mutations outside client code.

06

Integrate authentication as an application boundary

Use Nexis session primitives with application-owned identity and storage boundaries.

07

Enforce authorization and compose middleware safely

Apply RBAC and ownership on the server, then layer request guards, correlation, and rate limits around the Nexis production middleware.

08

Secure the complete request path

Protect rendering, Actions, cookies, remote media, proxy headers, telemetry, logs, and releases as one layered system.

09

Host for throughput, latency, and safety

Select Node, Deno, or Cloudflare from runtime needs; use caching correctly; then deploy with observability and a rollback plan.

10

Prove the enterprise contract before release

Use layered checks for output, interaction, security, metadata, adapters, performance, and operational readiness.