Skip to content

Add a landing page - #30

Open
mberrishdev wants to merge 1 commit into
mainfrom
site/landing-page
Open

mberrishdev wants to merge 1 commit into
mainfrom
site/landing-page

Conversation

@mberrishdev

Copy link
Copy Markdown
Owner

A landing page in site/ — three files, no build step, no dependencies. Open site/index.html or serve the folder; it is ready for GitHub Pages as it stands.

The hero is the product, not a picture of it

app.js carries the same canonicalPath and transformFor the app draws with, so the page renders the real notch geometry — concave flares included. The Top / Right / Bottom / Left buttons re-dock it for real, and Open it swaps the handle for the panel.

Docking to any edge is the one thing no comparable app does, and demonstrating it beats claiming it. It is only possible because Notchly is HTML.

Choices worth disagreeing with

Light, not dark. Dev-tool pages default to near-black, and a dark page would have swallowed a dark panel. The ground is a cool grey so the app's own #0B0C0F reads as an object sitting on it, with the real --caution / --good tones on the arcs.

Familjen Grotesk and Instrument Sans, neither of them the usual reach for this kind of page.

One classic script, not ES modules. A landing page has to work when someone double-clicks the file, and browsers refuse module imports over file://. The first version was modules and failed exactly that way — blocked script, no handlers, empty display. Verified over both file:// and HTTP now.

Star count

The masthead button fetches stargazers_count and shows it only when GitHub answers with a number above zero. Offline, rate-limited, or no stars yet all leave it reading "Star", which is the call to action anyway — a button reading Star │ 0 argues against itself, and one reading Star │ looks broken. The fetch is fire-and-forget; nothing on the page waits on it.

One thing to keep in mind

The path maths is a copy of ui/lib/notch-shape.js, not an import, so the folder deploys standalone. If the shape changes there it has to change here — there is a comment saying so.

One folder, three files, no build step and no dependencies. Open
site/index.html or serve the folder; it is ready for Pages as it stands.

The hero is not a screenshot. app.js carries the same canonicalPath and
transformFor the app draws with, so the page renders the real notch
geometry — and the edge buttons re-dock it for real, which is the one
thing no comparable app does and the only honest way to show it.

Light rather than dark on purpose: a dark page would swallow a dark
panel, so the ground is a cool grey and the app's own #0B0C0F reads as an
object sitting on it, with the real tone colours on the arcs.

Written as one classic script rather than ES modules. A landing page has
to work when someone double-clicks the file, and browsers refuse module
imports over file:// — which is exactly how the first version failed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018W5NcWEVVk1nPGsj2tD5P4
@mberrishdev mberrishdev mentioned this pull request Sep 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant