Documentation Manager · Content Strategy · Information Architecture · Developer Experience
When I took on the API and developer documentation, the content was spread across multiple locations and formats, making it difficult for developers to find what they needed quickly. The documentation team struggled to keep the APIs updated due to the separation of code and documentation. I collaborated with a Project Manager to determine the need for our API documentation and how we could get developers more involved in the process.
The current experience lacked cohesion, clarity, and a central place where our technical audience could confidently navigate. I saw an opportunity to bring everything together into a unified, intuitive developer portal that felt supportive, structured, and scalable.
As the Documentation Manager for cPanel, I guided the migration and modernization of our API and developer documentation. My work included:
• Consolidating content into a single, developer‑friendly portal
• Rebuilding the information architecture for clarity and ease of use
• Standardizing content patterns and terminology using OpenAPI
• Improving navigation and reducing friction in common developer workflows
• Collaborating closely with engineering and product teams to ensure accuracy and alignment
• Creating a foundation that could grow with future API updates and product expansion
I began by auditing the existing API documentation and mapping out where developers were encountering gaps or confusion. From there, the technical writers and I reorganized the content structure, clarified endpoints and workflows, and introduced a style guide for our APIs that made the documentation easier to maintain and easier to understand. Once we started the conversion process, it was all hands-on deck. Our engineers created scraper tools that allowed the process to move quickly and make sure that we were getting all of the information from the previous implementation. Between Technical Writers, Engineers, and QA, we converted 1500 functions into Open API standards. Throughout the process, I partnered with lead engineers to ensure technical depth remained intact while improving readability and developer experience.
• A unified, centralized developer portal
• Clearer navigation and more intuitive content hierarchy
• Reduced time spent searching for endpoints or examples
• More consistent documentation across API versions and product areas
• A scalable structure that supports ongoing updates and new integrations
The previous documentation was a large wall of text, with no clear direction. Writers struggled to keep the documentation up to date, since often we would have to track down developers to understand the functions. There was no clear strategy and no branding.
Our new site, using Redocly, is better organized and has clearly defined paths for the user. The APIs are now updated by developers while the code is being written, which ensures that the content is accurate and updated regularly.