Skip to content
Browse themes

Open Source Project

The install command above the hero, the API in twenty lines, and who funds it said plainly — because “what happens if the sponsors stop” is the question that decides whether a team takes the dependency.

9 blocks295 lineslucide-reactAdded 14 Sept 2026

What's included

  • app/oss-landing-page.tsx
  • 9 blocks it is built from, installed with it
  • Needs lucide-react

Works with

  • React
  • Next.js
  • Tailwind CSS
  • TypeScript

npx hoverlab add oss-landing-page

Or over MCP, from your editor's agent — no account needed.

License

Free to read, copy and install, for personal and non-commercial projects. Shipping it in client work or a paid product needs Pro ($79 once). The source lands in your repo and stops being ours — no attribution, nothing to upgrade.

Was this useful?

Preview

ratchet
Install
npm install ratchet
MIT · v2.4.0 · 2.1M downloads a month

Schema migrations that refuse to break production

A migration runner that reads your application code before it drops a column, and blocks itself when something still needs it. Plain SQL, one static binary, no DSL.

ratchet up
Read the docsStar on GitHub

The whole API is one object and two files

A config, and migrations that are plain SQL. If you already know how to write an ALTER TABLE you know how to use this.

  • Migrations are SQL files — nothing to learn, nothing to unlearn
  • The guard is the only unusual concept, and it is four lines
  • Irreversible migrations are declared, not inferred
import { Ratchet } from 'ratchet' // A migration is a file, not a class. The up is required; the down is// optional and, if you leave it out, the migration is declared// irreversible and the tool will say so rather than guess.export const ratchet = new Ratchet({  dir: './migrations',  url: process.env.DATABASE_URL,   // The whole point of the library. Before applying anything that drops  // or narrows a column, parse the queries in these paths and refuse if  // one of them still reads it.  guard: {    scan: ['api/**/*.go', 'reports/**/*.sql'],    onConflict: 'block',  },}) await ratchet.up()

Why this rather than the one you already have

Five differences. The first one is the reason the project exists; the others are consequences of keeping it small.

It reads your code before it drops a column

The guard parses the queries in the paths you name and blocks a destructive migration while anything still reads the column. Most outages caused by a migration are this exact shape.

Plain SQL, no DSL

Your database’s own documentation is the reference. Nothing to learn and nothing that stops working when Postgres adds a feature.

Irreversible is a thing you declare

A migration with no down is fine — lying about it is not. Say so in a comment and the plan output says so too.

No lock held while it thinks

Planning happens before the transaction opens, so a slow guard scan never holds a lock on a production table.

One binary, no runtime

6MB, static, no Node or Python needed in the image that runs it. The library and the CLI are the same code.

18.4k
GitHub stars
And 312 open issues, honestly
2.1M
Downloads a month
npm, last 30 days
184
Contributors
41 with commit access
MIT
Licence
Since 2021, and it will not change

Funding, since you are about to depend on it

Two maintainers are paid part-time; the rest is volunteered

Northwind funds one day a week and Contoso funds two, both on rolling twelve-month agreements, and neither gets any say over the roadmap — that is written into both. If both stopped tomorrow the project would keep going more slowly rather than stopping, because no single contributor holds more than 19% of commits. This paragraph is here because it is the question a team should ask before taking a dependency, and most projects do not answer it.

£61k
Funded in 2025
Two corporate sponsors, 340 individuals
3 days
Paid maintainer time a week
Across two people
19%
Largest share of commits
No single point of failure
0
Sponsor influence on the roadmap
Written into both agreements

The real page, rendered in your current theme — every section below is a live block, not a screenshot.

Built from

All blocks
  1. Responsive NavbarBrand, links and CTAs with a mobile panel that unmounts when closed — so its links are never tabbable while invisible — plus escape-to-close and focus return.
  2. Package Manager Code TabsOne install command behind npm/pnpm/yarn/bun tabs with a working copy button — every reader uses exactly one package manager, so showing all four wastes three lines.
  3. Developer Hero with Install CommandA drawn terminal whose install line is real, selectable text with a working copy button and a feature-detected clipboard call — the hero for anything adopted by typing rather than signing up.
  4. Editor Window ShowcaseA feature section paired with a tabbed fake editor — real selectable code, generated line numbers and a copy button.
  5. Bento Feature GridSix tiles on an asymmetric 4x3 grid with per-tile spans, a hover glow and a mobile collapse that follows source order.
  6. Hairline Stats BandA four-up metrics strip with 1px hairline dividers, built from a single gap-px grid so the rules stay crisp on any display.
  7. Stats Beside the ArgumentFour figures in a hairline card next to the paragraph making the claim, each carrying an optional source line — for numbers that mean nothing without knowing lower than what, over how long, across how many.
  8. Community Link BandA closing CTA of three link cards pointing at GitHub, chat and social — somewhere to go for the visitor who is not ready to convert.
  9. Mega Footer with Link ColumnsBrand column, four labelled nav columns, socials and a legal bar — the one place every page links to every section. Ships no client JavaScript.

Only want one section? Open it and copy that block instead — browse Navigation.

Shipped in these templates

Want the whole project rather than this one screen? A template ships every route, the theme tokens and the layout.

Source

app/oss-landing-page.tsx
/**
 * An open-source project's home page — install first, sell never.
 *
 *   install    the command, in four package managers
 *   terminal   what it does, shown rather than claimed
 *   code       the API, in twenty lines
 *   why        the three things it does differently
 *   adoption   the numbers that stand in for trust here
 *   funding    who pays for it, said plainly
 *   community  where to go next
 *
 * AN OSS PROJECT PAGE IS NOT A MARKETING PAGE AND THE DIFFERENCE IS THE
 * FIRST SCREEN. The visitor is a developer who has arrived from a search or
 * a link, has already decided the category is interesting, and wants two
 * things in this order: the install command, and enough code to judge the
 * API. Everything a SaaS landing page opens with — the value proposition,
 * the social proof, the CTA to book a demo — costs that reader a scroll and
 * buys nothing.
 *
 * SO <CodeTabsPanel> IS THE FIRST BLOCK ON THE PAGE, above the hero. The
 * npm/pnpm/yarn/bun tabs matter because every reader uses exactly one and
 * showing four lines of install command wastes three of them; the block
 * already makes that argument in its own header.
 *
 * FUNDING IS ON THE PAGE, NOT IN A SPONSORS FILE. "Who pays for this and
 * what happens if they stop" is the question that decides whether a team
 * takes a dependency, and a project that will not answer it is one a
 * cautious reader passes over. <StatsNarrative> carries it as a sentence
 * with figures rather than a wall of sponsor logos, which say who gave
 * money but not how much or for how long.
 *
 * NO PRICING BLOCK AND NO "ENTERPRISE" SECTION. Both exist on the sponsor
 * page, and putting either here changes what the project reads as. The one
 * commercial fact on this page is the funding paragraph, which is framed as
 * disclosure rather than as a pitch.
 *
 * Anchors are prefixed `os-`.
 */

import * as React from 'react'
import { NavbarSimple } from '@/components/navbar-simple'
import { CodeTabsPanel } from '@/components/code-tabs-panel'
import { HeroTerminal } from '@/components/hero-terminal'
import { CodeShowcase } from '@/components/code-showcase'
import { BentoFeatures } from '@/components/bento-features'
import { StatsBand } from '@/components/stats-band'
import { StatsNarrative } from '@/components/stats-narrative'
import { CommunityBand } from '@/components/community-band'
import { FooterMega } from '@/components/footer-mega'

const INSTALL = [
  { label: 'npm', code: 'npm install ratchet', language: 'bash' },
  { label: 'pnpm', code: 'pnpm add ratchet', language: 'bash' },
  { label: 'yarn', code: 'yarn add ratchet', language: 'bash' },
  { label: 'bun', code: 'bun add ratchet', language: 'bash' },
]

const RUN_OUTPUT = [
  'ratchet 2.4.0 — schema migrations that refuse to go backwards',
  '',
  '  ✓  0001_initial.sql           applied    2.4s',
  '  ✓  0002_add_ledger.sql        applied    0.8s',
  '  ✓  0003_split_settlement.sql  applied   14.1s',
  '  ⚠  0004_drop_legacy.sql       BLOCKED',
  '',
  '     0004 drops column `orders.legacy_ref`, which 2 queries still read.',
  '     Found in: reports/monthly.sql:41, api/orders.go:212',
  '',
  '     Run with --force to override, or delete the readers first.',
  '',
  '3 applied, 1 blocked, 0 failed — database unchanged for 0004.',
]

const API = [
  {
    name: 'migrate.ts',
    code: `import { Ratchet } from 'ratchet'

// A migration is a file, not a class. The up is required; the down is
// optional and, if you leave it out, the migration is declared
// irreversible and the tool will say so rather than guess.
export const ratchet = new Ratchet({
  dir: './migrations',
  url: process.env.DATABASE_URL,

  // The whole point of the library. Before applying anything that drops
  // or narrows a column, parse the queries in these paths and refuse if
  // one of them still reads it.
  guard: {
    scan: ['api/**/*.go', 'reports/**/*.sql'],
    onConflict: 'block',
  },
})

await ratchet.up()`,
  },
  {
    name: '0004_drop_legacy.sql',
    code: `-- Migrations are plain SQL. No DSL to learn, and your database's own
-- documentation is the reference.
--
-- ratchet:irreversible
--   Says out loud that there is no down. Without this, a migration with
--   no down block is a warning at plan time rather than a surprise at
--   rollback time on a Friday.

ALTER TABLE orders DROP COLUMN legacy_ref;`,
  },
]

const DIFFERENCES = [
  {
    title: 'It reads your code before it drops a column',
    body: 'The guard parses the queries in the paths you name and blocks a destructive migration while anything still reads the column. Most outages caused by a migration are this exact shape.',
    span: 'sm:col-span-2',
  },
  {
    title: 'Plain SQL, no DSL',
    body: 'Your database’s own documentation is the reference. Nothing to learn and nothing that stops working when Postgres adds a feature.',
  },
  {
    title: 'Irreversible is a thing you declare',
    body: 'A migration with no down is fine — lying about it is not. Say so in a comment and the plan output says so too.',
  },
  {
    title: 'No lock held while it thinks',
    body: 'Planning happens before the transaction opens, so a slow guard scan never holds a lock on a production table.',
  },
  {
    title: 'One binary, no runtime',
    body: '6MB, static, no Node or Python needed in the image that runs it. The library and the CLI are the same code.',
    span: 'sm:col-span-2',
  },
]

const ADOPTION = [
  { value: '18.4k', label: 'GitHub stars', caption: 'And 312 open issues, honestly' },
  { value: '2.1M', label: 'Downloads a month', caption: 'npm, last 30 days' },
  { value: '184', label: 'Contributors', caption: '41 with commit access' },
  { value: 'MIT', label: 'Licence', caption: 'Since 2021, and it will not change' },
]

const WHERE = [
  {
    label: 'GitHub',
    description: 'The code, the issues and the RFC process. Every design decision was argued in public and the threads are still there.',
    href: '#',
    meta: '18.4k stars · 312 open issues',
  },
  {
    label: 'Discord',
    description: 'About 4,000 people. Two maintainers are in it daily; nobody is paid to be, so answers are faster on weekdays.',
    href: '#',
    meta: '4,100 members',
  },
  {
    label: 'Documentation',
    description: 'Guides, a full CLI reference and thirteen recipes for migrations that are genuinely hard to get right.',
    href: '#os-docs',
    meta: 'Versioned back to 1.0',
  },
  {
    label: 'Changelog',
    description: 'Every release since 1.0, with the breaking changes called out and a codemod where one was possible.',
    href: '#',
    meta: 'Latest: 2.4.0',
  },
]

export default function OssLandingPage() {
  return (
    <div className="min-h-screen bg-background text-foreground">
      <NavbarSimple
        brand="ratchet"
        links={[
          { label: 'Docs', href: '#os-docs' },
          { label: 'Changelog', href: '#' },
          { label: 'Roadmap', href: '#' },
          { label: 'GitHub', href: '#' },
        ]}
        activeLabel="Docs"
        ctaLabel="Sponsor"
      />

      <main>
        {/* Install command first, above the hero. See the header. */}
        <div id="os-install" className="mx-auto w-full max-w-3xl px-4 pt-12 sm:px-6 lg:px-8">
          <CodeTabsPanel title="Install" tabs={INSTALL} />
        </div>

        <HeroTerminal
          eyebrow="MIT · v2.4.0 · 2.1M downloads a month"
          heading="Schema migrations that refuse to break production"
          subheading="A migration runner that reads your application code before it drops a column, and blocks itself when something still needs it. Plain SQL, one static binary, no DSL."
          command="ratchet up"
          output={RUN_OUTPUT}
          primaryLabel="Read the docs"
          primaryHref="#os-docs"
          secondaryLabel="Star on GitHub"
        />

        <div id="os-api">
          <CodeShowcase
            heading="The whole API is one object and two files"
            subheading="A config, and migrations that are plain SQL. If you already know how to write an ALTER TABLE you know how to use this."
            bullets={[
              'Migrations are SQL files — nothing to learn, nothing to unlearn',
              'The guard is the only unusual concept, and it is four lines',
              'Irreversible migrations are declared, not inferred',
            ]}
            files={API}
          />
        </div>

        <BentoFeatures
          heading="Why this rather than the one you already have"
          subheading="Five differences. The first one is the reason the project exists; the others are consequences of keeping it small."
          tiles={DIFFERENCES}
        />

        <StatsBand stats={ADOPTION} />

        <StatsNarrative
          eyebrow="Funding, since you are about to depend on it"
          heading="Two maintainers are paid part-time; the rest is volunteered"
          body="Northwind funds one day a week and Contoso funds two, both on rolling twelve-month agreements, and neither gets any say over the roadmap — that is written into both. If both stopped tomorrow the project would keep going more slowly rather than stopping, because no single contributor holds more than 19% of commits. This paragraph is here because it is the question a team should ask before taking a dependency, and most projects do not answer it."
          stats={[
            { value: '£61k', label: 'Funded in 2025', source: 'Two corporate sponsors, 340 individuals' },
            { value: '3 days', label: 'Paid maintainer time a week', source: 'Across two people' },
            { value: '19%', label: 'Largest share of commits', source: 'No single point of failure' },
            { value: '0', label: 'Sponsor influence on the roadmap', source: 'Written into both agreements' },
          ]}
          ctaLabel="Sponsor the project"
        />

        <div id="os-docs">
          <CommunityBand
            heading="Where to go next"
            subheading="The documentation is the place to start. The Discord is faster on weekdays, and every design decision is argued in a public RFC."
            links={WHERE}
          />
        </div>
      </main>

      <FooterMega
        brand="ratchet"
        tagline="Schema migrations that refuse to break production. MIT licensed since 2021."
        statusLabel="All systems operational"
        regionNote="Maintained from Lisbon, Berlin and Dunedin"
        columns={[
          {
            heading: 'Docs',
            links: [
              { label: 'Getting started', href: '#os-install' },
              { label: 'The guard', href: '#os-api' },
              { label: 'CLI reference', href: '#' },
              { label: 'Recipes', href: '#' },
            ],
          },
          {
            heading: 'Project',
            links: [
              { label: 'GitHub', href: '#' },
              { label: 'Changelog', href: '#' },
              { label: 'Roadmap', href: '#' },
              { label: 'RFCs', href: '#' },
            ],
          },
          {
            heading: 'Community',
            links: [
              { label: 'Discord', href: '#' },
              { label: 'Contributing', href: '#' },
              { label: 'Code of conduct', href: '#' },
              { label: 'Security policy', href: '#' },
            ],
          },
          {
            heading: 'Support it',
            links: [
              { label: 'Sponsor', href: '#', badge: 'GitHub' },
              { label: 'Corporate funding', href: '#' },
              { label: 'Who funds this', href: '#' },
            ],
          },
        ]}
        legalLinks={[
          { label: 'MIT licence', href: '#' },
          { label: 'Trademark policy', href: '#' },
        ]}
      />
    </div>
  )
}

How to use it

  1. 1. Copy each of the 9 blocks above into components/ — each block page has its own copy button.
  2. 2. Drop this file at app/oss-landing-page.tsx. The imports already point at @/components/…, so they resolve with no edits.
  3. 3. Delete the sections you do not want. Every block takes props, so the copy changes without the layout moving.

For AI

The component, its props, the design tokens it expects and the command that installs it — as one prompt. Paste it into Claude, Cursor, v0 or ChatGPT and what they build around it will match the rest of the catalog instead of inventing its own system.

See the prompt
More Marketing Pages
Open the full page for this page
SaaS Landing Page
A complete marketing page in the order that actually converts — hook, proof, substance, price, objections, exit. Twelve blocks, navbar and footer included.
Marketing Pages12 blocks89 lines
Open the full page for this page
Pricing Page
Plans, a feature matrix and a pricing-specific FAQ written to remove the last purchase objection rather than answer general questions.
Marketing Pages3 blocks94 lines
Open the full page for this page
Waitlist Landing Page
A pre-launch page for a product you cannot buy yet: one email field, scarcity instead of adoption, and no pricing section to be held to later.
Marketing Pages9 blocks206 lines
Open the full page for this page
Developer Tool Landing Page
Install command first, real code before any prose, and a usage calculator instead of tiers — the order a developer actually scans in.
Marketing Pages9 blocks254 lines
Open the full page for this page
Mobile App Landing Page
Store badges above the fold, the App Store rating as the first proof, and a single price — a page with one job, which is the install.
Marketing Pages9 blocks231 lines
Open the full page for this page
Agency Landing Page
A studio site: full-bleed hero, client list, engagements described as engagements, and the actual team — with no pricing, on purpose.
Marketing Pages9 blocks216 lines
Open the full page for this page
Local Service Landing Page
A booking widget above the fold, every price published including the awkward ones, and a footer carrying the registrations a regulated trade must show.
Marketing Pages9 blocks353 lines
Open the full page for this page
Marketplace Landing Page
Two audiences, one page: a search field and real listings for buyers up top, the seller economics below, and a searchable FAQ because they ask different things.
Marketing Pages9 blocks354 lines
Open the full page for this page
Enterprise Landing Page
Built for a champion assembling an internal case: numbers in the hero, a comparison that concedes two rows, video references, and published prices instead of a sales wall.
Marketing Pages10 blocks336 lines
Open the full page for this page
Integration Platform Landing Page
The connector names in the hero, a catalogue with honest live/beta/planned status, four SDK languages, credit pricing, and a dated roadmap for everyone who is not on the list.
Marketing Pages9 blocks377 lines
Open the full page for this page
Creator Course Landing Page
One person selling one course: a student testimonial as the hero because a course cannot demo, a long instructor section, one price and a refund policy on the page.
Marketing Pages10 blocks243 lines
Open the full page for this page
Blog Index
The post grid, a subscribe ask that comes after the proof, and a minimal footer — no hero, because the featured post already is one.
Marketing Pages4 blocks39 lines
Open the full page for this page
Article Page
A single post: header, byline and opening prose in one reading column, with the subscribe form after the article — at the only moment it converts.
Marketing Pages4 blocks39 lines
Open the full page for this page
Careers Page
Team first, openings second, then the questions candidates only ask after an offer — answered while they can still change who applies.
Marketing Pages6 blocks72 lines
Open the full page for this page
Documentation Page
The site navbar over the three-column docs frame. In your project this is one catch-all route — the slug picks the article, the frame never changes.
Marketing Pages2 blocks30 lines
Open the full page for this page
Help Centre
Search first, the six answers that absorb the most contact volume under it, and the ticket form in plain sight rather than behind a modal — a support page measured in tickets not filed.
Marketing Pages7 blocks162 lines
Open the full page for this page
Changelog Page
The release timeline with the site chrome kept on, and the one subscribe form on the site that is not a detour — "tell me when this page changes" is exactly what it promises.
Marketing Pages4 blocks39 lines
Open the full page for this page
Security & Trust
The page a security questionnaire arrives from, written to be forwarded rather than to persuade: certifications early, benchmarks with a denominator, objections in a reviewer’s own words, and a route to a human.
Marketing Pages8 blocks60 lines
Open the full page for this page
Switching & Migration
The landing page for a reader whose current tool already works: the migration mechanism second rather than buried, integrations stated at depth, and deliberately no pricing section.
Marketing Pages8 blocks57 lines
Open the full page for this page
Launch Note
A product announcement shaped as writing rather than a landing page — serif headline, real byline, three pieces of evidence, and an endpoint card that doubles as documentation for the week before the docs exist.
Marketing Pages6 blocks53 lines
Open the full page for this page
Single Offer
One thing, one price, named above the fold — for a course, a consultation or a one-time licence, where there is nothing to compare against and hiding the number answers the only question last.
Marketing Pages7 blocks57 lines
Take 1 of 2
Open the full page for this page
About Page
No hero — a reader who clicked "About" has already read the pitch and is checking whether the company is real, so the page opens with numbers and a timeline instead of a headline.
Marketing Pages7 blocks110 lines
Take 1 of 2
Open the full page for this page
Contact Page
The form first, then the four questions that cause most of the messages — answered here, because that is faster for the sender than a reply and leaves the inbox for what needs a person.
Marketing Pages4 blocks77 lines
Take 1 of 2
Open the full page for this page
Team Page
Who we are, as distinct from who we are hiring: faces, the shape of the company in four numbers, and three working commitments that could actually be falsified.
Marketing Pages6 blocks91 lines
Take 1 of 2
Open the full page for this page
FAQ Page
Search and browse, in that order, because the two halves serve opposite visitors — one arrives from a search engine with a phrase, the other from the navbar with none.
Marketing Pages5 blocks170 lines
Take 1 of 2
Open the full page for this page
Case Study
The numbers above the story, which is the opposite of how these are usually written: the colleague this link gets forwarded to needs the result in the first screen.
Marketing Pages7 blocks116 lines
Take 1 of 2
Open the full page for this page
Case Study Index
Excerpts that lead with the outcome rather than the customer’s biography, filterable by industry — because the reader is scanning for a problem that resembles their own.
Marketing Pages6 blocks134 lines
Take 1 of 2
Open the full page for this page
Services Page
For a business that sells work rather than licences: three engagements named by situation, and prices in a comparison table rather than a pricing card with a monthly toggle that does not apply.
Marketing Pages7 blocks173 lines
Take 1 of 2
Open the full page for this page
Integrations Directory
Every connection with its real status on the card — live, beta or planned — because a directory that hides which is which is discovered at exactly the wrong moment.
Marketing Pages6 blocks153 lines
Take 1 of 2
Open the full page for this page
Integration Detail
One connection, answering the four questions an integration page usually leaves to a support ticket: which records move, which way, how often, and what happens on conflict.
Marketing Pages8 blocks189 lines
Take 1 of 2
Open the full page for this page
Comparison / Alternatives
The competitor-name landing page, with a section naming where each rival is the better buy — which is what makes the other forty rows believable.
Marketing Pages7 blocks143 lines
Take 1 of 2
Open the full page for this page
Public Roadmap
Board plus changelog, because a roadmap alone is a promise — the last three releases underneath are what turn the shipped column into something with dates attached.
Marketing Pages6 blocks143 lines
Take 1 of 2
Open the full page for this page
Webinar / Event
Registration at the top and again at the bottom, with an agenda timed by the minute — so the reader knows what they are getting before handing over an address.
Marketing Pages7 blocks139 lines
Take 1 of 2
Open the full page for this page
Coming Soon
The shortest page in the catalog, and it still says what the product does — including what it will not do at launch. No countdown, because a clock at zero is worse than no clock.
Marketing Pages4 blocks88 lines
Take 1 of 2
Open the full page for this page
Community Page
Member counts and reply times on every door, because "join our community" with no number reads as an invitation into an empty room — plus a digest for people who will not install another chat app.
Marketing Pages7 blocks101 lines
Take 1 of 2
Open the full page for this page
Affiliate Programme
Terms before the application, and a calculator so the reader sees a number rather than doing arithmetic with an ARPU they do not know.
Marketing Pages7 blocks128 lines
Take 1 of 2
Open the full page for this page
Testimonials Wall
Third-party scores first, because they are the only part of the page the company does not control — and the four-star quotes stay in, because a wall of nothing but fives reads as filtered.
Marketing Pages7 blocks174 lines
Take 1 of 2
Open the full page for this page
Gallery / Showcase
A switcher rather than an infinite grid: four named views, one visible at a time, so the page weighs one image on load instead of forty.
Marketing Pages7 blocks111 lines
Take 1 of 2
Open the full page for this page
Portfolio Index
A studio’s list of work, with excerpts that name the outcome and the constraint rather than the aesthetic — a contents page, not a landing page.
Marketing Pages7 blocks144 lines
Open the full page for this page
Developer Portfolio
An engineer’s portfolio that opens on a terminal rather than a gradient, and puts thirty legible lines of real code on the page — because a portfolio that only links to repositories asks the reader to go and judge for themselves, and almost nobody does.
Marketing Pages9 blocks304 lines
Open the full page for this page
Résumé
A personal site whose home page is the CV itself, printable, so the document that decides whether you get a reply is the one that is actually maintained. Four blocks, and the restraint is the design.
Marketing Pages4 blocks91 lines
Open the full page for this page
Crypto Exchange Landing
A regulated exchange’s front door: a moving price rail before a word of copy, custody and reserves above the feature grid, and the risk warning as a section rather than as small print.
Marketing Pages10 blocks307 lines
Open the full page for this page
Markets
The public price screen — sparklines instead of a percentage column, because two assets both up 4% got there differently, and that shape is what a trader is scanning for.
Marketing Pages7 blocks200 lines
Open the full page for this page
Conference Landing
A conference home page built around a deadline: the price step-up above the hero, the programme extract above the speakers, and tickets as a comparison rather than a plan picker.
Marketing Pages10 blocks294 lines
Open the full page for this page
Conference Programme
Both days in full, as two grids rather than a day switcher — because this is the page people print, and a tab hides half of it from find-in-page.
Marketing Pages4 blocks263 lines
Open the full page for this page
Restaurant Landing
Hours, address and phone as a first-class section directly under the hero, then the menu — the two jobs a restaurant site has, in the order visitors actually need them.
Marketing Pages9 blocks236 lines
Open the full page for this page
Menu
The full bill of fare, typeset with leaders and dietary marks, split into food and drink because a diner reads the two differently. No photography, deliberately.
Marketing Pages5 blocks335 lines
Open the full page for this page
Table Reservation
Two booking blocks on purpose: four nights with free-slot counts to answer “is there any point”, then the real grid. The cancellation policy is stated before the button, not in the confirmation email.
Marketing Pages6 blocks183 lines
Open the full page for this page
Property Search
An estate agency home page where search owns the first screen and results are already populated, plus the achieved-against-asking figure most agents will not publish.
Marketing Pages7 blocks183 lines
Open the full page for this page
Property Detail
A product detail page with different stakes: tenure, council tax, EPC and chain position above the prose, and a description that names a flaw so the rest is believed.
Marketing Pages8 blocks214 lines
Open the full page for this page
Job Board
A two-sided marketplace where only one side is reading — candidates get the whole page, employers get one section. Every listing carries a real salary range, which is the entire differentiator.
Marketing Pages8 blocks248 lines
Open the full page for this page
Job Listing
One role, with the four facts a candidate needs before the mission statement and the whole interview process published — stages, hours, and whether the take-home is paid.
Marketing Pages8 blocks229 lines
Open the full page for this page
Newsletter Landing
The archive is the argument, so it sits above the testimonials, and the three worries about handing over an address are answered as content rather than as small print.
Marketing Pages8 blocks268 lines
Open the full page for this page
Directory Index
Faceted by pricing model and hosting rather than by category, because the reader already knows the category. Publishes its own removal rate, which is a claim that can be checked.
Marketing Pages8 blocks333 lines
Open the full page for this page
Directory Listing
One entry, compared against the two obvious alternatives — against the vendor’s interest and exactly in the reader’s. No buy button and no affiliate link, which is what makes the comparison credible.
Marketing Pages9 blocks251 lines
Open the full page for this page
Streaming Service Landing
The catalogue sells itself: rails second, features far down as objection handling, and a real watch screen on the marketing page instead of a device montage.
Marketing Pages8 blocks257 lines
Open the full page for this page
Watch
The one page in the catalog whose job is to get out of the way — player, chapters, a searchable transcript, and no comments section, because a thread is a moderation commitment rather than a component.
Marketing Pages5 blocks182 lines
Take 2 of 2
Open the full page for this page
About Page 02
The founder’s letter instead of the evidence wall: a byline and a dateline, for a company whose best asset is still conviction rather than a six-year record — and it ends on the job board, because /team is linked from job posts more often than from sales decks.
Marketing Pages7 blocks170 lines
Take 2 of 2
Open the full page for this page
Contact Page 02
Route before you write — three doors, each with the form its sender actually needs: a calendar for a buyer, a structured ticket for a broken import. One textarea costs a round trip.
Marketing Pages6 blocks147 lines
Take 2 of 2
Open the full page for this page
Team Page 02
The team page that is really a recruiting page: it opens on the trade rather than the faces, and puts a salary band on every role — a board with three bands and one “competitive” teaches the reader which is the bad one.
Marketing Pages7 blocks154 lines
Take 2 of 2
Open the full page for this page
FAQ Page 02
Objection-ordered and search-free: the questions that lose deals first, hardest at the top, because a search box over eighteen questions implies a list long enough to get lost in — and its empty state reads as “no refund policy”.
Marketing Pages6 blocks215 lines
Take 2 of 2
Open the full page for this page
Case Study 02
The narrative take, for a study found by search rather than forwarded by a champion: the customer’s sentence first, the numbers last, and the six weeks in the middle where the software was losing to a spreadsheet.
Marketing Pages7 blocks153 lines
Take 2 of 2
Open the full page for this page
Case Study Index 02
A results directory rather than a reading list: search the situation, facet by entity count and ledger, and the aggregate claim sits at the bottom underneath the thirty-four rows it was computed from.
Marketing Pages7 blocks205 lines
Take 2 of 2
Open the full page for this page
Services Page 02
One productised engagement with the price in the first screen and no mandatory call — a fixed price behind a scoping call is consulting with extra steps. Includes the paragraph naming when it is the wrong shape.
Marketing Pages8 blocks185 lines
Take 2 of 2
Open the full page for this page
Integrations Index 02
Search-first, with facet counts including the zeroes — nobody browses an integration directory, and “Payroll (0)” answers the question inside the list the reader is already looking at.
Marketing Pages7 blocks193 lines
Take 2 of 2
Open the full page for this page
Integration Detail 02
The setup guide, not the pitch: what moves and which way, then a five-step wizard — written for the person turning the connector on rather than the one deciding to buy it.
Marketing Pages7 blocks309 lines
Take 2 of 2
Open the full page for this page
Alternatives Page 02
One rival, head to head, for a reader who already owns the competitor — so the argument is what a migration costs, and the page opens by telling roughly a third of its readers to stay where they are.
Marketing Pages8 blocks219 lines
Take 2 of 2
Open the full page for this page
Roadmap Page 02
Themes and refusals, no quarters — four problems stated as problems, plus the four things we have decided never to build, which is the section that takes nerve and the one customers actually need.
Marketing Pages7 blocks180 lines
Take 2 of 2
Open the full page for this page
Webinar Page 02
The replay, ungated, for the traffic that arrives months after the event — the gate moves to the transcript and the template, where it is a trade rather than a toll.
Marketing Pages7 blocks192 lines
Take 2 of 2
Open the full page for this page
Coming Soon 02
A referral queue with a real position: three places per invite, forty admitted a week, and the admission ceiling on the page rather than in the confirmation email — otherwise it is a dark pattern with a progress bar.
Marketing Pages5 blocks116 lines
Take 2 of 2
Open the full page for this page
Community Page 02
The calendar is the community: the next session bookable in the first screen, the month underneath, and the chat links demoted to a strip — an idle Slack is a worse first impression than a half-full calendar.
Marketing Pages6 blocks137 lines
Take 2 of 2
Open the full page for this page
Affiliate Page 02
Proof before arithmetic — what four named partners actually earned last quarter, including the one for whom it is not working, and no calculator anywhere. A slider shows what you could earn from numbers you picked yourself.
Marketing Pages7 blocks212 lines
Take 2 of 2
Open the full page for this page
Testimonials Wall 02
Segmented by who is talking rather than sorted by score, because a wall of forty quotes is uniformly impressive and uniformly irrelevant — with the full rating spread underneath, ones included.
Marketing Pages8 blocks229 lines
Take 2 of 2
Open the full page for this page
Gallery Page 02
The whole catalogue at once, filterable, with the total stated up front — the opposite trade to the switcher, and it honestly costs ninety images on load rather than one.
Marketing Pages7 blocks209 lines
Take 2 of 2
Open the full page for this page
Portfolio Index 02
One project per screen, four in total, each naming the constraint it worked around — nobody reads four case studies, and the constraint is the only sentence a competitor cannot copy.
Marketing Pages7 blocks169 lines