Final Result
The completed project is the Event Board example. You can inspect the source, run it in StackBlitz, or compare it with the code you wrote during the tutorial.
This tutorial moved through Nano Kit in the same order an app tends to grow:
- Start with one page and one store.
- Replace manual fetch state with query.
- Keep inputs reactive and pace expensive search requests.
- Move shareable state and page matching into the router.
- Add mutations for page actions and forms.
- Improve mutations with optimistic updates.
- Normalize shared records with entities.
- Prepare stores and router integration for SSR.
- Move API calls into injectable service classes.
- Add server rendering with
Stores$,Head$, hydration, and a bundled production server. - Add session auth with an HttpOnly cookie, a route guard, and SSR cookie forwarding.
- Translate the app and make SSR locale-aware.
- Test stores through injection contexts with a mock transport.
The important bit is not that every app must use every layer. The useful pattern is adding each layer when the app asks for it.