Removed underline from anchor styling #534
No reviewers
Labels
No labels
Kestra
bug
enhancement
someday
subtask
☁️ api
🎛️ infrastructure
🐞 sentry
📆 2025 Season
📝 pages
allpicks
📝 pages
picks
📝 pages
standings
🚀 performance
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
johnsturgeon/tgfp-web!534
Loading…
Reference in a new issue
No description provided.
Delete branch "remove-underline-from-a-styling-for-the-v3-pool-531"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Resolves #531
I have enough to write the review. Both key findings are confirmed against the working tree.
Summary
This PR extracts two reusable utilities (
card-gold,tgfp-link) intov3.src.cssand swaps the repeated inlineunderline text-tgfp-accentlink styling over totgfp-link(which drops the always-on underline in favor of hover-only), plus regenerates the compiledv3.css. The refactor is clean and the compiled CSS correctly picks up the new utilities and purges the now-unused ones, but one link lost its styling entirely in the process.Blocking
app/templates/v3/home.html:12-13— the Discord link was left withclass=" ", so it now renders as unstyled inherited text. Every other link in this PR moved totgfp-link, but this one had itstext-tgfp-accent underlineclasses stripped and replaced with an empty class instead. The result is a link that is neither colored nor underlined and is visually indistinguishable from body copy — the opposite of the PR's intent. This should beclass="tgfp-link".Worth fixing
app/templates/v3/allpicks.html:6-8— the<p>opened on line 6 is never closed before the</div>. Browsers will auto-close it, but the original markup was well-formed (<h1>…</h1>) and this regresses that. Add the missing</p>after "before seeing this page". (Also note the copy dropped its trailing period, if that matters for consistency.)Nits
underline,bg-linear-to-br,from-tgfp-light-gold/30,to-white, orto-80%, so removing those utility classes from the compiledv3.csswon't break other pages. No action needed — just flagging that it was verified.home.htmlregression would not have been caught by CI. Not something to fix in this PR, but worth keeping in mind.