Typefaces
Names, styles, specimens, and the details visitors need to explore a family.
Create
A private content system for type foundries. Edit typefaces, pages and stories in one studio — then show them on any modern website.
Built around typefaces, specimens, locales and editorial pages — not a generic blog kit dressed up for fonts.
Each foundry gets a private CMS and address on minastype.studio, with its own database and login.
Connect Next.js, Nuxt, Svelte or Astro. The studio holds content; your site decides how it looks.
The headless CMS
A CMS stores and organises content. Headless means the public website is separate: you edit in the studio; the site asks for content through an API.
Names, styles, specimens, and the details visitors need to explore a family.
Stories, release notes, and long-form writing with titles, dates, and rich text.
Bios, portraits, and credits that introduce the people behind the type.
About, contact, and other site pages built from flexible blocks you edit in the studio.
The UI Frontend
Choose a framework for the public site. Click a card to see how Minastype, the code, and the website fit together.
Discover
From a new typeface in the studio to a live page on your site — five steps, one continuous flow.
In the CMS
In the frontend
On the website
Open your studio and add a typeface — name, styles, and basics.
And what
Before you can publish, you need two accounts. Each one covers a different part of the stack.
Why: This is your studio — where you manage typefaces, pages, and stories.
What it does: Minastype gives you a private CMS, your own studio address, and the tools to publish content without writing code.
Why: Your website’s design and code need a safe home that can deploy updates.
What it does: GitHub stores the frontend project and connects it to hosting, so changes to the site can go live in a controlled way.
Framework