Add typeset landing page under site/#15
Open
karanb192 wants to merge 1 commit into
Open
Conversation
Single-file static landing page styled as a technical journal — cream paper, ink black, vermillion accent. Catalogs the five hooks with lifecycle diagram, apparatus, marginalia, and an index of forthcoming hooks. Untracked so far; ready to wire up to GitHub Pages later.
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
site/index.html(1,279 lines, ~47 KB, no build step, no dependencies beyond Google Fonts)§01–§05) with input → verdict vignettes, plus a lifecycle diagram, three-step apparatus, marginalia (safety / runtime / exits), an index of forthcoming hooks, and a colophonWhy now
Landing it on a branch so we can come back later to iterate on copy, deploy choice (Pages vs. subdomain vs. Vercel), and link-back from the README + blog post. Nothing in the existing repo references it yet — fully additive.
Test plan
site/index.htmldirectly in a browser — hero reveal, custom cursor, lifecycle dots, hover states all behaveprefers-reduced-motion(animations should collapse)