feat: link 1MB Club membership in the footer #5

Closed
lytedev wants to merge 1 commit from 1mb-club into master
Owner

lyte.dev is a member of the 1MB Club — sites whose pages weigh under 1 megabyte. This links the membership in the footer as a Meta button, matching the neighboring links (icon + label).

Sanity check: the homepage plus every asset it references (CSS, JS modules, webfont, icon, both avatar variants) currently totals ~126 KB, comfortably inside the club's constraint.

Stacked on #4 (→ #3#2#1) — merge those first and this reduces to one footer <li>.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TKabGxxNaNoocaxN8B4BFG

lyte.dev is a member of the [1MB Club](https://1mb.club/) — sites whose pages weigh under 1 megabyte. This links the membership in the footer as a Meta button, matching the neighboring links (icon + label). Sanity check: the homepage plus every asset it references (CSS, JS modules, webfont, icon, both avatar variants) currently totals ~126 KB, comfortably inside the club's constraint. **Stacked on #4** (→ #3 → #2 → #1) — merge those first and this reduces to one footer `<li>`. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01TKabGxxNaNoocaxN8B4BFG
Replace the catppuccin latte/mocha palettes with ayu light/dark. Exact
values come from the ayu npm package (v8.0.1, the canonical published
palette): https://github.com/ayu-theme/ayu-colors

The catppuccin-named variables (--Rosewater..--Crust) are replaced by
ayu-named ones (--tag, --func, --entity, --string, --keyword, ...);
semantic variables (--bg, --fg, --link-fg, --syntax-*) now reference
those. Chroma token mapping: keywords -> ayu keyword (orange),
names/functions -> func (yellow), strings -> string (green),
literals -> constant (purple), tags -> tag (cyan), comments -> comment,
errors -> error. Links use entity blue (darkened in light mode for
contrast, mirroring the old darkened-sapphire approach); code-block
edges highlight with the ayu accent.

The only users of the old named vars (blockquote bg/border, inline code
fg) now use --panel-bg, --syntax-ledgbq, and --keyword.

Verified with headless Chromium: toggle/persistence still pass, plus
exact-color spot checks for link color and code-block background in
both schemes on a syntax-highlighted post.
The domain is no more; keep the bio text but drop the dead links.
Replaces 'help run a small Christian church' (index + config
description, which mirror each other) and 'a pastor for my small
church where I help run ...' (about) with simpler serving-the-local-
church phrasing.
Adds a self-hosted webring, fully static:

- data/webring.yaml is the ring: an ordered member list (slug, name,
  url) that wraps around
- /webring/<slug>/next and /webring/<slug>/prev are real 302s served
  by Netlify via a generated _redirects file (Hugo custom 'redirects'
  output format on home rendering layouts/index.redirects)
- /webring/ lists members and explains how to join (PR adding an entry
  to data/webring.yaml + embed the nav snippet)
- /webring/random/ picks a random member client-side with a noscript
  fallback list
- the site footer carries the ring navigation, making lyte.dev the
  first member
Per review: no prev/next links in the footer; the webring is a plain
button under Meta like the other links. Ring navigation lives on
/webring/ and via the member-site snippets.
Member listings show plain URLs instead of names (the yaml drops the
name field), and the ring gains two members.
data/webring.yaml is now just an ordered list of member URLs; the
navigation paths derive from each member's hostname
(/webring/<host>/next), so there's no separate slug to invent.
lyte.dev is listed at https://1mb.club/ (sites whose pages weigh under
1 megabyte); the homepage currently totals ~126 KB with all assets.
Shown as a Meta button like the neighboring links.
lytedev closed this pull request 2026-07-07 15:22:38 -05:00

Pull request closed

Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lytedev/site.lyte.dev!5
No description provided.