The problem
A documentation platform lives or dies on two things that pull in opposite directions: authors need it to be flexible enough to structure real, messy knowledge, and readers need it to be fast, calm, and easy to move through. Push too far toward author power and you get a tangled reading experience; push too far toward simplicity and authors can't express what they need to. Avenra had to hold both.
On top of that, documentation only earns its keep if people can find it. That made search-engine discoverability a first-class requirement, not an afterthought — the content had to arrive as real, meaningful HTML that both readers and crawlers could rely on.
The approach
I worked across the whole stack: modelling how documents and their structure were stored, building the interfaces authors used to organise content, and shaping the reading experience on the other side. The guiding principle for the reader-facing side was restraint — good documentation design gets out of the way. Clear typography, obvious navigation, and pages that load quickly matter far more than anything decorative.
Because discoverability mattered, I made sure pages rendered meaningful content on the server rather than depending on client-side JavaScript to fill them in. That decision — server-first rendering — is the difference between documentation that ranks and documentation that's invisible, and it's a trade-off I've written about in choosing a stack for a new product.
The stack
Avenra pairs a structured content model with fast, server-rendered reading pages and author-facing tooling for organising knowledge. I focused on keeping the data model clean enough that new kinds of content could be added without rework, and on keeping the reading pages light so navigation between them felt instant. Performance wasn't a phase at the end — it was a constraint I designed around from the start, the way I describe in building fast interfaces.
The outcome
The result is a platform where authors can structure real knowledge and readers get a fast, uncluttered experience that search engines can index properly. You can see it in production at docs.avenra.online. Building it reinforced something I keep relearning: the best documentation tooling is the tooling you don't notice, because it never gets between the reader and the answer they came for.