developer landing page

Status: ready — not yet trained.

Traits

Developer Voice

Direct technical tone ↔ Marketing department voice

Whether the copy reads like a developer wrote it for developers — direct, specific, technically honest, dry — versus reading like it passed through a marketing approval process: superlatives, benefit-speak, passive constructions, and enthusiasm markers.

Honest Scope

Named limits and trade-offs ↔ Vague universal claims

Whether the page accurately represents what the product does and does not do — naming limitations, trade-offs, and non-goals explicitly — versus making vague universal claims, suppressing scope boundaries, or implying the product solves all related problems.

Path Clarity

One clear next action ↔ Ambiguous or absent next step

Whether the page makes the next action unambiguous at every decision point — one clear CTA per section, labeled with what happens when you click it — versus ending sections without a next step, presenting multiple competing actions of equal weight, or burying the path to getting started in prose.

Show Don't Tell

Code and output shown ↔ Capabilities described only

Whether the page demonstrates the product through actual code, commands, terminal output, or concrete before/after examples — versus describing capabilities in prose without showing the product in action.

Technical Credibility

Technical depth as proof ↔ Social proof theater

Whether the page establishes trust through technical specificity — architecture decisions, named trade-offs, real benchmarks with methodology, links to source code, acknowledgment of alternatives — versus using social proof theater: "trusted by thousands", award claims, unnamed enterprise logos, and credibility borrowed from vague association.

Time to Understanding

Instant precise definition ↔ Abstract positioning blur

Whether the first paragraph or headline delivers a precise, specific description of what the product is and who it is for — versus opening with abstract positioning language, taglines, or capability-neutral phrasing that forces the reader to hunt for the actual definition.

Zero Friction Try

Immediate no-signup access ↔ Gated behind signup or sales

Whether a visitor can run or try the product immediately without signing up, entering a credit card, scheduling a call, or installing significant prerequisites — versus gating access behind account creation, sales contact, or complex setup.