Add Precise footer to StorageDaddy landing page - #59
Merged
sarthakagrawal927 merged 2 commits intoOct 5, 2026
Merged
Conversation
sarthakagrawal927
marked this pull request as ready for review
October 5, 2026 17:56
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change
Integrate the already-selected Precise footer into StorageDaddy's public Worker-served landing page. Preserve the native CTA, disclosures, all six existing footer links, analytics and dark palette. The selected shared runtime renders StorageDaddy's existing catalog-authorized, consent-based newsletter opt-in; catalog capture policy and app behavior are unchanged. Serve the existing public-intended StorageDaddy illustration and pinned OFL font assets through the existing static asset binding. The only CSP change is the owner-approved
font-src 'self'directive. A scopedwidth:100%rule keeps the footer host and studio strip full width.Verification
npm --prefix site run checkvia Fleet Workspace passed: 19 tests, TypeScript, and Wrangler dry-run (34 public files); Fleet wrapper exit 0.37348616135is green. Its current workflow covers native Swift/candidate checks, not the site tests; the managed web check above qualifies the site source.