Context. A growing developer ecosystem needed documentation that could scale — but the existing WordPress infrastructure lacked the flexibility to keep up, and updates were happening through email threads, Slack messages, and long in-person sessions instead of a real system.
Process. The strategic call was to reject the expedient option. Rather than patch WordPress, the rebuild moved to Vue.js with Markdown publishing — lowering the DevOps burden while opening the platform to visual customization pulled straight from the existing design system. Contributors, including non-developers on the content team, could submit updates directly through GitHub, with core-team review before anything published.
Solution. The final system paired two integrated platforms: the new Vue.js/Markdown site for general documentation, plus an Angular SDK reference site (powered by Doxygen) for iOS/Android integration docs — both styled and maintained to match the product's visual language. Navigation and structure were generated directly from Markdown headings, functioning as a living index rather than a hand-maintained one.
Outcome. The documentation held up under real partnership pressure — it was instrumental during later client engagements — and proved a broader point: it's alright to think outside the box. Prioritizing team composition and long-term maintainability over the fastest fix produced a better outcome than sticking with the existing tool.