~/cases/mostly-aliveActive
Mostly Alive
Designing a knowledge system where wrong information matters.
→Problem
Safety content needs a stronger hierarchy and provenance model than an ordinary blog.
→Architecture
Markdown and Zod validation feed bilingual SvelteKit pages, MiniSearch and PWA caching.
→Trade-offs
A database-free delivery path simplifies operations, but content and validation must do more work before deployment.
Authoritative sources
Markdown + Zod validated frontmatter
MiniSearch client fuzzy index
SvelteKit EN · DE
Web + PWA offline basics
- Authoritative sources become validated Markdown content.
- SvelteKit serves bilingual content and a client-side search index.
- PWA caching keeps emergency basics available offline.
→Decisions & trade-offs
| Decision | Why | Trade-off |
|---|---|---|
| Separate safety instructions from humor | Presentation should never obscure an emergency action. | The editorial system carries an explicit content boundary. |
→Result
- The repository contains automated checks for content, search, auth and production rendering.
→Evidence
- Content parity
- EN · DE
- Offline basics
- PWA
- Verification
- Vitest
Native bilingual content model
Caching for emergency access
Content, auth and usability tests
→What I'd change today
The next step is keeping synchronized review of EN/DE safety content visible to contributors.