Skip to content

Review the latin-only font subset against real recipe content #9

Description

@chrispezza

PR #6 self-hosted the three typefaces to stop the installed app falling back to Georgia and system-ui offline. The seven faces in The Back Bar Design System/assets/fonts/ are the latin subsets only — 160 KB total, chosen to keep the shell cache small.

That is a deliberate trade with an untested edge: any glyph outside the latin range falls back to Georgia mid-sentence, which is more visible than a whole page in the wrong face.

Content that plausibly reaches outside it:

  • The vintage imports in scripts/vintage/ (Thomas 1862, Winter 1884) — period text with typographic quirks.
  • Ingredient names carrying accents. "Orange curaçao" is already in the seeded data; the ç is in the latin subset, but names like crème de cassis, piña colada and añejo are worth confirming rather than assuming.
  • The fraction glyphs the design system requires (¾ ⅓ ⅘) and the fleuron ◆ — these render today, but should be checked in every face, not just the display one.

Action: audit the ingredient and cocktail names actually in the database against the subsets' unicode ranges, then either confirm latin is sufficient or add latin-ext for the faces that need it (roughly +25 KB each). The @fontsource packages the files came from ship latin-ext variants of every face used here.

Found during the UX audit (2026-09-02).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementType: new capability or improvement

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions