Northwind
Documentation, API exploration, and account keys unified into one coherent developer journey.
System decisions
- Reorganized content around developer jobs instead of the company's internal product structure.
- Connected guides, API reference, examples, and account configuration through predictable navigation.
- Defined reusable documentation and code-pattern components with responsive behavior.
Case study
Challenge. Developers had to jump between documentation, an API explorer, and account settings to complete a first integration. Navigation labels reflected internal teams, making even common tasks difficult to locate.
Approach. I audited the content, grouped support questions into developer jobs, and used tree testing to refine the new structure. We prototyped the full path from choosing an endpoint to creating a key, testing a request, and resolving an error.
Outcome. The new portal treated documentation and account tools as one product. Shared patterns for navigation, code samples, parameters, and response states gave content and engineering teams a consistent system for future endpoints.
Before & after
Disconnected documentation and account tools became one task-based developer journey, from choosing an endpoint through testing a request and resolving errors.
#3157D5 → #7A5AF8#101828#344054#F2F4F7Color library
Electric blue and violet identify interactive paths through the developer journey. Layered slate tones organize navigation, code, and account tools, with a cool gray canvas that reduces glare around technical content.
Font library
Inter provides a neutral, dependable voice for navigation and product controls. Space Mono gives code, endpoints, parameters, and generated values a clear technical texture.