Where Programming Fonts Gets Its Font Information

Updated

Programming Fonts (programmingfonts.org) is a test-drive gallery for monospace coding fonts. Its font information is not generated automatically from font files or a font database — it is curated by the site's maintainers and published through the site itself, with the GitHub repo and Tumblr blog serving as the project's public presence. The site's own page lists "Github repo" and "Tumblr blog" as its external links, and the font list is organized by metadata fields the maintainers assign to each entry.

How the font list is organized

The site exposes several sort and search controls that reveal what data it stores per font:

  • Sort by: Newest, Oldest, Newest addition, Name, Author
  • Search: a text field for filtering the list
  • Details: a per-font view
  • Coverage: a per-font field
  • Variants: a per-font field
  • Website: a link out to the font's own page

This tells you the site treats each font as a record with at least: a name, an author, an addition date, a coverage value, a variants value, and an external website URL.

Where the underlying data comes from

The page evidence does not describe an automated pipeline, API, or font-file parser. What it does show is:

  1. A GitHub repository — listed as a link on the page. For a project like this, the repo is typically where the font list, metadata, and site code live, and where changes are proposed and merged.
  2. A Tumblr blog — also listed as a link. This is the project's informal update channel, separate from the site's own font list.

So the practical answer is: the information is maintained by the project (via its repo) and surfaced on the site, with the blog as a secondary channel. If you want to know why a specific font is listed, missing, or tagged a certain way, the repo is the place to check or ask.

What "Coverage" and "Variants" mean in practice

These two fields are the most useful for judging a font before you test-drive it:

Field What it tells you Why it matters
Coverage Which character sets / glyph ranges the font includes Determines whether your language, symbols, or ligatures will render
Variants Which weights, widths, or styles exist Determines whether you can pick a light/bold/italic version

Because the site does not document these fields on the page itself, treat them as filters rather than guarantees — always confirm against the font's own website, which the Website link takes you to.

How to verify a font's origin yourself

  1. Open the font's entry on programmingfonts.org.
  2. Read the Coverage and Variants fields to see what the site claims.
  3. Click Website to go to the font's own page and check the official character set and available styles.
  4. If the two disagree, trust the font's own site — the gallery is a convenience layer, not the source of truth.

Common sticking points

  • "Newest addition" vs. "Newest": these are separate sort options, so the site distinguishes when a font was added to the gallery from when the font itself was released. If a font looks out of order, check which sort you selected.
  • Missing fonts: the list is curated, so a font not appearing does not mean it doesn't exist — it may simply not have been added yet.
  • Stale metadata: since the data is maintained by hand, a font's variants or coverage may have changed upstream without the gallery being updated. The Website link is your check.