Articles

Different MCP implementation patterns lead to different developer portal information architecture and publishing strategies. Rather than introducing a separate MCP portal, organizations can evolve their developer portal CMS to model new interface types alongside existing APIs, preserving a coherent organizational layer for discovery, governance, documentation, and AI-facing interfaces.

How can your different teams manage their preferred gateways while maintaining consistent oversight, documentation, and user experience across the enterprise? Across different multi-org setups, our approach enables a single developer portal. We outline three practical multi-org scenarios in their essence, which we can apply to your use case, be that with several Apigee instances or multiple gateways. 

Effective localization drives global growth and boosts competitiveness. In this article, we dive deep into the importance of translation and localization and introduce how Drupal can enhance content comprehension and provide a smooth and engaging experience with features like RTL layout adjustments or UTF-8 compatibility.

A large, Netherlands-based financial services provider partnered with Pronovix to improve its developer portal’s UX and content structure. The Techwriters introduced API flow guides, refined onboarding, and ensured better content organization for lasting improvements. This article explores the challenges encountered and how UX and technical writing expertise can make a difference.

What does the near future hold for developer portals? Further specialization towards platform-like and product-specific microportals. Flexible user experiences, to expose the diversity of interface- and gateway integrations. Authoritative and authentic documentation will be more important than ever before. 

Excellent OpenAPI specifications enable developers to gain clarity on data structures and responses, while automation tools leverage these specs for better code generation and testing, reducing manual effort. In this article, we share some best practices and highlight the essential elements for a better OpenAPI specification.