Internal Developer Portal

This project is an internal developer portal built to help engineers find information quickly, understand the systems they depend on, and work more independently. It brings together application data, API details, SDKs, infrastructure projects, ownership information, and developer-facing documentation in one place. The application is built with Next.js and React, backed primarily by Contentstack for structured content, with Nextra powering the documentation experience.

The Problem

In a growing engineering organization, information tends to fragment across codebases, internal knowledge, and scattered documentation. That slows teams down. People spend time asking who owns a system, where to find a specification, or whether an API already exists instead of moving directly into implementation. The goal of this portal was to create a trusted source of truth that reduces that friction.

What I Owned

Key Decisions

I focused on making the portal useful for day-to-day engineering work, not just as a static reference site. Searchable and filterable table views help developers narrow large sets of APIs, applications, and other assets by name, owner, or technology. Pagination and responsive UI patterns keep the experience practical even as the dataset grows.

At the detail-page level, I wanted developers to have a single place to understand a system. When available, API pages render OpenAPI specifications directly in the portal, alongside project-level materials such as README and changelog content. That gives teams an immediately useful view of how a service works without making them hunt across multiple tools.

Outcome

The result is a portal that supports faster self-service for engineers. Teams can look up ownership, explore APIs and applications, and read standards documentation without relying as heavily on tribal knowledge or side conversations. From an employer’s perspective, this project is a strong example of how I work: I build practical tools, care about usability, and turn complex internal information into something people can actually use.

I also built a dedicated chatbot experience for the developer portal, but I have broken that out into its own case study so I can show the architecture and design decisions in more detail. You can read that write-up here.