brand
Primary readers are senior developers, performance-minded library evaluators, open source maintainers, and technically strict GitHub community members. They arrive in a research or review mindset, usually to judge architecture quality, API clarity, benchmark credibility, and maintenance posture before deciding whether BitCal deserves trust, adoption, or contribution time.
BitCal's Pages site exists to present the library as a serious systems project rather than a generic utility package. It should help advanced readers understand the vNext public model, algorithm organization, dispatch boundaries, evidence posture, and support limits with the clarity of a technical whitepaper and the navigability of a modern documentation system.
Rigorous, precise, high-agency. The tone should feel academically grounded, technically self-aware, and quietly confident. It should communicate that BitCal values contract fidelity, benchmark honesty, and engineering craft more than marketing volume.
- Generic SaaS landing pages with feature-card grids, empty buzzwords, and inflated claims
- Beginner-first documentation portals that bury architecture behind onboarding fluff
- Loud neon "cyber" aesthetics that look technical but reduce readability
- Hand-wavy benchmark pages that present local numbers as universal truth
- Lead with thesis, not slogans: every major page should clarify a technical position or support a claim.
- Evidence before promise: surface support boundaries, benchmark caveats, and migration costs plainly.
- Reading flow is product design: navigation should guide advanced readers from architecture to evidence to contract detail without dead ends.
- Visual polish must serve comprehension: figures, contrast, spacing, and typography exist to make technical ideas easier to inspect.
- Distinctive restraint wins: the site should feel authored and premium without falling back to startup-template tropes or decorative noise.
Target WCAG 2.1 AA contrast and focus on strong readability in both light and dark themes. Diagrams and SVG figures must remain legible in both modes, motion should stay subtle and optional in spirit, and long-form content should preserve scannable hierarchy, sensible line length, and link clarity for readers doing deep technical evaluation.