Skip to content

docs: say that a step's family in tokens.json names a font token - #11

Merged
rqbazan merged 1 commit into
mainfrom
docs/type-family-key
Oct 17, 2026
Merged

rqbazan merged 1 commit into
mainfrom
docs/type-family-key

Conversation

@rqbazan

@rqbazan rqbazan commented Oct 17, 2026

Copy link
Copy Markdown
Member

Summary

A reader of tokens.json couldn't tell that a step's family is a key, not a font stack. The "In code" section of typography.md now says so.

 tokens.json
   font.sans.value  "'IBM Plex Sans', 'Helvetica Neue', Helvetica, sans-serif"
   type.title.family  "sans"   ← the name of a font token
-                                (not said anywhere)
+                                typography.md: the stack is font[family].value

In CSS, --vlab-type-<step>-family already resolves to the stack, as var(--vlab-font-sans). Only a JSON consumer, such as a server-rendered image, has to look it up.

Patch changeset: a text changes.

Evidence

  • Before: typography.md says "read type in @variablelab/brand/tokens.json" and nothing more.
    After: it adds that family names a font token, sans or mono, whose stack is that token's value under font. pnpm check exits 0.

Merge Danger

Door: two-way.

Blast Radius: none.

One sentence in a chapter; no token, export or asset changes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01N8f1sEEDiR2ikgqtHWXgYn

@changeset-bot

changeset-bot Bot commented Oct 17, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 4ae9287

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@variablelab/brand Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@rqbazan
rqbazan merged commit 9bf78b0 into main Oct 17, 2026
2 checks passed
@rqbazan
rqbazan deleted the docs/type-family-key branch October 17, 2026 20:27
@vland-bot vland-bot Bot mentioned this pull request Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant