Why
ProGlove’s products were scaling faster than its documentation infrastructure. This put onboarding, support, and partner integrations at risk.What
When I joined, the documentation was minimal content on a static MkDocs site. As the sole writer, I owned tooling, content, structure, reviews, and delivery across hardware, software, and APIs.How
I introduced Paligo for scalable authoring and faster review cycles. I migrated all existing content using Pandoc and custom scripts, designed a new information architecture for the full product portfolio, and implemented OpenAPI references for the public APIs. I customized the HTML and CSS so the documentation portal matched the company’s visual identity. I created all diagrams, screenshots, and short tutorial videos. I set up contribution and review workflows across documentation, product, development, and QA. This removed review bottlenecks and sped up publication.Result
Within a year, ProGlove had a multi-product documentation portal with versioning, release notes, media, and automatically updated API references, supported by sustainable documentation practices.© 2026 Strahinja Milošević | Author of all-maker.com, a part of the tech writing blog webring