brand
The primary readers are strict interviewers, advanced GitHub developers, and future maintainers evaluating the repository as a serious engineering artifact. They arrive in a browser, often from GitHub, and want fast evidence of architectural depth, technical rigor, validation discipline, and documentation quality.
This project teaches high-performance C++ through runnable examples, but the docs site must do more than teach. It must frame the repository as an archive-ready technical whitepaper, academy, and architecture guide that explains why the code exists, how the modules connect, how claims are validated, and where the project fits in the broader systems ecosystem.
Rigorous, scholarly, exacting. The tone should feel calm, credible, and opinionated, with enough visual character to avoid looking like a generic docs template.
Do not look like a default GitBook clone, a card-farm SaaS landing page, a glassy AI-generated template, or a cyberpunk dashboard. Avoid ornamental gradients, gimmicky hero metrics, and any layout that signals "marketing site" before "engineering publication".
- Show evidence, not slogans.
- Make reading flow as strong as visual style.
- Treat diagrams as arguments, not decoration.
- Keep bilingual entry surfaces structurally equivalent.
- Favor durable, low-maintenance design primitives over one-off flair.
Target WCAG AA contrast on both themes. Support reduced-motion users by keeping motion subtle and non-essential. Maintain strong readability for long-form technical content, including diagram captions, code-adjacent reference surfaces, and bilingual navigation.