feather-landing

Landing page and privacy policy for Feather, a Chrome extension that converts documents into Markdown entirely in the browser.

Two pages plus an error page, no build step, no dependencies:

File	Purpose
index.html	Landing page
privacy.html	Privacy policy. This is the URL to put in the Chrome Web Store's Privacy Practices tab.
404.html	Error page. Served automatically by GitHub Pages and Vercel. Uses root-absolute paths, because it is served at whatever address the visitor mistyped.
styles.css	The whole design system, both palettes
theme-boot.js	Sets the theme attribute before first paint. Classic script in <head> on purpose.
theme.js	Theme switch (Auto / Light / Dark) and the scroll-reveal animation
assets/icon.svg	The product icon exactly as it ships in the extension
assets/logo.svg	Monochrome silhouette of the same feather, used for the mark and the drifting feathers
assets/hero-eagle-light.webp	Hero artwork, light theme
assets/hero-eagle-dark.webp	Hero artwork, dark theme
assets/og.png	Share card, 1200x630, referenced by og:image on both pages
assets/favicon.svg	Favicon

Internal links name the file, extension included: privacy.html, not /privacy. An extensionless URL is a host rewrite rather than a file, so linking to one breaks on a plain file server, on a local copy, and on any host that does not rewrite. vercel.json redirects /privacy and /privacy-policy to the file so any address already published keeps working.

Distribution note: the extension repository is private, so nothing here links to it. The Chrome Web Store is the main channel: https://chromewebstore.google.com/detail/hohblnepjgeffeoojlogfhopfmplebbn

Run it

There is nothing to install. Open index.html in a browser, or serve the folder if you want correct relative URLs:

python -m http.server 8080
# then open http://localhost:8080

Design

The system is editorial precision: a serif display face, a grotesque for body copy, monospace reserved for data and metadata, hairline rules, soft low elevation, and generous whitespace. The reference point is a well-set journal or annual report rather than a SaaS template.

The serif is the deliberate point of difference. Surveys of SaaS typography put sans-serif usage above 90%, so a serif display face is the cheapest way to look unlike the category while still reading as serious, and it suits a product about documents.

Two constraints are deliberate and worth keeping:

• No CSS framework. The page is smaller than any framework it could use.
• No web fonts. A product whose entire pitch is that it does not upload your documents should not make a third-party font request on its own marketing page. System stacks only, which also means no render blocking and no layout shift.

All colour lives in two palette blocks at the top of styles.css, one per theme. No rule hardcodes a colour, including shadows.

Checks

Two scripts, no dependencies, run them before pushing:

node verify.mjs          # links, anchors, dead CSS, sitemap agreement, a11y basics, conventions
node verify-policy.mjs   # privacy.html vs the extension's actual code

verify.mjs covers all three pages. Beyond the obvious, it checks both directions of the class contract (no class without a rule, no rule without a class), that fragment links into another page hit an id that exists there, that every sitemap URL resolves to a file and is some page's canonical, and that the error page is noindex with no canonical of its own.

verify-policy.mjs is the important one. The privacy policy is a legal declaration and it is the URL the Chrome Web Store listing points at, so it drifting out of sync with the code is a compliance problem rather than a rendering one. It checks that every analytics event the extension can send is documented, that no event is documented that the code never sends, that the event properties match, that the permissions the policy claims are unused are genuinely absent from the manifest, and that the analytics host named in the policy is the one the code posts to. It expects the extension repository as a sibling directory and skips cleanly if it is not there.

Deploying

Static hosting, anywhere. For GitHub Pages, enable Pages on the main branch at the repository root. .nojekyll is present so files are served as-is. Both GitHub Pages and Vercel serve 404.html for an unknown path with no configuration.

vercel.json sets cleanUrls: false on purpose. With it on, Vercel serves privacy.html at /privacy and redirects the .html path away, which makes the deployed URLs disagree with the files in the repository and with a local copy. Redirects cover the extensionless addresses instead.

The privacy policy must stay reachable at a stable URL, because the Chrome Web Store listing points at it. Do not rename privacy.html without updating the store listing.

google2b6793271aeeeccc.html is the Google Search Console verification file for feather.quilonix.in. It is 54 bytes of plain text whose contents name the file itself, so it cannot be renamed, edited, or disallowed in robots.txt. Search Console refetches it and verification lapses if it stops resolving. A DNS TXT record on quilonix.in would cover every subdomain at once and is worth adding alongside it.

Accuracy

Every number and claim on these pages reflects what the extension actually does, and several are deliberately unflattering (see the footnotes on token savings and the "what it does not do" section). If the extension changes, these pages change with it. Specifically:

• the supported site count and the site ticker
• the format table
• the batch and file size limits
• the analytics event table in the privacy policy, which must match src/analytics.js in the extension repo exactly