Talk about your next project
Gatsby case study

The lesson

End a technical case study on a step-by-step timeline of one metric, so the reader sees each stage of improvement and not just the final number.

The move

The hero pairs the title "LaunchDarkly's Headless Gatsby and Prismic Site" with one sentence on what LaunchDarkly does, a credit to agency Woolly Mammoth, and a shot of the finished LaunchDarkly site. "The LaunchDarkly Story" lists the old stack (JSON, Markdown, hard-coded copy, a WordPress blog on a subdomain), then "What was LaunchDarkly looking for?" sets six goals in an icon grid, such as "Blazing fast page load speeds" and "Friendly for non-technical teammembers". "The Challenge" carries a quote from Jay Gandhi, Senior Director of Marketing Operations at LaunchDarkly, and "Solution" walks through the Gatsby upgrade, Gatsby Cloud, and the move from WordPress to Prismic with a quote from Sam Logan, Founder of Woolly Mammoth. "Why Gatsby?" closes with build times going from 30 minutes to an hour on Netlify, to 11 minutes, to 4 minutes cold and 1 minute warm, to 42 seconds for incremental builds and 5 second deploy times.

Why it works

  • Our readListing the messy old stack first gives a developer a starting point they may recognize from their own site.
  • Our readThe six-goal icon grid lets a skimmer see what the buyer wanted before reading any paragraph, and each goal maps to a later section.
  • Our readThe build-time sequence names the previous host and each version step, so the final 42 seconds reads as a measured trend, not a single claim.

What not to copy

Don't copy the agency-as-narrator setup, the Netlify comparison, the series D deadline or the Prismic plugin details. Keep the old-stack inventory, the goals grid, a named customer quote and a named partner quote, and the closing metric timeline.

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.