feat(website): For teams becomes the briefing block - #1081
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
blove
force-pushed
the
blove/teams-briefing
branch
from
September 9, 2026 02:17
4731953 to
bc4fa01
Compare
Contributor
blove
force-pushed
the
blove/teams-briefing
branch
from
September 9, 2026 02:40
bc4fa01 to
d908ab7
Compare
Contributor
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
readFileSync anchors to the repo root, not the vitest root, and jsdom makes import.meta.url an http: URL. Both simpler forms throw. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Two defects I put in the plan, both caught in review. .field-report-num painted the 01-06 chapter markers in --color-signal at 10px bold. That is 1.78:1 on the surface it sits on; the ATC theme split the accent role precisely so this yellow stays fill-only. --color-accent is the interactive ink at 14.86:1. .pilot-eyebrow was kept on a false premise: I matched it as a substring of .pilot-eyebrow-spaced / -tight, which /pilot-to-prod does use -- but those are defined in pages.css. The bare class had no consumer left. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Centring made the form's position depend on the cover's height: the cover is 477px against a 390px ask column, so the primary action was pushed down 43px, and would move again if the document gained a chapter. Measured 393px -> 350px from the section top (it was 618px before this redesign). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
blove
force-pushed
the
blove/teams-briefing
branch
from
September 9, 2026 03:00
d908ab7 to
9751070
Compare
Contributor
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
1 participant
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
The homepage's "For teams" section had its primary goal buried and described the document it offers incorrectly. Both are fixed.
The section inverted its own goals. Measured on the live page at 1440px: 916px tall, with the field-report form — the primary conversion goal — at y=618, two-thirds down. "Talk to an engineer" was a large amber button within 3% of the form's submit in visual weight, so nothing told a reader which ask mattered. The top of the aside held a four-step pilot timeline that
/pilot-to-prodalready covers in full, with week numbers.Now: the ask leads, beside a preview of the actual document; contact is a link beneath a rule.
The copy was wrong, and now it cannot drift
Checked against the shipped
apps/website/public/whitepaper.pdf:pdfinfoand a page-object count agreeerror boundar,fallback,observabThree of the four topics we named in exchange for an email address appear nowhere in what we send. The six chapters are Streaming State Management, Thread Persistence, Tool-Call Rendering, Human Approval Flows, Generative UI, and Deterministic Testing — and the briefing preview now renders that real table of contents, so the claim and the artifact are the same object.
FIELD_REPORTholds these facts, and a test counts/Type /Pageobjects in the PDF itself and asserts the declared count matches — dependency-free, and mutation-verified failing withexpected 18 to be 17. Regenerating the document at a different length now fails the suite instead of silently making the page lie.WhitePaperBlock, used by the four library pages, repeated both errors and is corrected too.Notes
<h2>id changespilot-heading→field-report-heading, ande2e/website.spec.ts:57changes with it. That is the only test edit in this change — the spine catches accidental removals, and a rename landing beside its own test is not that.aria-hidden, unlike the decorative.wp-cover-wrapit borrows.wp-paperfrom: it carries the table of contents, which is the reason to download. The drawn01–06markers are hidden, since the<ol>already numbers the list.home_whitepaper,teams-block,hero_talk_to_engineers.WhitePaperBlock's "No vendor pitch — what we learned shipping it" is left alone deliberately (spec §9): the document was script-generated, which makes the line hard to defend, but choosing between new copy and a new document is not a copy edit.Test Plan
npx nx test website— greennpx nx lint website— 0 errorsnpx nx build website— greennx e2efails identically onorigin/mainwith a different pair of docs-pagepage.gototimeouts each run; local load, not this change)#proof-heading'sSpec:
docs/superpowers/specs/2026-09-08-teams-briefing-design.mdPlan:
docs/superpowers/plans/2026-09-08-teams-briefing.md🤖 Generated with Claude Code