The demo template is the built-in front-end Fontdue serves out of the box at your-site.fontdue.com (or your custom domain, once connected). It reads from your catalog and CMS, lays out a homepage and product pages automatically, and exposes a small set of special slugs you can use to wire in licenses, test fonts, articles, and the customer login.
The template is a good fit if you want a fully working storefront without writing any front-end code. It supports limited customization – your logo, UI font, and theme colors, plus your cart and checkout copy, flow through automatically – and that’s the extent of the configurable surface. If you need finer control over layout, navigation, or typography, build your own site against the GraphQL API and embed Fontdue components instead, or get in touch about full-service website development.
Homepage
The homepage adjusts to the size of your catalog:
- One typeface – the homepage is the product page for that typeface.
- Two or more – the homepage is an index of every root collectionRoot collectionA top-level font collection – either a standalone family or a superfamily. These are the collections that usually have their own product page on your site. , with each row linking through to a product page.
The order of the index follows the order of the Collections list in the admin.
Product pages
Each root collection renders as a product page under /{slug}. The content comes straight from the collection’s Content tab:
- A header image carousel from the Images field (videos work too – upload an MP4 and it plays inline).
- The main Description below the type testers, rendered from markdown.
- A PDFs sidebar of any PDFs you’ve uploaded, with thumbnails generated from each PDF’s first page.
- A Supported languages list when Languages is set.
- A Minisite link button when Minisite link is set.
- A New badge next to the title when New is ticked.
- The
<meta name="description">populated from Short description.
Type testers configured in the collection’s Type testers tab render inline on the product page; the Character viewer appears below them. Both are interactive – visitors can toggle OpenType features, adjust variable axes, and edit the sample text.
Navigation
Every page you create in Content → Pages appears automatically in the top navigation, in the order set on the Pages list. Drag rows in the admin to reorder.
Tag a page with footer to move it from the top navigation to the footer navigation instead. A page in the footer is otherwise identical to one in the top nav.
The site logo from Site identity sits in the top-left and links back to the homepage.
Special slugs
Four page slugs unlock template behavior beyond a plain content page. Create a page in Content → Pages with one of these slugs, and the demo template swaps in a richer layout – any markdown you write in the page body appears alongside it.
licenses– renders an index of your font licenses. The list appears in a side navigation; your page text appears in the main column above the index.test-fonts– renders the test fonts download form. Your page text appears above the form. If you don’t have test fonts configured, the form will show an unavailable message.articles– renders an articles index. Tags on your articles populate as filter chips in the left column; each row shows the article’s first gallery image as a thumbnail.customer-login– customizes the message at the top of the customer login page, where customers request a magic-link sign-in to reach the customer dashboard.
Each special slug is optional. If you don’t create a page with the slug, the template still renders a default version of the surface (the customer login page works without a customer-login page, the articles list works without an articles page) – you only need to add one when you want to override the default copy or layout.
Article pages
Each article renders at /articles/{slug} with the title as an H1, tags inline below the title, the full image gallery as a header carousel, and the markdown body. The first gallery image is also used as the article’s thumbnail on the articles index.
The Published at, Link, Font collections, and SEO metadata fields are not rendered by the demo template – they’re available through GraphQL for custom sites to use.
Theme and typography
The demo template picks up your branding and cart and checkout copy:
- Logo, foundry name, UI font – the logo lives in the top-left; the UI font is used across the entire site, not just inside components.
- Theme colors – the CSS variables that style the components also style the template’s chrome (header, footer, links, type tester surrounds).
- Labels – string overrides apply to the cart, opt-in surfaces, and checkout the same as they do in any other integration.
There is no separate template-only style configuration.
Disable the demo template
If you’ve built your own site and don’t want Fontdue serving anything at your-site.fontdue.com, turn on Headless under Settings → Integration. Visitors to your Fontdue subdomain get a Not found page; your own site becomes the only public surface.
Fontdue still serves the paths that components and checkout depend on – /graphql, /quotes/*, /shared-cart/*, /customer-dashboard, and so on – those keep working regardless of the Headless setting. Only the demo template’s pages (homepage, product pages, articles, special-slug pages) are gone.
If you’re using the demo template, leave Headless off – it would 404 your own storefront.