landing: restore product depth (demo, code tabs, breach math, pilot form)#55
Merged
Conversation
… math, pilot form PR #54 (the editorial pass) collapsed too much content. This brings back every section that existed on the prior landing while keeping the new type system (Fraunces + Inter Tight + JetBrains Mono) and monochrome palette. The page now reads as an auth-system landing, not a magazine. What returned - Live demo iframe (/demo.html) right after the hero - Quickstart with three code tabs (curl / Node.js / Python) + copy button - How it works as three side-by-side cards each with a mini-code snippet - Developer features grid (6 cards: REST&SDKs, Live+test keys, Audit log, Devices&attestation, <100ms verify, Open source) - Breach comparison (Okta Oct-2023 vs ZeroAuth, with the line items and $25M+ vs $0 totals) - Enterprise pilot form posting to /api/leads/pilot with a success state - Whitepaper section retained as the only place that names Pramaan (no trademark mark per the brand directive) Tightening - Hero padding clamped down; numbers folded into the hero as an inline stats row instead of a standalone section - Section vertical rhythm tightened from 96-168 to 80-128 — denser, less whitespace-as-status - Code tabs + copy button wired with vanilla JS Fix - Feature card icons were rendering full-size because the .feature-icon span was inline; switched to display:block with an explicit 26px box.
There was a problem hiding this comment.
Pull request overview
Restores the landing page into a fuller product-oriented auth-system page with demo, quickstart snippets, product feature messaging, breach comparison, enterprise lead capture, engineering links, and white paper CTA.
Changes:
- Adds live demo iframe, quickstart code tabs with copy behavior, feature cards, and “how it works” cards.
- Adds breach comparison and enterprise pilot form posting to
/api/leads/pilot. - Keeps the editorial typography/monochrome styling while expanding landing content.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+1500
to
+1504
| var data = { | ||
| name: form.name.value.trim(), | ||
| company: form.company.value.trim(), | ||
| email: form.email.value.trim(), | ||
| size: form.size.value |
Comment on lines
+995
to
+1001
| curl <span class="c-kw">-X</span> POST <span class="c-str">https://zeroauth.dev/v1/users/register</span> \ | ||
| <span class="c-kw">-H</span> <span class="c-str">"Authorization: Bearer $ZEROAUTH_API_KEY"</span> \ | ||
| <span class="c-kw">-H</span> <span class="c-str">"Content-Type: application/json"</span> \ | ||
| <span class="c-kw">-d</span> <span class="c-str">'{ | ||
| "external_id": "user_42", | ||
| "commitment": "0x1f3c…" | ||
| }'</span> |
Comment on lines
+1003
to
+1011
| <span class="c-cmt"># 2. Verify a Groth16 proof at login</span> | ||
| curl <span class="c-kw">-X</span> POST <span class="c-str">https://zeroauth.dev/v1/verifications</span> \ | ||
| <span class="c-kw">-H</span> <span class="c-str">"Authorization: Bearer $ZEROAUTH_API_KEY"</span> \ | ||
| <span class="c-kw">-H</span> <span class="c-str">"Content-Type: application/json"</span> \ | ||
| <span class="c-kw">-d</span> <span class="c-str">'{ | ||
| "external_id": "user_42", | ||
| "proof": { "a": [...], "b": [...], "c": [...] }, | ||
| "public_signals": ["0x1f3c…"] | ||
| }'</span></pre> |
Comment on lines
+986
to
+990
| <div class="code-tabs" role="tablist"> | ||
| <button class="code-tab active" type="button" role="tab" data-tab="curl">curl</button> | ||
| <button class="code-tab" type="button" role="tab" data-tab="node">Node.js</button> | ||
| <button class="code-tab" type="button" role="tab" data-tab="python">Python</button> | ||
| <button class="code-copy" type="button" data-copy="curl">Copy</button> |
Comment on lines
+1015
to
+1032
| <pre><span class="c-kw">import</span> { ZeroAuth } <span class="c-kw">from</span> <span class="c-str">'@zeroauth/sdk'</span>; | ||
|
|
||
| <span class="c-kw">const</span> za = <span class="c-kw">new</span> <span class="c-fn">ZeroAuth</span>({ apiKey: process.env.ZEROAUTH_API_KEY }); | ||
|
|
||
| <span class="c-cmt">// 1. Register a user from your backend</span> | ||
| <span class="c-kw">await</span> za.users.<span class="c-fn">register</span>({ | ||
| externalId: <span class="c-str">'user_42'</span>, | ||
| commitment, <span class="c-cmt">// from client SDK</span> | ||
| }); | ||
|
|
||
| <span class="c-cmt">// 2. Verify a proof on login</span> | ||
| <span class="c-kw">const</span> { verified, principal } = <span class="c-kw">await</span> za.verifications.<span class="c-fn">create</span>({ | ||
| externalId: <span class="c-str">'user_42'</span>, | ||
| proof, | ||
| publicSignals, | ||
| }); | ||
|
|
||
| <span class="c-kw">if</span> (verified) issueSession(principal);</pre> |
Comment on lines
+1518
to
+1520
| } catch (err) { | ||
| btn.disabled = false; | ||
| btn.textContent = 'Try again'; |
| "public_signals": ["0x1f3c…"] | ||
| }'</span> | ||
| <h3>REST & SDKs</h3> | ||
| <p>A typed REST API with first-party SDKs for Node and Python. Predictable error codes and idempotent writes.</p> |
| <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"><path d="M14 2H6a2 2 0 0 0-2 2v16a2 2 0 0 0 2 2h12a2 2 0 0 0 2-2V8z"/><polyline points="14 2 14 8 20 8"/><line x1="16" y1="13" x2="8" y2="13"/><line x1="16" y1="17" x2="8" y2="17"/></svg> | ||
| </span> | ||
| <h3>Audit log</h3> | ||
| <p>Every signup, verification, key rotation, and device event — searchable, exportable, and tamper-evident.</p> |
| </div> | ||
| <div class="pillar"> | ||
| <dt class="pillar-key">Audit</dt> | ||
| <dd class="pillar-val">Append-only event log · Hash-chained<small>Every write produces a verifiable row. Chain integrity is checkable from any commit.</small></dd> |
Comment on lines
+1069
to
+1072
| <p class="lede"> | ||
| The user proves they hold a biometric on their device. Only a Poseidon | ||
| commitment and a Groth16 proof ever cross the network. Raw embeddings | ||
| stay in memory and are destroyed after hashing. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PR #54 (the editorial pass) collapsed too much. This brings back every section that existed on the prior landing while keeping the new type system (Fraunces + Inter Tight + JetBrains Mono) and monochrome palette. The page now reads as an auth-system landing, not a magazine.
What returned
Test plan