25 Issues in 30 Days at Mindee
When I started at Mindee, there was a backlog of documentation issues on GitHub that had been accumulating for months. The docs site had structural problems, SDK documentation was scattered across private repos, and there was no consistent format for release notes.
I resolved 25+ documentation issues in my first 30 days.
Clearing the Backlog
The backlog wasn’t just typos and broken links. It was structural issues: pages in the wrong sections, missing content for shipped features, SDK documentation that users couldn’t find because it lived in private GitHub repos. Each issue I resolved reorganised structure and improved usability across the platform.
Clearing the backlog quickly wasn’t about showing off. It was about building trust with the engineering team. When developers see that you understand the product well enough to fix 25 issues in a month, they start trusting you with the bigger architectural decisions.
Migrating SDK Documentation
Mindee had Python, Node.js, and other client libraries documented in separate private repos that most users couldn’t even find. I migrated all SDK documentation into the main documentation site on ReadMe, creating a unified developer reference.
One place to find everything. That’s what developers expect, and that’s what they got.
Validating the API Reference
For the API reference, I tested endpoints against the live ReadMe interface to validate parameter and schema information before publishing. This caught discrepancies between the spec and actual API behaviour that would have confused developers.
Documentation that doesn’t match the API is worse than no documentation. At least missing docs are honestly missing.
Creating a Release Notes Format
There was no consistent format for release notes. Release information was communicated informally or buried in changelogs. I created a standardised format that gave users a reliable way to track what changed across versions.
Monitoring Performance
Beyond writing, I monitored documentation performance using Google Analytics, ReadMe analytics, and Hotjar. The Hotjar recordings were particularly useful: you could watch real users navigating the docs and see exactly where they got confused, went in circles, or gave up.
Content Beyond Docs
I also authored product blogs, ran the company newsletter, and contributed to the overall content strategy. The work at Mindee was about establishing systems where there were none: formats, structures, workflows. And doing it quickly enough to keep pace with an active product team.