Skip to content

Landing revamp: market the wedge — M2M auth leads, supply chain proves#19

Open
bordumb wants to merge 2 commits into
mainfrom
gtm-landing-revamp
Open

Landing revamp: market the wedge — M2M auth leads, supply chain proves#19
bordumb wants to merge 2 commits into
mainfrom
gtm-landing-revamp

Conversation

@bordumb

@bordumb bordumb commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Restructures the landing page around the four use cases in priority order, per the positioning brief: don't market the platform, market the wedge.

Preview: https://auths-website-bi9py2b3a-bordumbs-projects.vercel.app

New page flow

  1. Hero — M2M / kill the API key. "Replace static API keys with signed, scoped, revocable identity." Animated terminal acts out the signed-request flow: mint challenge → auths auth challengeAuthorization: Auths-Presentation → verified principal.
  2. Authenticate Without Tokens (#auth) — the dormant LandingAuth section revived with the real shipped API: @auths-dev/express middleware (challengeHandler, authsAuth, capability enforcement, 401-replay/403-cap semantics), static-key contrast callout, blog link.
  3. Give Every Agent an Identity You Can Revoke (#agents) — attribution per DID, capabilities fixed at issuance and enforced at the gate, auths device remove as the revocation money shot, MCP mention.
  4. Prove Who Did What. Cut Access in Seconds. (#governance, new) — org lifecycle terminal with the real off-boarding output (KEL seq, lost caps), auths audit --require-all-signed CI gate, offline evidence bundles; absorbs the multidevice/rotation content.
  5. Prove Where Code Comes From (#supply-chain) — now the consolidated proof demo: sign/verify pair, the interactive offline verifier ("don't take our word for it"), CI actions, and the opt-in Sigstore strip.
  6. Comparison table with a fair-comparison intro ("including where the alternatives win") → architecture (agent tab promoted) → CTA with the install terminal.

Honesty notes

  • No "scoped at verification" claims — copy says scoped at issuance, enforced at the gate
  • Express-only middleware shown, no framework-breadth claims
  • Sigstore stays opt-in ("one flag"); registry claims untouched (still coming-soon)
  • Every CLI string verified against the v0.1.2 tree (org flags lifted from org.rs canonical examples); scripts/check-cli-drift.sh green

Voice is restrained-technical per owner decision. Build + typecheck green. 16 files → 2 files changed (page.tsx + landing-sections.tsx); net −15 lines.

Not merging — owner reviews the preview first.

🤖 Generated with Claude Code

New section order: M2M kill-the-API-key (lead) -> agent identity ->
org governance -> supply-chain proof demo -> honest comparison.

- Hero: "Replace static API keys with signed, scoped, revocable identity"
  with an animated signed-request terminal (challenge -> device-key sign ->
  Auths-Presentation header) replacing the install terminal
- Revived the dormant LandingAuth as LandingMachineAuth: real
  @auths-dev/express middleware code (challengeHandler + authsAuth +
  capability enforcement), 4-step presentation flow, static-key contrast,
  link to the replacing-api-keys post
- Agents: "Give Every Agent an Identity You Can Revoke" — attribution +
  issuance-scoped capabilities + `auths device remove` revocation as the
  money shot; MCP server mention
- New LandingGovernance: org lifecycle terminal (create/add-member/
  revoke-member/offboarding-log, audit --require-all-signed), compliance
  voice; absorbs the multidevice/rotation blocks
- Supply chain consolidates Sign&Verify + CI actions + Sigstore strip
  around the interactive offline verifier; Sigstore stays opt-in-truthful
- Comparison table gains a fair-comparison intro; agent tab promoted in
  architecture; CTA gains the install terminal; footer links the four
  use-case anchors
- Deleted the absorbed standalone sections (LandingInstall,
  LandingSignAndVerify, LandingCiIntegration, LandingMultidevice)

All commands verified against the v0.1.2 tree (org flags lifted from
org.rs canonical examples); drift check, typecheck, build green.
@vercel

vercel Bot commented Jun 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
auths-website Ready Ready Preview, Comment Jun 10, 2026 3:02am

Full visual redesign of the landing page on owner feedback that the dark
zinc/emerald template felt cluttered and generic:

- New aesthetic: bone-paper background, ink text, Fraunces display
  headlines, one seal-orange accent (section marks, primary CTA,
  verification ticks). Mono is reserved for code, terminals, and labels.
- Terminals/code panes are the only dark objects on the page — they read
  like photographs tipped into a document. New InkTerminal primitive,
  no traffic-light chrome, no nested borders.
- Ruthless cuts: one artifact per section; numbered sections 01-04
  (machine auth / agents / governance / supply chain); architecture tabs,
  Edge/CloudTopology/DelegationChain diagrams, CI snippet cards, and the
  multidevice blocks are gone from the landing.
- Comparison collapses to a 4-row hairline strip; the full honest table
  (now including an "ecosystem adoption: Sigstore wins" row) moves to a
  new /compare page, linked from nav and footer.
- SiteNav gains a light tone variant on / and /compare; dark pages keep
  the existing chrome. landing-sections.tsx shrinks to the dark footer
  the /network page still uses; page.tsx.backup deleted.

All CLI strings carried over verbatim from the verified set; drift check,
typecheck, build green.
@bordumb

bordumb commented Jun 10, 2026

Copy link
Copy Markdown
Contributor Author

Superseding update: full visual redesign per owner feedback — The Ledger (light editorial: paper/ink/Fraunces, one seal accent, one artifact per section, terminals as the only dark objects). Full comparison moved to a new /compare page. New preview: https://auths-website-hdxkg8v2e-bordumbs-projects.vercel.app

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant