Fontdue’s built-in Pages and Articles cover the common authoring cases – a foundry bio, a licensing FAQ, release announcements. When your editorial needs go beyond that – bespoke content models, draft and review workflows, structured fields with custom validation, content reuse across surfaces – a dedicated headless CMS like Sanity, Contentful, or Hygraph is the right tool.
The integration shape
Your site fetches from two APIs side by side. Fontdue’s GraphQL API supplies catalog data – collections, fonts, prices, license definitions, customer-facing settings. Your CMS supplies the editorial content around it: long-form product narratives, in-use galleries, journal entries, custom landing pages. Each request goes to whichever API owns the data; you compose the results at render time.
The shared key between the two systems is usually the collection slug. A Sanity document representing the product page for ibm-plex carries a fontdueSlug: "ibm-plex" field; your page loader queries Fontdue for the collection by slug and Sanity by the same slug, then renders the merged result.
In the admin, set Integration → Also using GraphQL API on Integration paths so Fontdue knows you’re querying the API. Leave Fontdue’s Pages, Articles, and the Content tab unused – they stay hidden when Fontdue template isn’t selected, so there’s no duplication to manage.
More detail to come
A worked example with Sanity GROQ queries joined against Fontdue collection slugs is on the way. In the meantime, Query the GraphQL API covers the Fontdue side of the pattern.