Enforcing Brand Consistency Across Pages

Every page Flint generates starts from your design system: colors, fonts, spacing, navigation, footer, CTAs. This guide covers how to keep brand consistent as you build at scale.

During site import, Flint extracts:

• •Visual identity — colors, fonts, spacing, button styles
• •Navigation — your site's header and menu structure
• •Footer — links, legal text, trust badges
• •Recurring elements — CTAs, social links, compliance badges

This becomes your design system baseline. Every new page Flint generates starts from this foundation. See Brand Import and Sync for details on the import process.

1. 1.Import from the right page. Flint pulls the header and footer from whatever page you provide during brand import. If your homepage uses a simplified nav, import from an interior page that shows your full navigation.
2. 2.Use Mirror Sections. For an exact match, Mirror Sections pull your live header and footer directly from your main site. Updates you make on your CMS reflect on Flint pages automatically.
3. 3.Review before publishing. When Flint generates a new page, check the header and footer in the editor before publishing. Swap in the correct navigation at the section level if needed.

For regulated industries, certain elements must appear on every page — certification badges (for example, LegitScript), legal disclaimers, privacy links, or trust seals.

Current best practice:

• •Include compliance elements on your brand source page. Flint picks them up during extraction and carries them into generated pages.
• •Specify them in your prompt. When generating pages, be explicit: "Always include the LegitScript badge in the footer" or "Every page must show the patient fee disclaimer."
• •QA before publishing. Review each page in the editor to confirm compliance elements are present.

We're building support for locked sections — designated parts of a page that cannot be removed or modified during generation. This will let you hard-enforce compliance badges, legal disclaimers, and other required elements across every Flint page.

Interested in early access? Email support@tryflint.com to get details or join the beta.

Flint learns your preferences through:

• •Initial brand import — your site's design system
• •Chat corrections — adjustments you make during page generation carry forward to future pages
• •Template pages — create a reference page that's exactly right and use it as the starting point for new pages

• •Start with a template page. Build one page that's correct end-to-end: right nav, footer, CTAs, badges. Use it as the template for everything that follows.
• •Be specific in prompts. "Make a landing page using our standard header, red CTA button, LegitScript badge, and 100kr patient fee in the footer" gets better results than "make a landing page."
• •Push updates in bulk. If your navigation or footer changes, use Bulk Updating Pages to push the change across all existing Flint pages at once.