Talk about your next project
Astro case study

The lesson

Add a Requirements section between the problem and the solution so the reader sees the customer's constraints before your product meets them.

The move

A gradient banner with the Contenda logo sits above a dark card reading "Case Study • June 2023", the headline "Content for Everyone" and the subhead about building a content-sharing platform in one month. Three intro paragraphs explain who Contenda is and what developer advocates do, followed by an illustration captioned with Contenda's own pitch. The body runs "Challenges", "Requirements", "Solution and Implementation" with a large pull quote from Grady Salzman, Software Engineer, then "Results" with 30% of users sharing blogs through Share Pear and the one-month build time. Two product screenshots of the share feature appear around Results, and a "Take Astro for a spin" banner closes the story.

Why it works

  • Our readThe "Requirements" section lists no backend changes and low or no cost, so a developer reader can check those constraints against their own before reading the outcome.
  • Our readExplaining what developer advocates do before the problem lets a reader outside that field follow why sharing drafts mattered.
  • Our readThe headline promises a time frame, and Results confirms it with the one-month build and the team's own estimate of how long it would have taken otherwise.

What not to copy

Don't copy the Netlify on-demand builders detail, the Discord community angle or Contenda's AI content pitch. Keep the logo banner with a dated label, the short context intro, the Challenges, Requirements, Solution and Results sequence, one large engineer quote and screenshots of the shipped feature.

More from Astro

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.