Repository navigation
Add six copy and paste sections in plain HTML and CSS - #430
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Oct 3, 2026
This branch was successfully deployed
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.
First half of #410. Six sections you can copy into any page: hero, feature grid, pricing, questions, email signup and footer. The page that shows them and the copy button are #411; this is the set itself, defined once so what somebody reads and what they paste cannot drift.
Plain HTML and CSS. No React, no Tailwind, no bundler, no script tag, and nothing fetched from anywhere, so a block pastes into a WordPress template, a PHP file or a folder of static files and works offline. Every library in the research ships React plus a motion library, and the ones that serve everyone else ship markup with no behaviour.
Colours and spacing come from
--sck-*custom properties with their own fallbacks, so a pasted block inherits the host page's palette where there is one and still looks finished where there is not. Every rule is rooted at.sck, so nothing it is pasted into gets restyled; a test fails if a selector escapes that.No testimonial component. It is the one section whose sample content would be a made-up endorsement, and a kit that hands people a fake quote to ship is worse than one section short. Questions took its place.
Copy is written for one fictional bookkeeping business, specific enough that it could not be find-and-replaced onto another: 340 independent cafes, a company number, a named export format. Tests ban the filler vocabulary and the chrome that makes a page look mass produced: tracked-out capitals above every heading, an arrow glued to button text, numbered markers on things that are not a sequence.
Three things the browser found that the tests could not:
display: flexon a summary removes the disclosure triangle, which is the only thing telling anyone the answer is in there. It isdisplay: list-itemnow, with a test.Verified by rendering the whole set and driving it: six sections at 1440 and 390, nothing overflowing, no sideways scroll, no console errors; a question opens by mouse click and by Enter with the summary focused, and the answer is visible; the focus ring is a 3px solid outline. Contrast measured across every text role, lowest 5.67:1 on the primary button and 5.76:1 in the signup field, with headings at 17.62:1 and body text at 10.78:1.
Reverting the selector scoping or adding filler copy each fails its own test. tsc and eslint clean, vitest 699 of 699.