Recipes for specific situations that come up once your site is running – narrower than the walkthrough, each one self-contained. The first three extend steps of the walkthrough; the rest cover situations that surface as a site matures, including upgrading an existing v2 site to v3.
Generate TypeScript types from your queries so data flows typed into your components.
Share GraphQL fragments across queriesDefine a fragment once and reuse it across query files with #import.
Write your own @font-face CSSPreload and serve your Fontdue-hosted fonts as page webfonts.
Customize Stripe elementsStyle the Stripe Address Element to match your site’s design.
Gate third-party scripts on consentBlock analytics scripts until the visitor accepts cookies.
Use a headless CMSCompose Fontdue’s GraphQL API with a separate CMS like Sanity for richer editorial workflows.
Render components in your contentRender Fontdue components that editors embed as HTML in collection descriptions and content pages.
Migrate from v2Upgrade an existing Next.js site from fontdue-js v2 to the framework-agnostic v3.