The Monaspace type system: a monospaced type superfamily with some modern tricks up its sleeves. It is comprised of five variable axis typefaces. Each one has a distinct voice, but they are all metrics-compatible with one another, allowing you to mix and match them for a more expressive typographical palette.

Letters on a grid is how we see our code. Why not make those letters better?

✨ An exploration from GitHub Next. ✨ See the full story of Monaspace at monaspace.githubnext.com.

🔤 Download the latest release 🔤

Monaspace is made available as both a variable-axis font and as static builds. You can install them both side-by-side; their family names are distinct. For example:

• Monaspace _____: the static family
• Monaspace _____ Var or VF: the variable family

The variable fonts have one file per family (Neon, Argon, etc). Modern and convenient!

The static fonts have one file per cut per family. The variable axes have named stops for each of the axes, like light or bold for weight, italic for italics, and semiwide and wide for width. The combinatoric explosion of all these properties means that the full installation of static fonts involves hundreds of font files. But for situations which don't yet support variable fonts, the static builds give you a wide variety of stops throughout the range of each axis.

There are eight groups of coding ligatures, separated into stylistic sets. You may be able to selectively enable or disable individual sets:

• ss01: ligatures related to the equals glyph like != and ===.
• ss02: ligatures related to the greater than or less than operators.
• ss03: ligatures related to arrows like -> and =>.
• ss04: ligatures related to markup, like </ and />.
• ss05: ligatures related to the F♯ programming language, like |>.
• ss06: ligatures related to repeated uses of # such as ## or ###.
• ss07: ligatures related to the asterisk like ***.
• ss08: ligatures related to combinations like .= or .-.

You must enable discrectionary ligatures first, often using the dlig setting. See below for editor-specific instructions.

You can manually drag the fonts from the fonts/otf and fonts/variable directory into Font Book.

There is also a script which automates the deletion of all Monaspace fonts from ~/Library/Fonts and then copies over the latest versions. Invoke it from the root of the repo like:

$ bash ./util/install_macos.sh

All files with a .woff or .woff2 suffix are intended for use on the web. You do not install them with your operating system, but rather add them to your web development project.

As with the desktop fonts, they are made available both as variable and static fonts.

Texture healing and coding ligatures are controlled by the same setting. You can enable either, or both.

If you only want texture healing and basic coding ligatures, add the following line to your settings.json:

  "editor.fontLigatures": true,

If you want more coding ligatures, you must customize that setting to specify all of the sets you want enabled:

  "editor.fontLigatures": "'calt', 'liga', 'dlig', 'ss01', 'ss02', ... (more stylistic sets) ...",

If you want coding ligatures but do not want texture healing, you can elide the calt setting:

  "editor.fontLigatures": "'liga', 'dlig', 'ss01', 'ss02', ... (more stylistic sets) ...",

There's no formal contribution guide yet! If you're interested in contributing to the typefaces, you should read the Texture Healing guide, as it explains how to produce the neccessary alternate glyphs.

This is a convenience utility which renames moves the built fonts into the respective directories. You will need Deno installed, and invoke it thus:

$ ./util/renamer.ts --src="~/path/to/the/built/fonts"

SIL OFL. See LICENSE.

Please file issues on this repo. Monaspace is not a supported product; do not reach out to GitHub support with questions as they do not provide support for GitHub Next explorations.

Monaspace was made with the goal of improving all code, for all developers. GitHub Next set out on this journey in 2022, and we were fortunate to find a type foundry that shares our passion for improving software in Lettermatic. The result is a marriage of form and function that opens the door to new developer experiences, and that would not have been possible without the domain expertise and skill of the lettermatic team, and the time they invested to work with GitHub Next on figuring out how typography ought to work for code.

• Riley Cran
• Danelle Cheney
• Heather Cran

• Cole Bemis
• Amelia Wattenberger
• Krzysztof Cieślak
• Idan Gazit

• Anna Thomas
• Marg Chronister
• Jane Solomon