Repository navigation
Description
Font family name: Mckitrick
Designer: Ian Lawton (https://github.com/ianlawton)
Repository: https://github.com/ianlawton/McKitrick
License: SIL Open Font License 1.1, no Reserved Font Names
Description: Mckitrick is a condensed display typeface drawn from a single sheet of hand-cut marker sketches. Every letter is built from separate, flat-ended strokes that stop short of one another where they meet; the shoulders of m, n and h branch steeply from the stem, and the dots on i and j are tapered, wider at the top. It is intended for display sizes: headings, posters, signs and labels. A stylistic set (ss01) provides a long-tailed f taken from the margin of the original sketch, and a case feature raises dashes and guillemets for all-caps text.
Styles: Regular (static), version 2.008
Glyph set: GF Latin Core plus Ţ ţ (349 glyphs), with combining marks, mark positioning, soft-dotted handling and a case feature
Sources and build: UFO source generated from Python stroke definitions (sources/build.py); fonts compiled with gftools builder sources/config.yaml. The OTF is hinted with otfautohint in a post-build step (sources/postprocess.py). Rebuilding reproduces the committed sources exactly.
QA: FontBakery check-googlefonts 1.1.0 on fonts/ttf/Mckitrick-Regular.ttf: 0 FAIL, 6 WARN, all expected: the alt-caron glyphs (ď ľ ť Ľ) use a dedicated wedge rather than a component, which the check can't inspect automatically; @ (three contours) and § (one continuous stroke) differ from the usual contour counts by design; the vendor ID is NONE; the subsets and article checks need the METADATA.pb and family folder that Google creates on onboarding; and the GF_TransLatin_Arabic note is informational. check-universal on the OTF: 0 FAIL, 0 WARN. Outlines have no overlaps, reversed contours or stray points.
Documentation: documentation/DESCRIPTION.en_us.html and documentation/article/ARTICLE.en_us.html with images.
Notes on authorship: The design and the original sketches are by Ian Lawton. The build tooling, the extrapolated glyphs and the spacing were developed with an AI assistant (Claude, by Anthropic) under his direction and review. This is recorded in FONTLOG.txt.
By opening this issue, I confirm the project meets the following requirements:
- [ x] The entire font project is available in a Github repository (repo) and licensed under the OFL
- [ x] I confirm that by 'entire font project', no "plus" or "pro" or other larger version of the project exists as a retail font anywhere
- [ x] The source files are available in the repo
- [x ] I am the sole copyright author of the entire project, or all other copyright authors have licensed their work to me under the OFL, and I commit to clearly disclosing if AI tools were used in the creation of this project.
- [ x] There are no "Reserved Font Names" in the OFL license information, or in the project documentation of any known upstream projects. If there are RFNs, they are not used in whole or in part in this family name, or, I want to discuss how Google can work with my use of them.
- [ x] The family name is unique according to namecheck.fontdata.com
- [ x] The name of the font family expected to appear on app menus must be very clearly communicated and definitive. It should not include any copyright holder's full names or acronyms.
- [ x] The font supports at least the Google Fonts 'Latin Core' glyphset from github.com/googlefonts/glyphsets (direct link)
- [ x] The repo has the Google Fonts preferred upstream repo structure
- [ x] I have read, agree with, and comply with, the full Google Fonts contributing requirements
- [ x] I will maintain the repository and participate in the onboarding process (addressing, solving, and responding to issues, merging pull requests, etc)

Activity
github-actions commentedon Nov 5, 2026
Triage Summary
Repository Layout & Template:
fonts/,sources/, anddocumentation/directories.sources/config.yamlforgftools builder.googlefonts-project-template(does not use the template Makefile orrequirements.in; build is managed viabuild.shand Python stroke-generation scripts).Font Sources:
sources/Mckitrick-Regular.ufo(UFO format).Licensing & Reserved Font Names:
OFL.txt).Checklist & Binary Validation:
fonts/ttf/Mckitrick-Regular.ttfandfonts/otf/Mckitrick-Regular.otf) were validated usingfontspector(googlefonts/glyph_coverage). Both passed with 0 failures, confirming full coverage of the Google Fonts Latin Core glyphset.DESCRIPTION.en_us.html, article, specimen images) are present.The submission is ready to proceed to human design evaluation.
emmamarichal commentedon Nov 6, 2026
Hi @ianlawton, thank you for your submission, we will review it as soon as possible and will let you know :)