Landing page prototypes

Three directions for the open-source launch page. Same content, three voices — pick one, or mix and match.

serve locally: npx serve landing  or  python3 -m http.server -d landing

Prototype 01

Goldfinch dark

Brand-forward product page. The gold-on-black mark is the hero; feature cards, jar visual, MCP config block, and a download table. Closest to a classic "product site" — good default if the page is the project's front door.

open → p1-dark/index.html

Prototype 02

Light editorial

Serif headlines on paper, numbered sections, a pull-quote. Reads like a well-kept open-source project's page — calm, credible, docs-adjacent. Good if the audience is "people who read READMEs".

open → p2-light/index.html

$ git clone …/goldfinch.git
$ npm install && npm start
✔ tests ✔ typecheck ✔ lint
→ 30 MCP tools, loopback only

Prototype 03

Terminal / dev-first

Monospace everything, a fake shell session as the hero, key/value spec tables. Unapologetically for developers — the clone-and-run path is the CTA. Good if adoption comes through engineers and agents, not installers.

open → p3-terminal/index.html

All three are single self-contained HTML files (system + Google fonts, no build step).
Download links point at the real v0.10.4 GitHub release assets; GitHub links at github.com/msieurthenardier/goldfinch.