templStart a font project
A new font starts from the Font.Garden project template. The template is a source repository in the Google Fonts layout, with the Font.Garden tools, QA and agent instructions. It holds a starter font with two glyphs. This chapter is the entry point for a new project.
Start by hand
-
Create a repository from the template with “Use this template” on GitHub, or clone it into a new folder.
-
Install the tools and name the family:
make setup make customize FAMILY="My Face" DESIGNER="Your Name" EMAIL=you@example.com -
Review the staged changes with
git diff --staged, then commit. -
Add glyphs. Draw them in the UFO, or trace them from a specimen image.
make customize replaces the placeholder family name, designer and repository URL in the sources, the documents and the file names. Run it once, before the first glyph.
Start from a specimen image with an agent
Give a coding agent (Claude Code, Codex or OMP) the image and this request. Replace the words in capital letters.
Create a font project from https://github.com/fontgarden/font-project-template for the specimen image at PATH. The family name is NAME, the designer is DESIGNER (EMAIL). The specimen is from ORIGIN. Clone the template into a new local folder, run
make setupandmake customize, then do the task in.agents/tasks/specimen-intake.md. Do not push or publish.
The agent needs img2glyph, img2bez and img2ufo on PATH. See Setting up a working environment.
The result is a project with one purple draft for each glyph of the specimen, a built font and a QA report. The designer then grades the drafts. See From a specimen image to drafts.
What the designer supplies
Only the designer can give these facts:
- the family name. A traced font does not get the name of the original typeface.
- the origin of the specimen, and that the design is free to use.
- the design decisions: which specimen, the metric targets and the style.
What the template gives
| part | content |
|---|---|
CONTEXT.md | the design rules of the style and the values that the tools check |
sources/ | a starter UFO, config.yaml and held-out-glyphs.toml |
Makefile | the commands, each of which calls fgtools |
AGENTS.md, .agents/ | the way of work for coding agents, and the task contracts |
documentation/ | the Google Fonts release document |
.github/workflows/ | the CI build, which runs make test |
After the start
The work loop is the same for every project: choose glyphs, draft, check, compare builds, review, grade and learn from the corrections. See Proposals and grading and Corrections and drafting evaluation.