Overflow — Overflow 2026

# Build brief — an original marketing website in the taste of Overflow

> Reference: https://overflow.sui.io · UIDiscovery: https://uidiscovery.com/sites/overflow · captured 2026-09-22 at a 1440px desktop viewport (+ 390px iPhone shots) · [full page](https://uidiscovery.com/media/captures/overflow/full.webp) · [scroll video](https://uidiscovery.com/media/captures/overflow/preview.mp4)

## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as Overflow — same structure, rhythm and polish, entirely new identity and content.

## 2. Originality rules
- Build an ORIGINAL design for the user's own brand in the same *taste* as Overflow: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse Overflow's logo, name, product imagery, illustrations, icons, screenshots or copy. Write new copy for the user's product.
- If the user hasn't said what their product is, ask first (or use clearly marked placeholders like [Brand], [Product], [Audience]).
- Reference screenshots are for looking at, not for embedding or tracing.

## 3. The taste, in short
- Overflow (overflow.sui.io): Crypto & Web3 marketing website, light, award winner.
- 8 sections: Hero → Features → Logo cloud → Statement → FAQ → Content.
- Spacing: long, content-rich sections (median ≈1145px tall at 1440).
- Hero headline: 3 words — short and punchy; keep yours under ~9.
- Type: one family (TWK Everett). Imagery: mostly product UI screenshots/mockups, some illustration.

## 4. Page structure (top to bottom)

### 1. Hero — state what the product is and for whom in one glance, and offer the primary action.
- Layout: headline-led stack: eyebrow → H1 → supporting line → actions, with a visual beside or below. Tall, ≈1.9 screens (1700px at 1440), own light band #f7f7f7; 29 image elements (icons, logos, product UI — not 29 photos); primary + secondary button.
- Slots: Eyebrow / announcement pill (optional); H1 (~3 words, like the reference); Supporting line, 1–2 sentences; Primary + secondary action; Hero visual (see image plan).
- Topic (tone/length only — never reuse): “Sui Overflow 2026”
- [Screenshot](https://uidiscovery.com/media/captures/overflow/s-01.webp) · imagery: slot 1

### 2. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. About one full screen (1145px at 1440), own dark band #000f1d; 3 image/graphics; no interactive controls; 6 headings → ~5 items under a title.
- Slots: Section title (~5 words, like the reference); 5 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “Why join Sui Overflow 2026?”
- [Screenshot](https://uidiscovery.com/media/captures/overflow/s-02.webp) · imagery: slot 1

### 3. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. Tall, ≈1.6 screens (1396px at 1440), own light band #f2eee4; 33 image elements (icons, logos, product UI — not 33 photos); 4 text links instead of buttons; 6 headings → ~5 items under a title.
- Slots: Section title (~3 words, like the reference); 5 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Tracks”
- [Screenshot](https://uidiscovery.com/media/captures/overflow/s-03.webp) · imagery: slot 1

### 4. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. Tall, ≈1.9 screens (1700px at 1440), own light band #f7f7f7; 41 image elements (icons, logos, product UI — not 41 photos); 1 text link instead of buttons; 6 headings → ~5 items under a title.
- Slots: Section title (~3 words, like the reference); 5 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Prizes”
- [Screenshot](https://uidiscovery.com/media/captures/overflow/s-04.webp) · imagery: slot 1

### 5. Logo cloud — borrow trust from recognisable customers or partners.
- Layout: a single row or wall of monochrome marks with a one-line lead-in. About one full screen (971px at 1440), own dark band #000f1d; 16 image elements (icons, logos, product UI — not 16 photos); one primary button, 16 links (link lists / navigation).
- Slots: One-line lead-in (e.g. “Trusted by…”); 6–10 monochrome customer/partner marks (your own, with permission).
- Topic (tone/length only — never reuse): “Sponsors”
- [Screenshot](https://uidiscovery.com/media/captures/overflow/s-05.webp)

### 6. Statement — a large-type moment that sets tone and pace.
- Layout: oversized typography with lots of space. Half to one screen (624px at 1440), own light band #f7f7f7; 28 image elements (icons, logos, product UI — not 28 photos); primary + secondary button, 26 links (link lists / navigation).
- Slots: Heading (~6 words, like the reference); Body copy; Supporting visual (see image plan); Primary + secondary action.
- Topic (tone/length only — never reuse): “Two years of Sui’s flagship hackathon”
- [Screenshot](https://uidiscovery.com/media/captures/overflow/s-06.webp) · imagery: slot 1

### 7. FAQ — remove the last objections before the call to action.
- Layout: question list with disclosure (accordion), often two columns on desktop. About one full screen (917px at 1440), own light band #f7f7f7; no images (type-led); 7 buttons (tabs, toggles or per-card actions); 6 headings → ~5 items under a title.
- Slots: Title; 5 question/answer pairs; Link to support/contact.
- Topic (tone/length only — never reuse): “FAQ”
- [Screenshot](https://uidiscovery.com/media/captures/overflow/s-07.webp)

### 8. Content — supporting content that deepens one idea.
- Layout: text + media block. Compact band (322px at 1440), own light band #e9ccff; 5 images/icons (a set of cards or a small gallery); form with 3 fields, one primary button.
- Slots: Heading (~4 words, like the reference); Body copy; Supporting visual (see image plan); One primary action.
- Topic (tone/length only — never reuse): “Follow @suidevelopers for updates”
- [Screenshot](https://uidiscovery.com/media/captures/overflow/s-08.webp) · imagery: slot 2

Inner pages also captured (Security): https://uidiscovery.com/sites/overflow?view=pages

## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#7c838a` | page background | — |
| foreground | `#000f1d` | body text, headings | 5.0:1 |
| accent | `#00bfff` | primary buttons, links, highlights — sparingly | 1.8:1 ⚠ not for text; use as a fill with #111111 text (8.9:1) |
| surface | `#61686d` | cards, inputs, alternate bands | text on it 3.4:1 |
| muted | `#ffffff` | secondary text, borders | 3.8:1 — borders / large text only |

Captured palette: `#7c838a` `#000f1d` `#00bfff` `#f7f7f7` `#ffffff` `#61686d`. Section bands top→bottom: `#f7f7f7` → `#000f1d` → `#f2eee4` → `#e9ccff`. Roles are assigned automatically — sanity-check them against the screenshot. Keep the palette's *mood* (light, cool) and proportions; swap the accent for the user's brand colour.

### Tokens
```css
:root {
  --background: #7c838a;
  --foreground: #000f1d;
  --accent: #00bfff;
  --surface: #61686d;
  --muted: #ffffff;
  --font-heading: "Hanken Grotesk", ui-sans-serif, system-ui, sans-serif;
  --font-body: "Hanken Grotesk", ui-sans-serif, system-ui, sans-serif;
  --radius: 12px; /* calibrate from the screenshot */
}

/* Tailwind v4 — in globals.css after @import "tailwindcss"; */
@theme {
  --color-background: var(--background);
  --color-foreground: var(--foreground);
  --color-accent: var(--accent);
  --color-surface: var(--surface);
  --color-muted: var(--muted);
  --font-heading: var(--font-heading);
  --font-sans: var(--font-body);
}
```

### Typography
- Headings: **Hanken Grotesk** (Google Fonts) — reference uses TWK Everett. “TWK Everett” is a licensed face — use Hanken Grotesk (or Inter) as the free stand-in, or license the original.
- Body: same family — a single-family system; create contrast with size and weight, not a second face.
- Scale (starting point, sizes weren't measured — calibrate against the 1440px screenshot): display clamp(2.75rem, 6vw, 5rem), h2 clamp(1.75rem, 3vw, 2.5rem), h3 1.25rem, body 1rem–1.125rem / 1.6, small 0.875rem. Headings: tight tracking (-0.02em), line-height 1.05–1.15.

### Spacing & rhythm
Sections run ≈1145px tall at 1440 (median; range 322–1700px, captures cap at 1700px) — long, content-rich chapters. Start with 96–128px vertical padding per section on desktop and about two-thirds of that on mobile. The background changes 6 times down the page — use band changes to mark chapters. 8px spacing grid, 1200–1280px max content width, 24px (mobile) / 32–48px (desktop) gutters.

### Shape, depth & theme
Expressive layout and motion are part of the appeal — study the scroll video, but keep motion subtle and respect prefers-reduced-motion. Read exact corner radius, border and shadow treatment from the screenshots. Light-first; for a dark mode use a near-black (not #000) background, ~90% white text, lift surfaces with lightness not shadow, re-check the accent.

## 6. Imagery plan

Best guess: mostly **product UI screenshots/mockups**, some illustration (light, cool, Crypto & Web3). Inferred from element counts, colours and industry — not from the pixels — so open the linked screenshots and match the real style before sourcing anything.

### Slot 1 · 1. Hero, 2. Features, 3. Features, 4. Features, 6. Statement → product UI (uncertain)
- Crypto & Web3 sections with many image elements — most likely product UI screenshots/mockups plus icons. Count: one consistent treatment across these sections. Aspect: 16:9 full-bleed (or 21:9). Look first: [ref 1](https://uidiscovery.com/media/captures/overflow/s-01.webp) [ref 2](https://uidiscovery.com/media/captures/overflow/s-02.webp) [ref 3](https://uidiscovery.com/media/captures/overflow/s-03.webp) [ref 4](https://uidiscovery.com/media/captures/overflow/s-04.webp)
- **Stock** — “laptop blank screen minimal desk”: [Unsplash](https://unsplash.com/s/photos/laptop-blank-screen-minimal-desk?orientation=landscape) · [Pexels](https://www.pexels.com/search/laptop%20blank%20screen%20minimal%20desk/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/laptop%20blank%20screen%20minimal%20desk/?orientation=horizontal)
- **Generate** — `Product-shot backdrop for a UI screenshot: smooth light gradient from #7c838a to #61686d with a soft #00bfff glow behind the centre, subtle floor shadow, empty centre area where a screenshot will be placed. Lighting: soft natural daylight, airy and high-key. Aspect ratio 16:9. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people. No UI elements.`
- Build the UI itself in HTML/CSS with realistic sample data from YOUR product (or screenshot your real app). Don't generate UI as an image and don't reuse the reference's screenshots. Stock/AI is only for the backdrop or device frame.

### Slot 2 · 8. Content → illustration (uncertain)
- Light Crypto & Web3 section with a few graphics — illustration, icon art or a product shot. Count: a set of ~5 in one consistent style. Aspect: 4:5. Look first: [ref 1](https://uidiscovery.com/media/captures/overflow/s-08.webp)
- **Stock** — “technology flat illustration”: [Unsplash](https://unsplash.com/s/photos/technology-flat-illustration?orientation=portrait) · [Pexels](https://www.pexels.com/search/technology%20flat%20illustration/?orientation=portrait) · [Pixabay](https://pixabay.com/images/search/technology%20flat%20illustration/?orientation=vertical)
- **Generate** — `Flat vector illustration: abstract gradient mesh, friendly simplified shapes, limited palette of #e9ccff, #00bfff, #61686d plus one soft neutral, plenty of empty background, consistent line weight, cool mood. Aspect ratio 4:5. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.`
- Uncertain: this could equally be photography, a product shot or icon art — open the reference screenshots and match what you see.

- **Logos** — 5. Logo cloud: Never generate or stock-source logos. Use your real customers'/partners' marks with permission (monochrome, equal height), or neutral wordmark placeholders until you have them. Integration icons: each tool's official brand kit (Simple Icons is a quick start; trademarks still apply).
- **No imagery (type-led)** — 7. FAQ: No imagery needed — type, spacing and colour do the work. If the screenshot shows a background graphic, rebuild it in CSS (gradient, grid, noise) or a short muted video, not a stock photo.

### If the screenshots show a different style
Open the refs first and name what you actually see (photo / product UI / illustration / abstract gradient or 3D / type only). If it differs from the guess, switch routes — UI is built in code, type-only needs no image, otherwise:
- **photography** — generate `Photograph: abstract gradient mesh. Composition: wide shot, subject off-centre to one side, generous clean negative space for the headline. Lighting: soft natural daylight, airy and high-key. Cool colour grade that sits on #f7f7f7, #00bfff, #61686d. Photorealistic, natural textures, shallow depth of field, 35mm lens. Aspect ratio 16:9. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“abstract gradient mesh” on Unsplash](https://unsplash.com/s/photos/abstract-gradient-mesh?orientation=landscape) (same query works on Pexels/Pixabay)
- **abstract 3D / gradient** — generate `Abstract 3D render: soft, matte clay shapes and a smooth gradient in #00bfff and #ffffff on a #7c838a background. Lighting: soft natural daylight, airy and high-key; cool tone. Minimal and calm, generous negative space on one side for text. Aspect ratio 16:9. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“abstract gradient 3d” on Unsplash](https://unsplash.com/s/photos/abstract-gradient-3d?orientation=landscape) (same query works on Pexels/Pixabay)

- **Licences:** Unsplash and Pexels images are free for commercial use under their own licences; Pixabay under the Pixabay Content License. Check each image's page before use, credit the photographer when asked (good practice anyway), and skip images showing logos, trademarks, branded products or identifiable people without a release.
- **AI generation:** the prompts work with any image model (GPT Image, Imagen, Flux, Midjourney, Firefly, SDXL…) — check its commercial-use terms. Never put the reference brand's name or “in the style of <brand>” in a prompt.
- **Never** download, trace or re-host the reference's own images, illustrations, product shots or logos.

## 7. Build steps
1. Confirm brand, product, audience and the primary action with the user.
2. Set up the tokens (CSS variables / Tailwind @theme) and load the fonts.
3. Build the sections in order, mobile-first, with each reference screenshot open.
4. Write original copy for every slot — match length and tone, never the words.
5. Source every image via the imagery plan (stock or generated); compress it and record credits.
6. Run the checklist at 390 / 768 / 1440px and fix what fails.

## 8. Acceptance checklist
- [ ] Responsive at 390px, 768px and 1440px — no horizontal scroll, tap targets ≥ 44px on mobile.
- [ ] Colour contrast WCAG AA: 4.5:1 body text, 3:1 large text and UI; visible focus states; full keyboard navigation.
- [ ] Semantic HTML: one <h1>, ordered headings, landmarks (header/nav/main/footer), labelled form fields, alt text on meaningful images.
- [ ] Performance: modern image formats with width/height set, lazy-load below the fold, ≤ 2 font families with font-display: swap, LCP < 2.5s.
- [ ] prefers-reduced-motion respected; animations under ~300ms and never blocking content.
- [ ] Originality: no copied logos, images, illustrations or copy from the reference; every image licensed or generated; credits recorded.

## 9. If you use Next.js + Tailwind
Paste the @theme block into globals.css, load fonts with next/font/google, make each section a server component in components/sections/, use next/image with explicit sizes, and keep client components for interactive bits only (menus, toggles, accordions).

---
More: tokens https://uidiscovery.com/api/v1/sites/overflow/tokens · kit https://uidiscovery.com/api/v1/sites/overflow/kit · MCP `get_design_brief({ slug: "overflow" })`, `get_image_plan({ slug: "overflow" })`. Cite the reference as https://uidiscovery.com/sites/overflow.