← Previous30 / 38Next →

Conduktor Account Setup

ConduktorEnterprise Apache Kafka platform

Design with AI

Create a new design inspired by Conduktor Account Setup, 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 720 words

# Design from Reference: Conduktor Account Setup

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

## Reference

- **Product:** Conduktor
- **Category:** Account Setup
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/7c8bd0343d9fcfd35237-1600.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

- **Style:** Deployment-choice onboarding page with white cards, violet actions, and a pale-lavender grouping surface.

### Page composition

- **Canvas:** 2880 × 1876 image px; CSS estimates assume an unverified 2× capture.
- **Top:** Brand at left and centered usage question.
- **Choices:** Desktop card separate at left; Cloud and Self-hosted grouped within large lavender panel.
- **Featured:** Self-hosted outlined in violet with Recommended top ribbon.
- **Footer:** Legal links, social icons, status pill, security badge, and help control.

### Information hierarchy

- **Primary:** Usage question and three deployment choices.
- **Recommendation:** Violet outline/ribbon highlights Self-hosted.
- **Actions:** Download, Start trial, and Free version/Request trial.
- **Audience:** Small uppercase monospaced captions explain each option.

### Typography

- **Family:** Neutral sans serif; exact family unverified.
- **Question/card titles:** Approximately 32 CSS px, bold.
- **Body:** Approximately 14px with 24px line-height.
- **Buttons:** Approximately 14px, bold.
- **Audience captions:** Approximately 12px monospace, uppercase.
- **Precision:** Values and 2× scale are estimates.

### Colors & surfaces

- **Canvas/cards:** #FFFFFF.
- **Grouping panel:** #F1F0FF.
- **Violet:** #4F3EEF.
- **Primary text:** #1B1524.
- **Additional pale shades:** #F0EFFF and #EFEEFE.
- **Secondary text:** Muted gray-violet.
- **Precision:** Colors sampled from screenshot.

### Components

- **Cards:** Approximately 395 × 390 CSS px under assumed 2×, small rounded corners, diffuse shadow.
- **Featured card:** Strong violet border and full-width violet header strip.
- **Actions:** Wide low-height rectangular buttons; outline variant for Request trial.
- **Audience caption:** Framed between fine dotted rules.
- **Footer status:** Small green dot and operational text.

### Visual rhythm

- **Alignment:** Card headings and actions use repeated insets.
- **Spacing:** Generous title-to-choice gap and broad lower margin.
- **Grouping:** Lavender panel communicates shared web-based UI options.
- **Density:** Compact footer balances large decision cards.

### Responsive

- **Observed:** Desktop only.
- **Recommendation:** Stack choices, keep recommendation attached to its card, and wrap action pairs.
- **Footer:** Allow legal/status groups to wrap.

### Adaptation guidance

- **Preserve:** Clear deployment comparison, audience cues, and recommended-state treatment.
- **Content:** Use supplied capabilities, trial terms, and deployment options.
- **Behavior:** Download/trial outcomes are not demonstrated.

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