Plausible Dashboard — Plausible Analytics

# Build brief — an original admin dashboard in the taste of Plausible Dashboard

> Reference: https://plausible.io/plausible.io · UIDiscovery: https://uidiscovery.com/sites/app-plausible-dashboard · captured 2026-09-22 at a 1440px desktop viewport (+ 390px iPhone shots)

## 1. Goal
Build an original admin dashboard for **[the user's brand]** that feels as considered as Plausible Dashboard — 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 Plausible Dashboard: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse Plausible Dashboard'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
- Plausible Dashboard (plausible.io): Developer Tools admin dashboard, dark, dashboard.
- 31 product screens captured in the browser — real product UI, not marketing pages.
- Type: one family (system sans-serif). Imagery: mostly abstract 3D / gradient art, some product UI screenshots/mockups.

## 4. Screens
Typical dashboard anatomy (confirm in the screenshots): sidebar or top nav, page header with title + primary action, KPI cards, a chart, a filterable/paginated table, and empty/loading/error states.


1. [Screen](https://uidiscovery.com/media/captures/app-plausible-dashboard/s-01.webp)
2. [Screen](https://uidiscovery.com/media/captures/app-plausible-dashboard/s-02.webp)
3. [Screen](https://uidiscovery.com/media/captures/app-plausible-dashboard/s-03.webp)
4. [Content](https://uidiscovery.com/media/captures/app-plausible-dashboard/ps-01-01.webp)
5. [Content](https://uidiscovery.com/media/captures/app-plausible-dashboard/ps-01-02.webp)
6. [Content](https://uidiscovery.com/media/captures/app-plausible-dashboard/ps-01-03.webp)
7. [Content](https://uidiscovery.com/media/captures/app-plausible-dashboard/ps-01-04.webp)
8. [Content](https://uidiscovery.com/media/captures/app-plausible-dashboard/ps-01-05.webp)
9. [Content](https://uidiscovery.com/media/captures/app-plausible-dashboard/ps-01-06.webp)
10. [Content](https://uidiscovery.com/media/captures/app-plausible-dashboard/ps-02-01.webp)
11. [Content](https://uidiscovery.com/media/captures/app-plausible-dashboard/ps-03-01.webp)
12. [Content](https://uidiscovery.com/media/captures/app-plausible-dashboard/ps-05-01.webp)
…and 19 more at https://uidiscovery.com/sites/app-plausible-dashboard.
Inner pages also captured (About, Sign up, Log in, Blog, Docs, Changelog, Contact, Security): https://uidiscovery.com/sites/app-plausible-dashboard?view=pages

## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#010000` | page background | — |
| foreground | `#ffffff` | body text, headings | 21.0:1 |
| accent | `#ffffff` | none captured — monochrome. Primary buttons invert (foreground fill, background text); add your brand colour only for small highlights | — |
| surface | `#000011` | cards, inputs, alternate bands | text on it 20.8:1 |
| muted | `#010011` | secondary text, borders | 1.0:1 — borders / large text only |

Captured palette: `#010000` `#000011` `#010011` `#ffffff` `#010011`. Roles are assigned automatically — sanity-check them against the screenshot. Keep the palette's *mood* (dark, neutral, desaturated) and proportions; swap the accent for the user's brand colour.

### Tokens
```css
:root {
  --background: #010000;
  --foreground: #ffffff;
  --accent: #ffffff;
  --surface: #000011;
  --muted: #010011;
  --font-heading: "Inter", ui-sans-serif, system-ui, sans-serif;
  --font-body: "Inter", 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: **Inter** (Google Fonts) — reference uses system sans-serif. The reference uses the system stack; Inter (or plain system-ui) keeps that neutral feel.
- 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.5rem, 5vw, 4.25rem), 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.

### Shape, depth & theme
On dark, separate layers with 1px borders at ~8–12% white and soft glows instead of drop shadows; dense but calm: 8px radii on cards, 1px borders, subtle shadow only on overlays (menus, dialogs). Read exact corner radius, border and shadow treatment from the screenshots. Dark-first; for a light mode swap background ↔ foreground, lighten the surface, keep the accent and re-check contrast.

## 6. Imagery plan

Best guess: mostly **abstract 3D / gradient art**, some product UI screenshots/mockups (dark, neutral, desaturated, Developer Tools). 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. Screen, 2. Screen, 3. Screen → product UI
- Developer Tools sections with many image elements — most likely product UI screenshots/mockups plus icons. Count: one consistent treatment across these sections. Aspect: 4:3. Look first: [ref 1](https://uidiscovery.com/media/captures/app-plausible-dashboard/s-01.webp) [ref 2](https://uidiscovery.com/media/captures/app-plausible-dashboard/s-02.webp) [ref 3](https://uidiscovery.com/media/captures/app-plausible-dashboard/s-03.webp)
- **Generate** — `Minimal empty-state illustration for a developer tools web app: one simple object or scene, flat shapes, palette #010000, #ffffff, #000011, lots of white space, centred, friendly. Aspect ratio 4:3. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.`
- App screens need little imagery: build the UI in code with realistic sample data; use initials or generated avatars (never real people's photos without consent), your own product thumbnails, and one consistent empty-state illustration style (prompt above).

### Slot 2 · 4. Content, 5. Content, 6. Content, 7. Content, 8. Content, 9. Content, 10. Content, 11. Content, 12. Content → abstract 3D / gradient (uncertain)
- Dark Developer Tools section with a few graphics — typically abstract 3D/gradient art or a product shot. Count: one consistent treatment across these sections. Aspect: 4:5. Look first: [ref 1](https://uidiscovery.com/media/captures/app-plausible-dashboard/ps-01-01.webp) [ref 2](https://uidiscovery.com/media/captures/app-plausible-dashboard/ps-01-02.webp) [ref 3](https://uidiscovery.com/media/captures/app-plausible-dashboard/ps-01-03.webp) [ref 4](https://uidiscovery.com/media/captures/app-plausible-dashboard/ps-01-04.webp)
- **Stock** — “abstract dark gradient 3d”: [Unsplash](https://unsplash.com/s/photos/abstract-dark-gradient-3d?orientation=portrait) · [Pexels](https://www.pexels.com/search/abstract%20dark%20gradient%203d/?orientation=portrait) · [Pixabay](https://pixabay.com/images/search/abstract%20dark%20gradient%203d/?orientation=vertical)
- **Generate** — `Abstract 3D render: soft, glossy glass-like shapes and a smooth gradient in #010011 and #000011 on a #010000 background. Lighting: low-key, moody directional light with deep shadows; neutral, desaturated tone. Minimal and calm, generous negative space on one side for text. Aspect ratio 4:5. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.`


### 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: low-key, moody directional light with deep shadows. Neutral, desaturated colour grade that sits on #010000, #ffffff, #000011. 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 dark” on Unsplash](https://unsplash.com/s/photos/abstract-gradient-mesh-dark?orientation=landscape) (same query works on Pexels/Pixabay)
- **illustration** — generate `Flat vector illustration: abstract gradient mesh, friendly simplified shapes, limited palette of #010000, #ffffff, #000011 plus one soft neutral, plenty of empty background, consistent line weight, neutral, desaturated mood. Aspect ratio 16:9. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“technology flat illustration” on Unsplash](https://unsplash.com/s/photos/technology-flat-illustration?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 navigation shell first, then each screen, 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/app-plausible-dashboard/tokens · kit https://uidiscovery.com/api/v1/sites/app-plausible-dashboard/kit · MCP `get_design_brief({ slug: "app-plausible-dashboard" })`, `get_image_plan({ slug: "app-plausible-dashboard" })`. Cite the reference as https://uidiscovery.com/sites/app-plausible-dashboard.