Skip to content

Fix landing view count and responsive text clearance - #53

Merged
sarthakagrawal927 merged 1 commit into
mainfrom
fix/landing-copy-responsive-49-51-20261003
Oct 2, 2026
Merged

sarthakagrawal927 merged 1 commit into
mainfrom
fix/landing-copy-responsive-49-51-20261003

Conversation

@sarthakagrawal927

Copy link
Copy Markdown
Member

The landing’s Explore card now correctly says nine views, matching the existing native mode selector. Its paragraph reserves the existing decorative-bar footprint at all widths, including enlarged text; compact hero CTAs wrap naturally rather than making a320px viewport overflow.

Only site/public/storagedaddy/index.html and style.css changed. Existing palette, type, breakpoints, desktop composition, native source, release manifest, updater feed and build110 binaries are preserved. This web-only patch is independent of held native PR50.

Validation: frozen npm install;17mocked site tests, TypeScript, Wrangler dry-run; actual isolated Chrome fixture normal320/390/620/621/768/1440, paragraph200% at320/390/768/1440, minimum25px bar clearance, keyboard download CTA and synthetic download boundary. Remote widgets/analytics and nonGET requests blocked. Normal tablet/desktop fullpage renders are byte-identical to baseline CSS counterparts before the one-word copy correction. Staged Gitleaks and whitespace checks pass.

References #49 and #51. Those issues stay open until separately authorized web publication and actual public proof. Issue52 is consolidated as a duplicate. No native release/install, security/config/dependency change, or owner acceptance claim.

@sarthakagrawal927
sarthakagrawal927 merged commit 915c566 into main Oct 2, 2026
2 checks passed
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