google / google/fonts

Add Aykiz

Open
#10,715 17 comments 0 reactions 0 assignees View on GitHub
I New Font II Submission
Dominant language
HTML
Stars
20.5k
Forks
2.9k
Avg merge
1d 21h
Merged PRs (30d)
95

Description

**Font Project Git Repo URL:** https://github.com/mumullickm/aykiz-font

**Super short description of the Font Family:**

Aykiz is a **corner-rounded derivative of Montserrat**, stated openly and up front. It is built from **Montserrat's own UFO masters and designspaces**, not by post-processing the static fonts: a corner-rounding filter fillets the corners on the masters with true circular cubic arcs, and fontmake interpolates the 18 static styles (Thin 100 to Black 900 plus matching italics) and builds the two variable fonts from the same sources. The radius scales with weight (6 / 28 / 58 units per 1000 UPM on the Thin, SemiBold and Black masters) so the softness stays optically consistent.

Which corners round is decided by two rules, not by a threshold. A corner buried inside overlapping ink stays sharp, because Montserrat is drawn from overlapping strokes and those corners belong to the construction rather than the drawing (the crossing of X, H's bar meeting its stems, the crossbar of e); this is measured with a winding-number probe. Every other corner is filleted, convex corners at the full radius and concave inner junctions at 55% of it.

Everything else (metrics, sidebearings, kerning, OpenType features, and the full Montserrat character set of extended Latin, Vietnamese and Cyrillic) is inherited unchanged. The result is a soft Montserrat for display use whose rounding disappears at text sizes; no rounded companion to Montserrat currently exists in the catalog.

Variable fonts: `fonts/variable/Aykiz[wght].ttf` and `fonts/variable/Aykiz-Italic[wght].ttf`, wght 100 to 900, nine named instances and a STAT table, matching upstream Montserrat's own variable build.

Provenance and transparency:
- Original design: Julieta Ulanovsky and the Montserrat Project Authors, used under the SIL OFL 1.1. Original copyright is retained in OFL.txt and the name table; the derivative adds its own copyright line alongside.
- The reserved font name "Montserrat" is not used in whole or in part ("Aykiz" is a Turkish given name; unique per namecheck.fontdata.com).
- **AI disclosure:** the outline-processing filter and build tooling were written with AI assistance (Anthropic's Claude). No glyphs were AI-generated; the filter deterministically transforms the human-designed Montserrat outlines. The build is fully reproducible: `sources/prepare_sources.py` regenerates the rounded masters from a fresh upstream Montserrat checkout and `sources/build.sh` builds the statics, the variable fonts and the metadata pass.

We understand light derivatives of existing catalog families are an editorial judgment call. Submitting honestly for your consideration, and happy to do whatever onboarding work would make this viable. If the team would rather see the rounding contributed to Montserrat itself than shipped as a separate family, I am glad to take it there instead.

**Requirements:**

- [x] The entire font project is available in a Github repository (repo) and licensed under the [OFL](https://openfontlicense.org/open-font-license-official-text/)
- [x] The source files are available in the repo (`sources/*.ufo` + `sources/*.designspace` are the source of record, with `sources/round_corners.py`, `sources/prepare_sources.py` and `sources/build.sh` making the whole family reproducible from upstream Montserrat)
- [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. (Montserrat is OFL; AI tooling disclosed above.)
- [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. (Upstream RFN "Montserrat" is respected and unused in the name "Aykiz".)
- [x] The family name is unique according to [namecheck.fontdata.com](https://namecheck.fontdata.com/) ("We can't find any font by that exact name")
- [x] The name of the font family expected to appear on app menus must be very clearly communicated and definitive: **Aykiz**
- [x] The font supports at least the Google Fonts 'Latin Core' glyphset (inherited from Montserrat, already in the GF catalog)
- [x] The repo has the [Google Fonts preferred upstream repo structure](https://googlefonts.github.io/gf-guide/upstream.html)
- [x] I have read, agree with, and comply with, the full [Google Fonts contributing requirements](https://googlefonts.github.io/gf-guide/index#pre-production-getting-your-fonts-ready-for-gf)
- [x] I will maintain the repository and participate in the onboarding process (addressing, solving, and responding to issues, merging pull requests, etc)

**Image:**

![Aykiz preview](https://raw.githubusercontent.com/mumullickm/aykiz-font/main/documentation/preview.png)

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the linked Aykiz repository and the Google Fonts contributing requirements, then inspect sources/prepare_sources.py and sources/build.sh to understand the reproducible build. Run the documented build and verify the stated static and variable font outputs, licensing, naming, glyph coverage, and upstream structure before determining whether the family is suitable for inclusion.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system, design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.