site: lead the homepage with the artifact, not the abstraction - #1086
Merged
Conversation
The most common response to this project is 'I don't fully understand it.' The homepage was a good part of the reason. The hero spent 227 words before anything moved, and asked the reader to hold six unfamiliar concepts first. 'A readable behavior layer for host objects' appeared in the kicker, the page title, the meta description and the opening sentence — the same abstraction four times, all before any evidence. It also ran two pitches at once: what the engine does, and which platforms it runs on. Portability is a good second question and a terrible first one; nobody asks whether a thing runs on Android before they can picture it. The standfirst is now two sentences a reader can check against the page they are looking at, the strongest being 'nothing on this page is animated'. That is the sentence that turns a CSS-transition assumption into a question. Kicker and title become 'a physics engine for interfaces' — a category people already have a slot for, where 'behavior layer for host objects' is one they have to be taught before anything else lands. Adds a #shipped section: Habitat on WebGL, Ascent on iOS and the App Store, zachshallbetter.com on vanilla, and the native parity matrix. Four doors into one core. The renderer-agnostic claim was previously prose; it is now four links that open. Cross-plane parity moves into the hero meta. Six forces reproducing identical output across JavaScript, Swift and Kotlin, verified on every commit, is the least common thing this project can claim — and the word 'parity' appeared exactly once on the page. The maturity line said 'no external users yet' while a published iOS app and a live WebGL game were running on it. Corrected to 'shipping in production apps, no third-party adopters yet': truer, and stronger. typecheck, build, check:api, check:docs and check:links all clean; hero and #shipped verified rendering in a browser.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Why
The most common response this project gets is "I don't fully understand it." The homepage was a good part of the reason.
What changed
Standfirst → two checkable sentences. The strongest is "Nothing on this page is animated." That's the line that converts a CSS-transition assumption into a question.
Kicker + title → "a physics engine for interfaces." A category people already have a slot for.
New
#shippedsection — four doors, one core:@fundamental-engine/three<field-root>+ elements · App Store@fundamental-engine/vanillaThe renderer-agnostic claim was prose. It's now four links that open.
Parity in the hero meta. Six forces, identical output across three planes, checked in CI — the least common thing this project can claim, and the word "parity" appeared once on the whole page.
Maturity line corrected. It read "no external users yet" while a published iOS app and a live WebGL game ran on it.
Verified
All four live URLs return 200;
habitat.fundamental-engine.comserves a byte-identical build to the Vercel origin. Hero and#shippedconfirmed rendering in a browser (computed styles checked — a black screenshot frame turned out to be a capture artifact, not a paint bug).typecheck · build ·
check:api·check:docs·check:links— all clean.