k8ordo

Packages

• @k8ordo/uiReact components with semantic design tokens, i18n, and generative-UI adapters.
• @k8ordo/formDerives HTML constraint attributes, messages, and server-side validation from one zod schema. The DOM holds the values, so it works without JavaScript.
• @k8ordo/stateDeclares state by where it lives — URL, history entry, localStorage, memory — one zod schema each, riding the Navigation API.
• @k8ordo/routerThe URL's pathname axis, owned. The route table is the application's pathname schema, and from it come the types, the matching, the links and the navigation. Search params and history-entry state belong to @k8ordo/state — the division is the URL's own "?".
• @k8ordo/staticBuilds an application into files. Every route is rendered ahead of time, and what ships is a directory a static host can serve — no server at run time.
• @k8ordo/serverRuns an application. Every request is answered by rendering, so route parameters need no list of values, an unknown URL is a real 404, and a form can post to a Server Action.

Shared commitments

1. Baseline only

   A feature is fair game the moment it reaches Baseline newly available — shipped in all four core browsers — rather than 30 months later at widely available. With no polyfills and no fallbacks it runs only on current browsers — it did not drop the old ones, it never ran on them.

2. Always on the latest React

   React 19 and Server Components are assumed, and each new idiom is adopted as it lands. No compatibility path is kept around, so there is only ever one way to write it.

3. TypeScript safe

   Types are not there to check what you wrote after the fact — they are there to make the mistake unwritable. Docs and generated artifacts are derived from the types, so they cannot drift from the implementation.

4. Readable by agents

   Every package ships its own documentation inside its npm package, so an agent reads the exact version you installed — nothing to copy, nothing to re-sync, no version drift.