the-homepage

# The homepage > Write your homepage for the person who actually reads it: the **end-user developer**, not the CTO who signs the check. The developer becomes your champion and sells it internally for you. **Use this when:** your homepage speaks to buyers/ROI, it's clever but vague about what the thing does, or a developer can't tell in 5 seconds whether to care, and can't start in 5 minutes if they do. ## The core rule (Czakon) **Address end-user developers on the homepage; put enterprise/ROI/buyer messaging on separate pages** (enterprise, pricing, case studies). If you write the homepage for the buyer, you've written it for someone who isn't there. ## Framework: the sections, in order (Czakon) 1. **Hook / core message**: immediately: what *is* it? Use a category ("CI for monorepos"), a known-incumbent comparison ("a Datadog alternative"), or a plain statement. **Headline = what it is · subhead = for whom / what job.** 2. **Hero**: a real product shot; two CTAs: **Get started** (signup) *and* **Docs**. Answer "what's in it for me?" up top. Lead with the **how**, not the why. 3. **Social proof, right after the hero**: recognizable logos are the fastest credibility you have. Impressive dynamic metrics (users, stars) if you've got them. 4. **Value prop & differentiation**: why you over the 10 alternatives (see `value-prop-that-converts`). 5. **Getting started**: a huge conversion lever. Free trial, **no credit card**, quick setup. Any hard barrier sends developers straigh...