Prompt 1,242 words Copy
# Design from Reference: OpenAI Customer Stories
Create an original, high-fidelity visual design inspired by the reference. Prioritize composition, typography, colors, spacing, and component styling over technical implementation.
## Reference
- **Product:** OpenAI
- **Category:** Customer Stories
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/o/48c02ee53bdbf8da3a03.webp)
- **Source:** https://openai.com/customer-stories/typeform
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:** A spare editorial customer story combines peach backgrounds, electric-blue branding and black text on white.
- **Capture evidence:** The image measures 1280 × 6514 pixels and was inspected in five portions through the decorative footer. Measurements below are approximate image pixels; CSS scale is unverified.
- **Visual language:** Large regular-weight typography, thin rules and broad white margins dominate; article content is not enclosed in cards.
### Page composition
- **Header:** A peach navigation bar aligns the blue brand at left, primary links across the middle and search/login/outlined action at right.
- **Hero:** A two-column title region places a small category label and large customer name left of a multiline summary.
- **Hero media:** A nearly full-width rectangular visual below shows a canyon-based conversational product example with a softly blurred outer image frame.
- **Article entry:** A thin rule introduces a metadata row with date, product link, topic links and a small bordered customer-logo square.
- **Article body:** A roughly 604px-wide text column begins around 233px from the left; a much wider pull quote breaks its width.
- **Later regions:** A peach video band interrupts white article text, followed by another product image, closing prose, a three-column related-story grid and a peach footer.
- **Footer detail:** Brand and grouped links precede legal/social links; horizontal blue stripes grow denser toward a solid blue bottom region.
### Information hierarchy
- **Hero roles:** The customer name is the largest title; the adjacent summary explains the story without duplicating that scale.
- **Article flow:** Short paragraphs use a consistent regular style and occasional underlined links.
- **Pull quote:** A very large multiline quotation and smaller bold attribution create the principal mid-article emphasis.
- **Media:** The video preview has a play marker, title and duration; the lower image demonstrates another conversational interface.
- **Related stories:** A serif section title contrasts with three image-led previews containing bold customer names and short summaries.
### Typography
- **Family:** A neutral sans-serif serves most content, with a contrasting serif for the related-stories heading. Exact font identities are unverified.
- **Hero name:** Approximately 72px, regular weight, around 80px line-height with slightly tight tracking.
- **Hero summary:** Approximately 28px with 34px line-height, regular weight.
- **Body:** Approximately 18px with 23–24px line-height and normal tracking.
- **Pull quote:** Approximately 46–48px, regular, around 52px line-height; attribution is approximately 18px bold.
- **Related heading:** Approximately 48px serif; story labels, footer links and metadata are around 18px.
### Colors & surfaces
- **Peach surface:** Sampled #E8C8B7 supplies hero, video band and footer regions.
- **Blue accent:** Sampled #0433FF supplies header/footer text, outlines and decorative stripes; nearby #0432FE occurs in rendered edges.
- **Reading surface:** Sampled #FFFFFF supports the article and related-story region.
- **Ink:** Sampled #000000 supplies article text and fine rules.
- **Media palette:** Sampled #938956 contributes to the olive-toned lower product visual; photographic colors remain within media assets.
### Components
- **Header action:** A compact rectangular blue outline with small corner radius includes a trailing external-link arrow.
- **Metadata row:** A fine black top rule spans the page, with information distributed across a multi-column grid.
- **Hero media:** Approximately 1232 × 694px with square outer corners; its inset product example has visibly rounded corners.
- **Video preview:** A roughly 604px-wide rectangular gradient preview is inset to the article column within a full-width peach band.
- **Pull quote:** Large black text sits directly on white without a border, background card or decorative quote icon.
- **Related previews:** Three equal columns use near-square images, small gaps and text directly beneath without enclosing borders.
- **Footer stripes:** Thin horizontal blue rules progressively increase in thickness and density near the bottom.
### Visual rhythm
- **Outer gutters:** Approximately 24px margins frame full-width hero and related content.
- **Reading inset:** The narrow body column leaves broad white space to its right and a stable left edge for text and smaller media.
- **Paragraph spacing:** Approximately 20–24px separates paragraphs; media and quotes use much larger 80–120px breaks.
- **Section alternation:** Peach bands punctuate long white reading areas, making major transitions clear.
- **Grid continuity:** Header, metadata, related stories and footer use consistent multi-column alignment.
### Responsive
- **Evidence limit:** Only one desktop capture is observed; navigation and video interactions are unverified.
- **Hero recommendation:** Stack customer name and summary, reduce display size and preserve clear category labeling on narrow screens.
- **Reading recommendation:** Use a fluid article column with around 20–24px mobile gutters and comfortable line-height.
- **Media recommendation:** Scale hero and inline media proportionally; prevent embedded interface labels from becoming the sole source of information.
- **Footer recommendation:** Stack link groups and related stories, retaining the decorative stripe treatment at an appropriate height.
### Adaptation guidance
- **Editorial system:** Reuse a two-column hero, narrow prose column, oversized quote and image-led related-content module.
- **Color discipline:** Keep blue primarily in branding and navigation; preserve black article text on white for sustained reading.
- **Media fidelity:** Treat product examples as static assets unless separate implementation evidence establishes their interaction.
- **Accessibility:** Use semantic quotation markup, descriptive media alternatives, accessible video controls and visible link focus.
- **Historical content:** Preserve the visual structure of this captured design without treating displayed product references as current product guidance.
## 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 image Attach it to your message: assistants can’t open image links. Open in ChatGPT ↗ Open in Claude ↗
Build it in Lovable ↗ v0 ↗ Figma Make ↗
Opening a tool copies the screenshot so you can paste it with your prompt.