A reference library with an editorial backbone
Tech Library is a modular reference for web, application and systems development. It combines a browsable technical catalog with explicit source provenance, immutable revisions and a controlled publication process.
The starter collection contains 32 curated topics across frontend, backend, data, mobile and desktop development, DevOps, testing, observability and security. English entries are the canonical source texts, while translations remain tied to specific English revisions and fall back explicitly when a translation is unavailable.
Discovery for readers
- Faceted browsing and SQLite FTS5 search across the reference catalog.
- Danish and English interface/content selection without translating source code or established technical terms.
- A dark-first interface with a persisted light/dark preference.
- Reader accounts with private topic favorites.
- An installable React/Vite progressive web application.
Monitoring proposes; editors publish
An independent worker monitors enabled official sources and normalizes volatile page content. A changed fingerprint produces a deduplicated finding, while fetch failures update source health instead of being treated as editorial changes.
An administrator reviews the source and prepares an immutable draft revision. Approval is required before publication, and the active publication pointer and search index are updated together. Rollback selects an earlier approved revision rather than overwriting the historical record.
A modular application stack
The web application uses React, Vite and local shadcn/ui primitives built on Radix accessibility foundations. A Fastify API handles the editorial policy and authentication, while shared contracts use Zod schemas and public TypeScript types.
SQLite and Drizzle provide the data layer, and a separate worker handles monitoring. The repository includes a Docker Compose topology, health checks, persistent storage and operations documentation covering backup and restoration.
Built for accountable technical knowledge
The interesting design choice is the separation between finding a source change and accepting it as published guidance. Claim-level provenance, explicit translation revision links and publication history make the reference inspectable rather than presenting automated updates as unquestioned truth.
Local development requires the documented Node.js/npm versions and initialization steps. Deployment-specific credentials and session configuration should be supplied privately; they are intentionally not reproduced here. The featured artwork is a conceptual knowledge-library illustration, not a screenshot of the application.
Explore the repository
Read the source code and project documentation for the latest implementation details and setup instructions. This description is based on the public repository reviewed on October 29, 2026.