Context
Important reasons, ownership, architecture boundaries, and outcomes were distributed across repositories and working conversations. That made it difficult to explain why a system existed, who decided a trade-off, what was currently true, or how a new reader should continue.
Katteke needs public transparency without exposing private runtime state, raw conversations, credentials, personal data, customer information, or unpublished repository content.
Decision
Katteke will maintain docs.katteke.com as its canonical public documentation portal for company governance and philosophy, shared standards, evidence-based product entries, durable public decisions, and periodic reports.
The portal will:
- use English as the canonical language and provide curated Dutch pages where they serve the Dutch audience;
- use a separate Zola 0.22.1 static build with raw CSS and minimal progressive JavaScript;
- run as a separate Cloudflare Pages project from the marketing site;
- identify Rei, Founder & CEO, as public author and final decision authority;
- publish machine-readable product and decision indexes;
- keep claims proportional to current evidence;
- exclude private and sensitive working material.
Rationale
A static portal is lightweight, fast, auditable, easy to archive, and does not require an application runtime. A separate build prevents documentation choices from coupling to the React marketing site and provides a clean path for future site migration without requiring it now.
Central navigation makes context discoverable, while decision and reporting standards keep the portal from becoming an unstructured archive.
Alternatives considered
- Keep documentation inside individual repositories only: useful for implementation detail but insufficient for company-wide discovery and responsibility.
- Use the marketing application as the only docs UI: would couple public company memory to a heavier application stack and release path.
- Publish raw working conversations: faster initially, but unsafe, noisy, difficult to maintain, and not a trustworthy system of record.
Consequences
Katteke must maintain indexes and canonical pages when product truth changes. Reports require evidence and founder review. Curated translations may lag English and must say so through navigation rather than silently presenting stale copies.
The portal creates no certification, product-readiness, public-company, or financial-reporting claim.
Review trigger
Review this decision if the canonical domain, company ownership, publication model, primary static-site generator, or public/private boundary changes.