Fontdue includes a basic content management system (CMS) for authoring the parts of your site that aren’t fonts themselves – the product page accompanying a family, profiles for your designers, standalone pages like About or FAQ, and blog-style articles. It lives in four places in the admin: the Content tab on each font collection, and the Designers, Pages, and Articles sections.
Everything authored here is exposed through the GraphQL API for your own site to query. The demo template renders product-page content, pages, and articles automatically; designer profiles are available through GraphQL but the demo template doesn’t display them. Fontdue’s CMS is often enough for foundry sites – for more ambitious content-driven sites, query the core catalog alongside a separate headless CMS like Sanity.
These content surfaces are only relevant for certain integrations – the demo template, or your own site fetching from the GraphQL API. If your site runs on WordPress, Webflow, or another website builder, you’ll most likely author content there instead. Set your integration path accordingly: the Content tab on font collections and the Designers, Pages, and Articles sections stay hidden when Fontdue isn’t being used for content.