← Previous24 / 35Next →

Privacyboard Documentation Article

PrivacyboardPrivacy compliance, without the paperwork

Design with AI

Create a new design inspired by Privacyboard Documentation Article, with your own content.

1Content

2Fidelity to the reference

Keeps its visual language, rearranges freely around your content.

3Your brand Optional

Use the reference style

Brand nameColorsFontsGuidelines

4Output

Prompt 820 words

# Design from Reference: Privacyboard Documentation Article

Create an original, high-fidelity visual design inspired by the reference. Prioritize composition, typography, colors, spacing, and component styling over technical implementation.

## Reference

- **Product:** Privacyboard
- **Category:** Documentation
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/958f403b535f77188abb-1600.webp)
- **Source:** https://privacyboard.io/docs/cookie-banner/blocking-before-consent

Analyze the attached screenshot first. If no image is attached, open the screenshot link; if neither is accessible, ask for it rather than guessing.

## Visual Design Context

## Privacyboard — shared visual language
- **Theme:** Light, calm compliance tool. Cool off-white canvas #F6F6F9 with white cards (#FFFFFF, #FBFBFD for inner rows), thin #ECECF1 borders and almost no shadow; one violet accent carries every primary action.
- **Typography:** Sora for headings (page h1 Sora 28px w700, lh 32.2px, ls -0.784px, #262B3F; onboarding h1 Sora 24px w600), Inter for everything else (body Inter 14–14.5px w400, lh ~22px, #6B7185; labels 13px w500). Small uppercase mono eyebrows (ui-monospace 11px, wide tracking, violet) mark steps such as "NEXT STEP · 1 OF 6 DONE".
- **Colors:** Ink #262B3F, secondary #444A60 / #4B516A, muted #6B7185, placeholder #9AA0B4. Accent violet #6241D3 for primary buttons, selected chips and progress; tint #F1EFFF for selected chips and badges. Warning amber #FDF4E3 background with #A15C07 text ("to confirm", "TIA needed"); green for done states.
- **Components:** 240px left sidebar grouped by job (Workspace, Your data, Publish, Respond) with 1.5px-stroke icons, a workspace switcher card on top and the account at the bottom. Top bar with breadcrumb, a ⌘K search field and a privacy center status pill. Buttons 10px radius (violet filled or white outlined), pill chips 999px radius with a check when selected, tables in a white card with sortable headers and status pills, modals 14px radius over a dark scrim.
- **Layout:** Content column up to 1240px, 48px side padding, generous vertical spacing; each page opens with an h1, a one-line explanation and its actions on the right. A footer line repeats "Privacyboard drafts and guides; it is not legal advice."
- **Tone:** Plain, reassuring second-person copy that names the next action and the time it takes ("6 steps left, about 14 minutes"); legal terms are explained inline rather than assumed.

### Overall aesthetic
- **Mood:** Plain technical documentation in three columns with dark code blocks.
### Page composition
- **Layout:** Site header; left sidebar (~250px) with docs search and collapsible sections; central article (~590px) with breadcrumb, eyebrow, h1, intro and metadata; right "On this page" outline (~210px); footer.
### Typography
- **h1:** Sora 42px w500, lh 46.2px, ls -1.47px, #171717.
- **h2:** Sora 26px w550, lh 31.2px; h3 Sora 19px w600.
- **Body:** Inter 17px #55555D; inline code in ui-monospace on #EFEFF2.
### Colors & surfaces
- **Base:** #F7F7F8 page; active nav item on white; code blocks #16161A with #ECEEF3 text; violet links.
### Components
- **Sidebar:** Section titles with chevrons, nested links with a left rule.
- **Related cards:** Two white cards at the end of the article.
### Responsive
- **Mobile:** Sidebar and outline collapse, text full width, code blocks scroll horizontally.
### Adaptation guidance
- **Lesson:** In technical docs, give "what cannot be done" its own section next to how-to steps.

## Content

**Instructions:**

Generate realistic example content that fits the selected design reference.

Create appropriate headlines, descriptions, labels, buttons, and supporting copy based on the type of interface being designed.

If a product or business description is provided, use it to guide the content.

Otherwise, invent a plausible fictional SaaS product appropriate for the reference.

Keep the content concise, coherent, and visually balanced.

Do not present fictional statistics, customer names, or testimonials as verified facts.

## Design Direction

**Instructions:**

Use the reference screenshot as the main source of visual inspiration rather than a strict layout template.

Preserve its most distinctive design characteristics, such as typography, visual rhythm, color relationships, component treatments, and overall aesthetic.

Feel free to modify section arrangements, proportions, spacing, and individual components to better suit my content.

Introduce original design decisions where they improve usability, composition, or brand consistency.

The result should clearly reflect the reference's visual language without looking like a direct reproduction.

Follow the visual identity of the reference design.

Use its typography, color palette, component styling, and overall aesthetic as the primary design direction.

Do not introduce an unrelated visual identity.

## Output

**Instructions:**

Generate a high-fidelity visual mockup of the requested interface.

Present the design as a polished, realistic website or product UI screenshot.

Prioritize visual composition, typography, spacing, colors, alignment, and component details.

Use the available image-generation or visual-design capabilities.

Do not replace the mockup with source code, a written design specification, or a textual description.

If direct visual generation is unavailable, clearly explain the limitation.

## Constraints

- Use the actual screenshot as the primary visual reference.
- Preserve essential messaging and factual accuracy.
- Prioritize visual quality and consistency.
- Do not invent unsupported product claims.
- Adapt structure and copy length for visual balance.

Reference imageAttach it to your message: assistants can’t open image links.

Build it in

Opening a tool copies the screenshot so you can paste it with your prompt.

Visit live page

Tech Stack

React
Vercel

Added on

November 13, 2026

A help article with its limits stated

This Privacyboard documentation page, "Blocking before consent", explains how the cookie banner holds back known analytics and marketing tools. The intro says it covers which loading methods the banner can and cannot intercept, and "Updated 12 November 2026" and "3 min read" sit under it.

Technical detail in plain sections

Sections such as "Automatic blocking", "Mark your own scripts", "Removing cookies" and "What cannot be blocked" mix short paragraphs, bullet lists with inline code, and dark code blocks showing the script attributes to add.

Three columns of navigation and text

A left sidebar with a search field lists every documentation section, with "Cookie banner" expanded and the current page highlighted. An "On this page" outline sits on the right. The article ends with a two-question FAQ, a note that Privacyboard is a guidance tool, and cards linking to related pages.