Talk about your next project
GitHub content marketing

The lesson

Frame a gated whitepaper with one research-backed problem, then put the download form beside the copy that makes the asset feel worth requesting.

The move

A small label, "WHITEPAPER", sits above the title "How to increase developer productivity" and the date "November 6, 2022". The body opens with GitHub's survey of more than "1,600 developers, security leads, and executive decision makers" and says their shared goal was developer productivity. The copy argues that fragmentation is the enemy of productivity, naming context switching, remote collaboration gaps, and siloed knowledge. A "Download PDF" form asks for work details, followed by share links, a Software Development tag, and a row of other resources.

Why it works

  • Our readThe opening survey context names who GitHub interviewed, so the whitepaper feels grounded before the form asks for information.
  • Our readThe copy challenges simple productivity measures like pull requests and lines of code, which gives the reader a sharper reason to keep reading.
  • Our readThe form stays beside the pitch on desktop, so the action is visible while the reader scans the problem and promised takeaways.

What not to copy

Don't copy GitHub's survey language, developer-productivity argument, or resource recommendations. Keep the structure of research proof, problem reframing, specific causes, and a visible download form.

More from GitHub

More content marketing

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.