← Previous4 / 23Next →

Campsite Dashboard

CampsiteWhere teams share work in progress

Design with AI

Create a new design inspired by Campsite Dashboard, 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 599 words

# Design from Reference: Campsite Dashboard

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

## Reference

- **Product:** Campsite
- **Category:** Dashboard
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/o/40b2b22db1d0bef14a72.webp)

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

### Overall aesthetic

- **Character:** Minimal team feed with quiet navigation, a centered composer and a large image-led post.

### Page composition

- **Capture:** 1440 × 821 screenshot pixels; estimated CSS scale approximately 1×.
- **Structure:** Left workspace/project sidebar, Latest top bar, narrow central composer and one large post card; view toggles sit upper right.

### Information hierarchy

- **Priority:** Composer invites contribution; post image dominates the feed, followed by author/time, short caption, tags and interaction icons.

### Typography

- **Family:** Sans serif; exact family unverified.
- **Estimated CSS sizes:** Interface/body 16px, metadata 14px and sidebar labels 14px.

### Colors & surfaces

- **Measured palette:** Canvas #FAFAFA, white #FFFFFF, black #000000 in post artwork and control grays #F5F5F5/#F2F2F2/#F6F6F6.
- **Accents:** Mint initial avatars and pale blue work-in-progress tag.

### Components

- **Elements:** Workspace switcher, New post, project list, composer input, wide media card, overflow menu, tag chips and comment/reaction buttons.
- **Estimated geometry:** Sidebar 240px, feed approximately 736px wide, 8px card radius, 48px composer height and 16px post padding.

### Visual rhythm

- **Spacing:** Generous horizontal margins isolate the feed; compact post metadata sits beneath a roughly 16:9 image.

### Responsive

- **Suggested adaptation:** Collapse sidebar and let feed/media fill available width with modest gutters. Mobile behavior is not shown.

### Adaptation guidance

- **Transfer:** Preserve media-first posts, lightweight metadata and a clear contribution prompt. Adapt imagery to actual team updates.

## 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.