Restructure for Google Fonts onboarding#4
Open
Krivoblotsky wants to merge 2 commits into
Open
Conversation
- Add sources/Fixel.designspace and sources/config.yaml so the family builds reproducibly via gftools-builder - Fix features.fea across all 18 UFOs: replace AGL-style glyph refs (uni0492, uni0401, uni04AA, etc.) with the actual glyph names (Gestrokecyr, Io-cy, Estailcyr...). Without this the build fails. - Rebuild fonts/ with the new pipeline: one wdth+wght variable font (Fixel[wdth,wght].ttf, Regular default) plus 18 static TTFs and matching WOFF2. Drop the stale hand-built FixelDisplay-* and FixelVariable.ttf artifacts. - Add GitHub Actions workflows for build and FontBakery checks - Rewrite documentation/DESCRIPTION.en_us.html (Google Fonts About copy) and README.md (build, layout, designers, license) - Add FONTBAKERY-REPORT.md tracking remaining onboarding gaps Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
onikiienko
reviewed
May 11, 2026
|
|
||
| This file summarises the current state of `fontbakery check-googlefonts` against | ||
| the gftools-built artefacts. The detailed HTML report lives in | ||
| [FONTBAKERY-REPORT.html](FONTBAKERY-REPORT.html). |
Member
There was a problem hiding this comment.
We don't have this file in the repo and even add it to .gitignore
Member
There was a problem hiding this comment.
ok, we should regenerate. got it
| ```sh | ||
| pip install -r requirements.txt | ||
| cd sources | ||
| gftools builder config.yaml |
Member
There was a problem hiding this comment.
Should we commit this file or is it local and should be mentioned in the .gitignore?
onikiienko
approved these changes
May 11, 2026
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.
Summary
Sets up the repo so the Fixel family can be submitted to Google Fonts via the upstream-onboarding pipeline (https://googlefonts.github.io/gf-guide/onboarding.html).
sources/Fixel.designspace+sources/config.yamldrivegftools builderto produce one variable font withwdth+wghtaxes (Regular default atwdth=100,wght=400), 18 static TTFs, and matching WOFF2.features.feain all 18 UFOs referenced AGL-style glyph names (uni0492,uni0401,uni04AA, …) that don't exist in the glyph sets; replaced with the actual glyph names (Gestrokecyr,Io-cy,Estailcyr, …). Without this,fontmakefailed on every master.fonts/— drop hand-builtFixelDisplay-*.ttf/FixelVariable.ttf(variable defaulted to Thin/Text, which GF rejects) in favor ofFixel[wdth,wght].ttf+Fixel-*.ttf(Display) +FixelText-*.ttf..github/workflows/build.ymlandfontbakery.ymlrun the gftools build andfontbakery check-googlefontson every PR.documentation/DESCRIPTION.en_us.html, rewrittenREADME.mdwith build / layout / designers / license sections, andFONTBAKERY-REPORT.mdtracking the FAIL categories that still need source-level fixes by the type designers (vertical metrics, GF Latin Core coverage, NBSP, vendor ID, STAT axis-value names, etc.).Next steps before submitting to Google Fonts
FONTBAKERY-REPORT.mdFAILs (vertical metrics, glyph coverage, name-table cleanup, vendor ID).Test plan
pip install -r requirements.txt && cd sources && gftools builder config.yaml— completes all 94 steps locally.fvar:{'wght': (100, 400, 900), 'wdth': (87.5, 100, 100)},fsType=0, STAT table with both axes.fontbakery check-googlefontsruns end-to-end on VF + statics (seeFONTBAKERY-REPORT.mdfor the current snapshot).🤖 Generated with Claude Code