Guide 01

Website & Landing Pages for Developer Tools

A comprehensive guide to creating developer-focused websites that convert. From foundational principles to advanced design patterns.

Level 1: Foundations

Developer Trust Ladder

The Core Truth About Developer Websites

Developers want to understand what your tool does, when it's good for them, and when it isn't. They know there's no silver bullet and there are tradeoffs. Saying where your tool is NOT a great fit gives comfort and safety to devs.

"Show me options and let me choose" — The developer mindset

The One Metric That Matters

If you could choose one metric for your entire dev marketing efforts: Time to First Hello World.

Measure it from signup or from landing on the website. It's a proxy for how smooth the try-out experience is and a great candidate for your activation metric.

What Makes Developer Websites Different

Modern dev-focused companies are moving away from corporate aesthetics toward:

Examples: Vercel Workflows, DagsHub, modern Supabase

Level 2: Header & Value Proposition

The Anatomy of a Great Dev Tool Header

A strong header needs these components:

  1. The "What" — Explained immediately (e.g., "Video API", "live and on-demand experiences")
  2. Clear Persona — Who is this for ("for developers")
  3. Job to Be Done — What they'll accomplish ("build online video")

Example from Mux:

Value Proposition Frameworks

The Jargon Balance: Common wisdom says talk about values, not features. But for developers, using industry jargon often works great.

Solution: Show Both + The "How" (Tailwind CSS approach):

  1. Show the result
  2. Name the feature (use jargon)
  3. Show the code with highlighted relevant parts

This educates and inspires simultaneously.

Header Design Patterns

Pattern: Header with Tabs (Appsmith)
When your tool does many things, use tabs in the header to let users self-select their use case without overwhelming.

Pattern: Competitor Mention (Axiom)
In mature categories, explicitly own your unique selling point versus known competitors:

Pattern: Event Promotion in Header (Vercel)
For major events, place registration CTAs right in the header — it's the most viewed part of the most visited page.

Naming and Category Framing

Words carry expectations, fears, and hopes. The difference between calling yourself a "language" vs "framework" vs "platform" is massive.

Wasp Case Study:

Think carefully about: language, framework, platform, tool, suite, solution, app, extension

Level 3: Feature Sections & Visual Design

The Compact Scrolling Feature Section

Problem: Displaying multiple features without making pages exhaustingly long.

Solution (from Graphite):

Variants:

Interactive Diagram Sections (Buildkite)

For complex products:

Showing Code and UI Together

The dance of showing code without overwhelming:

CircleCI approach: Clean video explainers that balance code visibility with clarity.

Social Proof That Works

Beyond logos — Buildkite's approach:

Level 4: CTAs & Conversion

CTA Philosophy for Developers

Most CTAs should go to docs. Use actionable copy:

The "Playground" CTA Pattern

For infrastructure tools where showing value quickly is hard:

Good copy elements:

Example: "Play with Axiom" → "Launch Playground"

GitHub Star CTA Placement

Put your GitHub star counter/CTA in the navbar. It's always visible and capitalizes on social proof.

Docs-to-Conversion Trick

Add a signup CTA to your docs header.

Stripe added "Create Account" to their docs header and saw significant conversion impact. Apollo GraphQL saw 20% signup increase with this simple change.

Level 5: Developer Funnel Structure

Developer Funnel

The Developer Marketing Funnel

Unlike classic B2B (awareness → consideration → conversion), dev tools have:

1. Exploration

2. Demo

3. Internal Sale

Level 6: Navigation & Information Architecture

Navbar Best Practices

Self-hosted deployment placement (n8n):
Place self-hosted deployment guidance in docs tab dropdown. This frontloads a key differentiator where developers naturally look.

What else to surface in docs dropdown:

The "Escape Hatch" Principle

People will land on wrong pages. Example: Googling "Stripe checkout" can land you on dev-focused or no-code-focused page.

Solution: Put a link/button at the top to help people go to the page they actually wanted.

Level 7: Specific Page Types

Comparison Pages

Developers search competitively more than typical buyers. Clear comparisons capture high-intent traffic.

New Relic vs Datadog approach:

Pricing Pages

Elena Verna's Framework:

Retool's Clarity:
Instead of ambiguous deployment terminology:

Level 8: The Complete Picture

Who Should You Address on the Homepage?

Land messaging for the champion, not the broadest audience.

Developers naturally think and talk about products through anchoring. Use it in your messaging.

Anchoring examples:

The Clear Copy Test

Two versions tested:

  1. "The easiest way to capture and transcribe meetings"
  2. "The API for developers to access meeting recordings, transcripts and metadata"

Version 2 won. It clearly says what it does. The first sounds like an investor pitch. The second captures interest of people searching for solutions.

Positioning Advice

Don't be "for every company on the planet."

Early on: Start narrow, build credibility, build one fantastic product people rave about. Then go wider.

Example: Snyk's narrow initial positioning — they didn't try to be everything from day one.

Quick Reference Checklist

Header

Value Proposition

Navigation

Social Proof

Feature Sections

Conversion Elements

Resources & Further Reading

Comprehensive Guides

Value Proposition & Positioning

Examples

Podcasts