docs(assets): OGAR logo + favicon (hand-authored SVG), wired into both READMEs#103
Merged
Conversation
Two SVG assets under docs/assets/: - ogar-logo.svg (1.2 KB, viewBox 320x150) — wordmark: a bisected O glyph with an outgoing edge to a leaf dot, followed by "GAR" in a clean geometric sans (Inter / IBM Plex / system-ui fallback). The bisector sits 2u above the O's geometric center so the lower half (the shared canonical concept) reads slightly heavier than the upper half (the per-app render lens) — the hi/lo asymmetry of a 32-bit classid as a visual signature. - ogar-favicon.svg (556 B, viewBox 64x64) — just the bisected O, optimized for 16-64px favicon use. Drops the edge+dot which wouldn't survive at small sizes. Both use fill="currentColor" for light/dark theme adaptation; no gradients, no shadows, no embedded fonts. Validated as well-formed XML via xmllint. Wired into the top of both README.md and README.de.md as a 64px-tall inline image, preserving the H1 heading below for accessibility and semantic structure.
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
2 participants
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.
What
Two hand-authored SVG assets under
docs/assets/, wired into both READMEs.ogar-logo.svgogar-favicon.svgGeometry notes
The bisector sits 2 units above the O's geometric centre. That makes the lower half slightly heavier than the upper half — a deliberate signature of the 32-bit classid's hi/lo asymmetry:
lo u16) — the bedrock every app stands onhi u16) — the swappable skinThe outgoing edge descends from the bottom of the O — semantically from the concept half — to a leaf dot, signalling graph (not just registry).
Style
fill="currentColor"throughout: adapts to GitHub light/dark mode without needing media-query<picture>switchesInter, 'IBM Plex Sans', 'Helvetica Neue', Arial, system-ui, …) so rendering falls back gracefully across platformsxmllintREADME integration
Both
README.mdandREADME.de.mdnow lead with the inline logo:H1 heading preserved below the image for accessibility and semantic structure (the alt text on the
<img>is alsoOGAR).Iteration handles
If the proportions need tuning later, the load-bearing constants are:
ogar-logo.svg,y="56"— vs geometric centre at y=58)Generated by Claude Code