Make Slopcamera’s site quiet and retain phone navigation - #265
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
1 participant
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.
The public site now uses the quiet shared theme: real media proof, ruled sections, sans headings, and an in-flow footer. All phone navigation links remain available in a scrollable row with 44px targets. Release-derived installation commands and existing media/copy/appearance controls remain intact.
Updates design-kit to v0.23.0, site-footer to v0.20.0, and immutable theme snapshots to the reviewed upstream source.
Validation: focused site contracts passed (114 cases before the phone-nav assertion update; the affected 7-case suite then passed), snapshot integrity passed, isolated frozen website install passed, and independent AI source review found no blocking issue. Full current-route browser validation, screenshots, and final integration gates remain pending host CPU capacity; this draft must not merge until those pass.