Talk about your next project
NX case study

The lesson

Prove the result held while the problem grew, and state the honest range next to the headline number.

The move

The headline and a one-line subhead sit over a dated video, followed by a stat bar reading "116+ projects", "45→6 minutes on CI" and "6 days of computation saved every single day" beside a "Ready to get started?" button. A short company intro leads into "Challenge", which has bulleted problems, a pull quote about modifying several repositories and the "45 minutes per run" pipeline. "Solution" opens with the team choosing Nx after evaluating Nx and Turborepo, then lists the tools used. "Results" runs under four subheads such as "Pipeline Speed Improved Despite Codebase Growing to Hundreds of Projects", and the page ends with a "Reach out to our team!" box and "Discover more" links to other stories.

Why it works

  • Our readThe stat bar gives a skimming engineer the before and after CI time and project count before any body copy.
  • Our readNaming the rival evaluated, Turborepo, and the real goal of modularizing a monolith tells a buyer in the same spot that the comparison was made.
  • Our readSaying most runs are around 6 minutes with some reaching up to 20 minutes makes the headline figure easier to trust.

What not to copy

Don't copy Hetzner's GitLab merge train details, the Nx Replay and Nx Console feature tour, or the private beta banner. Keep the stat bar under the hero, the Challenge, Solution, Results order, the named alternative that lost, and results subheads that each state one outcome.

More from NX

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.