Fix #199: deep-dive CTA buttons #201
No reviewers
Labels
No labels
actions
bug
cli
duplicate
enhancement
fork
forum
git storage
help wanted
insights
invalid
issues
moderation
oidc
ownership transfer
packages
pr/merge protection rules
projects
pull requests
question
releases
sponsorships
tags
webhooks
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
crueber/walhub!201
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/issue-199"
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?
Both 'How it works' links on the landing page (hero + quickstart bottom) were bare hover-underline spans. They are now secondary
.btnbuttons complementing the adjacent primary Browse repositories CTA — bottom CTAs sit side-by-side in one flex row; hero link is a centered button + explainer span. Copy kept ('How it works →'). Both themes via the shared.btntreatment in ui.css; keyboard focus via the global:focus-visiblerule. No new deps, no doc change (12_web_ui.md cross-link placement contracts unchanged).Verification:
node --test web/test/unit/*.test.js398/398 green (incl. new CTA-treatment pin in landing.test.js); real headless-Chrome CDP drive of the built bundle on both themes — button treatment confirmed via computed styles + screenshots, zero console errors.Both 'How it works' links (hero + quickstart bottom) were bare hover-underline spans; they are now secondary .btn buttons complementing the adjacent primary Browse repositories CTA. Copy kept ('How it works ->'); both themes via the shared .btn treatment in ui.css, keyboard focus via the global :focus-visible rule. No new deps. Pins: new CTA-treatment test in landing.test.js; how-it-works.test.js cross-link pins unchanged. No doc change: 12_web_ui.md cross-link placement contracts unchanged.