feat(manifest): generate site.webmanifest + maskable icons#41
Merged
Conversation
Signed-off-by: Aaron Cupp <mrcupp@mrcupp.com>
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.
Closes #29. Part of #26 (Phase 3 — extension).
The website wires a favicon and apple-touch-icon but ships no web app manifest, so there's no installable-PWA metadata and no maskable icons — Android masks the plain square favicon and clips the corners of the mark.
This adds a
manifestbuild target:logos/favicon/site.webmanifest— name,theme_color/background_color(both the dark wash#0a0e1a),display: standalone, and aniconsarray: the existing 192/512 aspurpose: "any"plus two maskable icons aspurpose: "maskable".logos/favicon/favicon-maskable-{192,512}.png— the symbol inset 20% on the wash, so a circular/squircle mask never touches the phi.New
[manifest]section inbrand.toml. Manifestsrcpaths are bare filenames — the file sits beside the icons inlogos/favicon/; consumers adjustsrcto their served path. Byte-identical on rebuild.