Fontdue can serve your whole storefront from a template, or hand you components to embed in a site you’ve built yourself. That choice is your integration path, and it’s the first thing to settle – what you can customize, and where those customizations land, follows from it.
Choose your integration path
The Integration tab in Settings is where you tell Fontdue which path you’re taking. The admin tailors itself to the selection – tabs and fields that don’t apply to your setup are hidden11For example, if you run your own website without the GraphQL API, the Pages and Articles sections are hidden, since Fontdue isn’t serving that content. – so set it before customizing the rest, and update it if your setup changes later. The options are listed in Settings → Integration.
Custom HTML and deploy hooks
Two developer settings on the same Integration tab handle the mechanics of wiring Fontdue into a site you host yourself: markup Fontdue injects into the pages it serves, and a hook it calls when your content changes.
HTML head
Markup entered here is injected into every Fontdue-served page – useful for analytics snippets and third-party tags. Even with the demo template disabled, Fontdue still serves the order confirmation page, customer dashboard, and login page, so the head snippet continues to apply on those surfaces.
If you’ve enabled cookie consent, see Gate third-party scripts on consent for how to wire scripts in this field through the consent banner.
Deploy hook URL
A web address Fontdue notifies whenever your content changes – a new collection, an edited price, an updated page. Point it at an endpoint that rebuilds or refreshes your own site, so visitors see the change without a manual redeploy. Revalidate data covers the setup for a statically built site.22The field is hidden on template setups – Fontdue rebuilds the pages it serves itself, so there’s nothing external to redeploy.