Developer Community
Senior UI / UX Designer

Developers often consume docs on mobile while creating and editing content on desktop. This redesign made the developer community easier to use on the go and helped increase mobile traffic.

    • Team
    • Project manager
    • Lead UI designer (me)
    • Lead UX designer
    • UX researcher
    • Lead front-end engineer
    • Timeline
    • 6 months
    • 2019
    • Platform
    • Responsive web

Discovery

Research showed that developers did not follow one predictable path to API content

Different developer behaviors called for a more flexible navigation model

  • Some participants wanted to move quickly and grab code examples right away. Others wanted a broader understanding first, but still needed to move efficiently between tutorials, documentation, quick starts, and examples.

  • Instead of following a single linear journey, participants moved between content types based on what they needed in the moment. That meant the navigation had to support multiple pathways, not one ideal route.

Navigation layout showing multiple developer pathways
  • Participants found Recently Viewed and signed-in update content helpful. Two of the three users who saw these updates said they would find them useful.

  • Design takeaway: personalized content had value, but it needed to support return visits without distracting from primary tasks.

Homepage wireframe showing personalized update content
  • Some participants could become disoriented when using menu anchors because they behaved differently from standard navigation links.

  • Design takeaway: anchor links needed clearer visual cues and feedback so users better understood where they were going.

Anchor menu interaction wireframe

Interaction Design

My main focus was designing a navigation model that could support different developer behaviors across mobile and desktop. The solution combined existing design pattern library components with a new side-navigation approach built for a content-rich experience.

We validated the direction through mid- to high-fidelity responsive prototypes, using InVision and HTML/CSS to test how well the navigation supported scanning, movement, and orientation.

The proposed side navigation interaction

Side navigation interaction concept
  • Mobile side navigation interaction
  • Desktop side navigation interaction

Side navigation in responsive layout

Responsive side navigation layouts

Selected UX screens

These screens show how the updated navigation and content structure came together across key experiences.

  • Authenticated homepage
  • Unauthenticated homepage
  • Events page
  • Tutorial page
  • Overview page

UI System

Alongside the navigation work, I helped extend the UI foundation so the experience could stay consistent as content and layouts scaled across devices.

Colors

  • Refinitiv blue
  • Refinitiv dark blue
  • Refinitiv darker blue
  • Refinitiv orange
  • Refinitiv purple
  • Refinitiv teal

Typography

Typography system

Buttons

Button styles

Forms

Form styles

Column grids

Responsive grid system

Impact

This work helped modernize a desktop-centric developer experience for more flexible, on-the-go use. By improving navigation clarity and responsive usability, the redesign better supported how developers actually discover and consume technical content.

It also created a stronger foundation for future site growth by introducing a more scalable navigation model and a more consistent UI system.

Additional UI concepts

I also explored dashboard concepts to make API service usage feel more visual and engaging for existing customers. These concepts were intended to bring more clarity and energy to product usage data.

Next case study