01
Build one coherent application
Follow the Nexis Workbench stages in order: create the project, render useful HTML, add safe static routes, enhance eligible links, add a narrow interaction, make shared state explicit, protect mutations, and ship a measured artifact.
02
Keep framework and application ownership separate
Nexis supplies rendering, routing, Link, Context, state, Actions, metadata, security primitives, adapters, and CLI contracts. Your application supplies its identity provider, durable storage, external service credentials, resource model, operational policy, and product-specific tests.
03
Prove each boundary
The executable Workbench example validates types, Action acceptance and rejection paths, compiler budget, static output, Link markup, a native form, and production serving. Extend it with provider-specific browser and integration tests before a real release.
PRACTICAL LABS
Run this capability.
Each example states the observable output, the boundary that remains your responsibility, and the check that proves the result.
01
Follow the full implementation path
Shellpnpm --filter @mohammedaydan/example-nexis-workbench verify
NEXIS_PORT=4174 pnpm --filter @mohammedaydan/example-nexis-workbench start- OUTPUT
- The reference path verifies types, Action policies, budget, and built HTML before serving.
- BOUNDARY
- The example demonstrates framework contracts; persistence, identity, deployment secret handling, and external integrations remain application-owned.
- PROVE IT
- Read the Workbench stages in order and add your provider-specific tests before release.
VERIFICATION
Prove the contract.
Run the Workbench verification command, inspect its built home/article/form HTML, then follow the production matrix before deploying an application of your own.