Talk about your next project
Mintlify case study

The lesson

Tie each product feature to the moment it changes a user's next step, so a story without hard metrics still shows cause and effect.

The move

The hero pairs the headline "How Kalshi uses developer docs to drive API adoption" with a "Talk to our team" button and a dark Kalshi logo panel. A bold one-sentence description of Kalshi leads into two shaded boxes, "Challenge" and "Solution", beside a sidebar listing "200+ pages", customer since "2025" and Finance, Developer tools. Under "A developer-first API hub", one bullet list names the deployed features, a second explains why each one mattered, such as "The playground removes friction", and "Plans for synchronized releases" lists what the team is exploring next. A pull quote from Brian Ta, Founding Growth Product Lead at Kalshi, closes the story before related stories and a "Start for free" call to action.

Why it works

  • Our readThe Challenge and Solution boxes give a skimmer the whole story in two short paragraphs before the detail begins.
  • Our readThe second bullet list explains each feature by what a developer would otherwise do, such as configuring Postman or opening a ticket, which makes the value concrete without a metric.
  • Our readThe sidebar facts on docs size, start year and industry let a buyer check fit at a glance next to the opening paragraphs.

What not to copy

Don't copy Kalshi's prediction market framing, the point about trading bots and AI agents reading docs, or Mintlify's feature names. Keep the boxed Challenge and Solution pair, the feature list followed by a why-it-mattered list, the forward-looking plans section and the sidebar of firmographic facts.

More from Mintlify

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.