Skip to content

feat(site): redesign the landing page around Srcly's own treemap - #391

Merged
byronwall merged 2 commits into
mainfrom
claude/landing-site-f6a5a4
Nov 20, 2026
Merged

byronwall merged 2 commits into
mainfrom
claude/landing-site-f6a5a4

Conversation

@byronwall

@byronwall byronwall commented Nov 20, 2026 •

Copy link
Copy Markdown
Owner

The Srcly site at byronwall.github.io/srcly now looks like Srcly. The landing page is drawn as a scan of Srcly's own source, and it is a one-page user guide: install, how to read the treemap, every view, workflows, the command line, a reference generated from the metric catalog, and a short "How I built it". A GitHub Actions workflow now deploys the site, so the hand-run gh-pages push goes away.

What you'll see

  • Hero: a real treemap of Srcly's repository at e4485453 (1,136 files), colored with the app's own attention ramp, with the headline cut into it. It is HTML tiles laid out at build time from site/src/data/tree.json, not an image.
  • Scope sections: each section is a treemap folder with a mono strip (start/, views/, cli/ …). The strip names the part of Srcly that implements the section, with its real LOC and max CCN, linked to GitHub. No number on the page is typed by hand.
  • Guide (about 60%): install and first run, how to read area, color, hatching and rollups, a tile for each of the 8 views with a fresh screenshot, and 5 workflows (find the refactor, review a PR, give an agent a map, ratchet file size, clean up exports).
  • Reference (about 30%): a CLI table plus real hotspots and explain output, all 35 metrics with rollup, languages and definition (from /api/metrics/catalog), languages and analyzers, findings checkers, srcly.toml, .srcly/rules and env vars.
  • How I built it (about 10%): short, first person, with an architecture diagram and links to the byroni.us project page and its three posts. Every claim comes from that page, its posts, or docs/CODE_MAP.md.
  • Dark mode follows the OS: ink background, same heat ramp.
  • The docs pages keep their URLs and content and take on the new theme. Their screenshot captions now match the new captures.

Style choice. I asked Codex for three mockups grounded in the old page and a real treemap. I built "scope map" in light and used the "thermal" mockup for dark. The third mockup stayed too close to the old page. Both take their tokens from the app's DESIGN.md and TREEMAP_RAMP, sampled with the app's Lab interpolation, so tiles match the app.

Proof

Before, 1440px:

Old landing page

After, 1440px. The hero is Srcly's own source:

New hero at 1440px

Dark mode:

New hero in dark mode

390px phone: the map moves above the headline. Scroll width is 390, so nothing scrolls sideways:

Phone at 390px

How to read the treemap, with a real client/src map beside the definitions:

read section

The views. All 8 screenshots come from site/scripts/capture.mjs:

views section

Command line, with real output from Srcly scanning itself:

cli section

Reference tables generated from the metric catalog:

reference section

How I built it, light and dark:

built section
built section, dark

A docs page in the new theme:

docs metrics page

Checks on this branch:

$ cd site && pnpm build
Prerendered 12 pages, docs entry point, and 404 page.
$ pnpm test
  6 passed (6.6s)

The new test checks that the landing page renders as static HTML with more than 200 treemap tiles and all 7 sections, and that every image, local link and #anchor resolves. All 10 external links (byroni.us page and posts, PyPI, uv, GitHub paths) returned 200.

Deploy: what changes, and your steps

Today gh-pages holds a hand-deployed build of this same Vite site (site/scripts/deploy.mjs, three "Deploy site" commits on 2026-11-06): /, /docs/<slug>/ for 11 guides, /screenshots/*.jpg, 404.html, robots.txt, sitemap.xml. The new build serves every one of those paths, .nojekyll included, so no link breaks. This PR deletes deploy.mjs and DEPLOY.md.

After merge:

  1. Open Settings › Pages in byronwall/srcly.
  2. Under Build and deployment › Source, pick GitHub Actions (it is "Deploy from a branch: gh-pages" today).
  3. Open Actions › Deploy site to GitHub Pages and click Run workflow on main. Later pushes to main that touch site/ deploy on their own.
  4. Check that https://byronwall.github.io/srcly/ shows the treemap hero.
  5. Optional: delete the gh-pages branch once the new deploy is live.

Limits

  • The page text and screenshots are fixed at e4485453. Run cd site && node scripts/capture.mjs after a UI release, then commit. A full run takes about 5 minutes.
  • The symbols and data-flow shots use engine/examples/symbol-graph, because a trace over the whole repository timed out.
  • The pages workflow can't run before merge, so the deploy itself is untested. The PR's Public site check builds and tests the same site/.

Stack: Srcly site

What splits: the new Srcly site, in two parts: the redesign with its capture script and Pages deploy, then a pass that makes it work for three visitor jobs (a link click, a docs search, a coding agent).
Why it splits: this PR is a complete site that can deploy alone. The second adds behavior (search, an interactive hero, llms.txt) that a reviewer can judge apart from the look.
Why this split: a split by area (landing, docs, deploy) was the other option. I rejected it because the deploy and the content must ship together to replace gh-pages, and each area layer would carry half of the new theme.

  1. feat(site): redesign the landing page around Srcly's own treemap #391: the redesign, screenshots and data from capture.mjs, and the Pages workflow.
  2. feat(site): search, an interactive hero and agent files #392: the interactive hero, header search, metric anchors, the agents section and agent files.

🤖 Generated with Claude Code

byronwall and others added 2 commits November 20, 2026 16:39
Each section is a treemap scope with the real LOC and complexity of the
code behind it. Adds a repeatable capture script, a GitHub Actions Pages
deploy, and dark mode.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- capture.mjs takes --ref (default origin/main) so every shot and data file
  comes from one revision, and waits for compare's summary
- compare screenshot, real explain output, metric catalog backticks as code
- docs captions match the new screenshots

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@byronwall
byronwall added this pull request to stack #393 November 20, 2026 23:02
@byronwall
byronwall merged commit 744216f into main Nov 20, 2026
10 checks passed
@byronwall
byronwall deleted the claude/landing-site-f6a5a4 branch November 20, 2026 23:07
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