Plain

Reference it for

• The bifurcated-colour headline as a brand device: split a hero H1 into two phrases, paint each in a different brand colour, let one element be the entire identity. Cheap to ship, hard to forget.
• A complete typographic system using just two weights (Regular 400, Medium 500). Hierarchy via size and colour, not weight contrast.
• The Geist Mono uppercase eyebrow label pattern: 13px / 19px / +0.195px tracking / brand-green colour, used to title every block. Reads as "system-built" without needing to ship a terminal screenshot.
• A cream-on-white card convention (#f9f6f1 and #fffbf5 rather than literal white) that softens an operational page and makes the green pop.
• A 128-token semantic colour layer where each token is a UUID (Framer's internal scheme) — too brittle to copy as-is, but the strategy of completely decoupling colour-roles from palette names is worth understanding.
• The single-easing motion contract: cubic-bezier(0.44, 0, 0.56, 1) (a smooth in-out sine) at 0.4s for every visible transition. One curve, one duration, everywhere.

Do not copy

• The Framer DOM structure. The captured page has one root div containing the entire 13,154px page with auto-generated UUID class names; there is no Astro-equivalent translation that makes sense for a Jiffi build.
• ABC Favorit Regular/Medium — licensed, framerusercontent-hosted, not portable. Lift the *idea* (one humanist sans, two weights only) on the client's own face.
• Loading ~30 font files (Inter Regular, Inter Variable, Inter Display in 9 weights × 2 styles × 7 subsets) when only 2 weights of one family are actually visible — a Framer performance cost the rebuild should not inherit.
• The bright #1ad379 green specifically — Plain-coded; a green-accent operational brand that copies this hex reads as a Plain clone.
• Termly cookie-consent JS and the dozen analytics scripts (Segment, Vector, Snitcher, Unify, Hubspot, Intellimize, Framer telemetry) loaded eagerly. Most Jiffi builds need at most 2-3 of these.