docs: make the two remaining landing-page headers claims - #1396
Merged
Conversation
"Real HTML first. JavaScript only when it earns it." was two claims where every other header is one, and it duplicated the opening of the bento's progressive-enhancement card word for word. "Modern full-stack, on web standards" was a label for the contents rather than a claim about them, which left it the only header out of step once the ledes started arguing. The headers now read as one chain: the page arrives finished, nothing is compiled away, you give up nothing to stay on the platform. Each stands on its own, which is the rule the comment above STATS now records, along with the two ways of breaking it that this page has already tried. The consequence link stays in the bento lede's first sentence, where there is room to name what it refers back to. As a header it could only point at a decision the reader has no way to resolve.
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.
Finishes the narrative spine from #1393. Two headers were still out of step with the ledes that now argue underneath them.
Real HTML first.also opened the bento's progressive-enhancement card verbatim. Dropping it from the header resolves that duplication, so the card needs no edit.Reading down the page the headers are now one chain: the page arrives finished, nothing is compiled away, you give up nothing to stay on the platform, light enough for AI, start where you are.
No lede changed. An earlier draft promoted the bento lede's opening sentence ("Everything below falls out of that one decision") into the header, and it failed review for a good reason: as a header it points at a decision the reader has no way to resolve from the header alone. That consequence link belongs in prose, where there is room to name what it refers back to. The comment above
STATSnow records the header rule plus both ways this page has already broken it.Nothing outside
page.tsreferenced either heading.Verified:
npm run typecheckclean,webjs checkclean,webjs test --server471/471, read end to end locally.