01
Model the docs as HTML-first
The homepage and article pages render their headings, descriptions, and navigation in initial HTML. An interactive search is a focused enhancement rather than a prerequisite for reading.
02
Keep content and mutation policies separate
Article slugs must be validated, unknown pages should return a real 404, and contact submission requires input validation, trusted origins, authorization/rate limits, and idempotency where appropriate.
03
Validate every capability
The reference matrix covers rendering, interaction, forms, routing, SEO, media, security, performance, and operations. Treat it as a release checklist, not optional polish.
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
Run the Workbench reference
Shellpnpm --filter @mohammedaydan/example-nexis-workbench verify
pnpm --filter @mohammedaydan/example-nexis-workbench start- OUTPUT
- A real workspace example builds static articles, a Link runtime, a native form, and Action safety tests.
- BOUNDARY
- Its session and persistence seams are typed application contracts, not a fake built-in identity or database.
- PROVE IT
- Inspect HTML for Link and form output, then run the four Action rejection/acceptance tests.
VERIFICATION
Prove the contract.
Use the example matrix to test a full docs app in both no-JavaScript and enhanced browser paths.