How we evolve our knowledge base
Our “knowledge base” is not a separate SaaS product—it is the same static HTML you ship: Docs, Tutorials, handbook pages, and honest copy on key landings. The goal is self-service first.
Documentation vs quick answers
Docs stay the structured reference (how things work, prerequisites, links). FAQ-style handbook notes and short sections on high-traffic pages cover the recurring “what do I do when…” moments without duplicating the whole manual.
Self-service
Pages must be skimmable, on-brand, and easy to search in-browser; we prefer fixing confusing UI copy over writing a long article nobody reads.
Up-to-date content
Stale HTML is inherited tech debt. Support threads are the signal for what to update next; changes land via PR on GitHub and deploy through Vercel so what we publish matches what users see.