The heroes ended 38px (home), 59px (category pages), and 80px (sponsorship) below their last line, against 20px above their top bar.
Co-Authored-By: Claude <noreply@anthropic.com>
Measured from the section edge to the nearest glyph or filled box, the guide band put 92px under its text against 51px above its heading, the sponsor band 67px against 52px, and the Sponsorship page sections ranged from 69px to 92px under content that sat 68px to 84px below their tops.
Co-Authored-By: Claude <noreply@anthropic.com>
The space above the label's first line added about 8px to the visible top gap, so the buttons sat closer to the footer than the label sat to the table.
Co-Authored-By: Claude <noreply@anthropic.com>
The hint's column capped at 28rem, so "Press / to search. Tags open their category. Click a row for details." wrapped to two lines beside the heading.
Co-Authored-By: Claude <noreply@anthropic.com>
The grid filled rows left to right, so reading down a column skipped through README order four categories at a time.
Co-Authored-By: Claude <noreply@anthropic.com>
The label's 1.5rem bottom margin stacked on the section's 1rem grid gap, leaving 51px between "Contribute" and the heading.
Co-Authored-By: Claude <noreply@anthropic.com>
Sections faded and slid in as they scrolled into view, so screenshots and quick scrolls caught the sponsor band and search box half-drawn.
Co-Authored-By: Claude <noreply@anthropic.com>
The section put 88px above its label and below its buttons; it now uses the page's side gutter like the table and guide sections.
Co-Authored-By: Claude <noreply@anthropic.com>
The table section started 72px below the sponsor band, and a one-line order note sat at the bottom of its grid row beside the two-line search hint, so category pages put 97px above the first text. The guide band put 81px above its heading. Both now use the page's side gutter.
Co-Authored-By: Claude <noreply@anthropic.com>
On phones the links line wrapped mid-phrase, splitting "19 hours ago" across two lines after the repository URL.
Co-Authored-By: Claude <noreply@anthropic.com>
The homepage printed each description inside its expanded row as .expand-desc, styled apart from the .desc-row that category pages use, so every spacing change to the table had to be tuned twice. The homepage now reveals the same .desc-row while a row is open, so its descriptions take the category pages' 15.2px size, and the .expand-desc markup and styles are gone.
Co-Authored-By: Claude <noreply@anthropic.com>
On phones the hidden number column is the first cell, so the name column fell back to the 0.55rem inner padding and names and descriptions sat 4px left of the links line and group headings, which use 0.8rem.
Co-Authored-By: Claude <noreply@anthropic.com>
An open row put about 38px between the project name and its description and 10px before its links, and category rows put 26px between name and description, because .table tbody td overrode the zero top padding meant for description and expand rows. The top gap is now about 2px larger than the bottom one, since the bold name's descenders make an equal gap look smaller.
Co-Authored-By: Claude <noreply@anthropic.com>
Each row restarted its own gradient, so the darker bottom of the open row met the lighter top of its expand row and read as a faint border between them.
Co-Authored-By: Claude <noreply@anthropic.com>
Below 960px the -1rem top margin on the sponsor link, meant for the side-by-side desktop layout, pulled the sponsor name closer to the link than the link sat to its own label, so the link read as part of the sponsor entry.
Co-Authored-By: Claude <noreply@anthropic.com>
On phones the hero stats ran together as one sentence, breaking wherever space ran out and leaving a "/" dangling at a line end.
Co-Authored-By: Claude <noreply@anthropic.com>
At phone width the two primary buttons labelled with the full address wrapped over three lines, and the address in the Get started sentence broke at its hyphen.
Co-Authored-By: Claude <noreply@anthropic.com>
On narrow phone heroes the sheen, a diagonal light stripe sliding across for 54s after load, rendered as a near-vertical band sweeping sideways that read as a loading or progress bar.
Co-Authored-By: Claude <noreply@anthropic.com>
The home hero was forced to the full viewport height, opening an empty band between the top bar and the headline whenever its content was shorter than the window and pushing the project table down.
Co-Authored-By: Claude <noreply@anthropic.com>
Sponsorship-page, sponsor band, category, group-page lead, and home hero links fell back to the browser's default focus ring.
Co-Authored-By: Claude <noreply@anthropic.com>
The sponsor band's background faded from --bg-paper-strong to --bg-paper, ending lighter than the page below it, with only a faint bottom border, so the band blended into the search section and read as its intro rather than a sponsor placement; the sponsor name also gave no cue that it links out.
Co-Authored-By: Claude <noreply@anthropic.com>
The longer billing lines added with the annual prices broke across two or three lines beside the price and split amounts from their units.
Co-Authored-By: Claude <noreply@anthropic.com>
On phones the hero's 74-link category grid was 1,236px tall and pushed the project table down to 2,583px, over three screens.
Co-Authored-By: Claude <noreply@anthropic.com>
Below 960px the table hid the PyPI Downloads column but kept the default downloads sort, so the visible Stars column looked unsorted and the active sort header was not shown or tappable.
Co-Authored-By: Claude <noreply@anthropic.com>
Keyboard focus on a table row drew one box per cell, because the focused row fell back to the browser's default outline and each cell also got an inset accent stripe on its left edge.
Co-Authored-By: Claude <noreply@anthropic.com>
The sponsorship hero kicker sat farther above the heading than the heading sat above its subtitle, so the label read as detached from the heading it labels.
Co-Authored-By: Claude <noreply@anthropic.com>
The subtitle's fixed top margin did not grow with the fluid h1, so heading descenders crowded the subtitle on category and sponsorship heroes.
Co-Authored-By: Claude <noreply@anthropic.com>
The sponsorship ledes were set in Cormorant Garamond, whose short x-height and thin strokes read poorly across a paragraph, and past sponsor names shared a baseline with Manrope descriptions, where the mismatched x-heights clash.
Co-Authored-By: Claude <noreply@anthropic.com>
On the sponsorship page the tier names and fact labels rendered smaller than the "/ month" cadence beneath them, inverting the hierarchy.
Co-Authored-By: Claude <noreply@anthropic.com>
Roughly 20 ad-hoc font-size values rendered near-duplicate sizes 1-2px apart, reading as noise rather than hierarchy, and .hero-category-link rendered below the documented 12px floor.
Co-Authored-By: Claude <noreply@anthropic.com>
Sponsorship tier prices rendered in Cormorant Garamond's default old-style figures, so zeros sat at x-height and the 5 dropped below the baseline, making "$500" hard to read.
Co-Authored-By: Claude <noreply@anthropic.com>
Mailto clicks on the sponsorship page leave no page view, so the sponsor funnel ended at the sponsorship page and never showed who went on to email. Each click now sends a sponsor_contact event with a short tier value (headline, featured, indie, or general) rather than the link URL, since GA4 caps event parameter values at 100 characters and the Indie Dev mailto href is 101.
Co-Authored-By: Claude <noreply@anthropic.com>
Picks in a "How to choose" list were plain text, so a reader had to hunt for the tool's row in the table.
Co-Authored-By: Claude <noreply@anthropic.com>
The hero-rise fade-in started .hero-copy, which holds the LCP <h1>, at opacity 0, and Chrome ignores opacity-0 paints for LCP, delaying it by about 455 ms.
Co-Authored-By: Claude <noreply@anthropic.com>
`.results-note` carried an inner `max-width: 28rem`, which breaks the rule that `.section-shell` is the only width cap.
Co-Authored-By: Claude <noreply@anthropic.com>
Group pages showed only tables, so visitors arriving from broad searches like "python ml library" got none of the which-one-to-pick guidance that each section's intro already gives.
Co-Authored-By: Claude <noreply@anthropic.com>
Inline code in category intros and guides inherited the body font with no background, so identifiers like INSTALLED_APPS read as ordinary words.
Co-Authored-By: Claude <noreply@anthropic.com>
applyFilters walked the static load-order NodeList, so after sorting by a column header, row numbers kept each row's original load-order position instead of counting 1..n down the sorted table.
Co-Authored-By: Claude <noreply@anthropic.com>
On section and subcategory pages, every row repeated its use case and current page as tags (and as the label under the name on phones), right under a heading that already said the same thing. They are now hidden in editorial order and shown again when a column sort flattens the groups.
Co-Authored-By: Claude <noreply@anthropic.com>
After sorting by a column, or while a search hid a group, category page group headings stayed hidden, so the header's jump links (and any use-case heading link) pointed at a hidden element and did nothing.
Co-Authored-By: Claude <noreply@anthropic.com>
Vinta ChenandClaude
AurantiumandGitHub