Brand Hub
Refari · Design system

Web & marketing pages

How the Refari brand is applied to a marketing or landing page. The brand fundamentals (logo, colour, type) live on the main Refari page; this is the layer on top: the hero-and-nav pattern, component library, motion, and the accessibility + SEO baseline a page must pass before it ships.

The principle

One brand, several page types

Don't confuse the brand with the page. The brand fundamentals are universal. On top of them sit page-type design systems, and a marketing page is deliberately louder and more animated than a policy or document page. This page defines the marketing one.

/* The rule that prevents 90% of off-brand mistakes: */
Teal (#4CF8EE) is a dark-background accent only.
On light backgrounds, use Blue (#0074BC). Teal on white fails contrast and looks washed out.
Colour in context

Same palette, placement is everything

The colours are the brand's; what's specific to marketing pages is where each one is allowed. Accents change by background.

Teal on dark
Correct — teal glows on ink/navy/hero backgrounds
Teal on light
Never — fails contrast, looks washed out
Blue on light
Correct — Blue is the accent on white/mist sections
Blue on dark
Weak — use teal (or white) on dark instead

Structure the page as alternating light bands (Mist / White) with one or two dark moments (the hero, a premium card, a stat strip). Teal and all the "magic" (glows, sparkles) live in the dark moments; the light bands stay calm and blue-accented.

The signature

The dark hero & nav

Every Refari marketing page opens the same way: a near-opaque deep-navy sticky nav with a 2px teal underline (white logo, teal CTA), flowing straight into the navy→blue gradient hero with a teal eyebrow and a shimmering accent phrase.

RefariPackagesFAQGet started
— Eyebrow in teal

A benefit-led headline, with one accent phrase.

Nav must be near-opaque (not translucent) so the hero doesn't bleed through as a grey haze. The underline is the brand's teal→cyan→blue or solid teal.

Component library

The building blocks

All included in the starter CSS, all seen live on the reference page.

Light vs dark cardsFree/base tiers in clean light cards; premium in a dark card with teal border + glow. The contrast does the selling.
Trust strip + reputationStar rating, review count and real review-platform logos (Google/G2/Capterra). Aggregate on a dark band.
Testimonial cardsReal quotes, named, with the source-platform logo. Never fabricate.
FAQ accordionNative <details> — collapsed, expand on click. Answers stay in the DOM (and in FAQPage schema) for AEO.
Logo / name marqueeHover-to-pause scroller for client or engine logos. Freezes to a static row under reduced-motion.
Sticky reputation barSlides up past the hero: rating on the left, package CTA on the right. Hides over the enquiry form.
Motion

Magical, but disciplined

Marketing pages are allowed to feel alive — but tastefully, and only in the dark moments. Every effect below must be disabled under prefers-reduced-motion (the starter does this for you).

Scroll revealSections fade/rise in as you scroll. The single biggest "crafted" signal.
Cursor glowA soft teal glow follows the pointer — on dark sections only, mouse only.
Sonar haloGentle teal rings emanate from the hero's signature card.
SparklesA few twinkling teal sparkles on the dark AI/premium moments.
Shimmer headlineA slow light-sweep through the gradient accent phrase.
RestraintNo motion on the light/informational bands. Nothing flashing or bouncing. Cluster it where it reinforces the story.
Non-negotiable baseline

A page isn't "done" until it passes these

Because our pages often sell the very things below, they must practise them. This is the ship gate.

Self-hosted fonts (Lato + Source Sans Pro as woff2, preloaded) — no third-party font calls
Single H1, logical heading order, <main> landmark, WCAG-AA contrast — target 0 axe violations
Valid JSON-LD: Organization, WebSite, WebPage, BreadcrumbList, plus page-specific (Service/FAQPage)
llms.txt + robots.txt welcoming AI crawlers + a sitemap.xml (this is the AEO layer)
Full favicon set (ico + png + apple-touch) using the current brand app icon
A purpose-built 1200×630 Open Graph image + complete OG/Twitter tags
Security headers: HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy
Hosted on S3 + CloudFront (edge-cached, immutable asset caching, one-command deploy)
Get started

Starter & reference

Don't rebuild the rules from prose — start from the tokens. The starter CSS carries the palette, type scale, hero/nav, buttons, cards, marquee and all the motion (with reduced-motion handled).

Download refari-web-starter.css View the reference page — aivisibility.refari.co
<!-- 1. Fonts (self-host in production; CDN shown for prototyping) -->
<link href="https://fonts.googleapis.com/css2?family=Lato:wght@400;700;900&display=swap" rel="stylesheet">
<link href="https://fonts.googleapis.com/css?family=Source+Sans+Pro:300,400,600,700&display=swap" rel="stylesheet">
<!-- 2. The starter -->
<link rel="stylesheet" href="/refari-web-starter.css">
<!-- 3. Build with .topbar / .hero / .band / .card / .card-dark / .btn-primary … -->

The reference page (aivisibility.refari.co) is the canonical worked example of every rule on this page — copy patterns from its source.