Prompt 1,320 words Copy
# Design from Reference: ChartMogul Integrations Library
Create an original, high-fidelity visual design inspired by the reference. Prioritize composition, typography, colors, spacing, and component styling over technical implementation.
## Reference
- **Product:** ChartMogul
- **Category:** Integrations Library
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/o/4c86700c23e20c9ac342.webp)
- **Source:** https://chartmogul.com/integrations/
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 bright integrations directory uses a saturated blue hero, pale-blue section backgrounds, white logo tiles, and a regular four-column catalog.
- **Evidence:** The source image is 1440 × 6189 px and was inspected across five readable crops. Dimensions below refer approximately to source pixels; CSS scale is unverified.
- **Visual language:** Simple logo-centered cards and consistent category headings make a long technical directory easy to scan.
### Page composition
- **Header and hero:** White branding and navigation sit on blue, with login and a white trial action right. A large left headline, supporting paragraph, and white CTA balance a central-platform integration illustration on the right.
- **Data sources:** A centered heading and explanation introduce a pale-blue catalog. Separate groups cover maintained billing integrations, third-party integrations, and enrichment.
- **Resource cards:** Pairs of wider white text cards explain API and spreadsheet import/enrichment methods beneath the logo groups.
- **Data output:** A slightly lighter blue region repeats the heading/explanation pattern, followed by destination tiles, other integrations, and paired export/API cards.
- **Closing CTA:** A large rounded blue/teal gradient panel contains a centered white platform message and white trial button.
- **Footer:** Brand/contact/social content sits left, four grouped-link columns right, and a ruled legal/status row spans the bottom.
### Information hierarchy
- **Hero:** A bold three-line white headline dominates; a smaller paragraph explains import, enrichment, and output before the trial action.
- **Major sections:** Large centered Data Sources and Data Output headings distinguish the two halves of the directory.
- **Subgroups:** Left-aligned labels identify integration ownership or use. Logo/name tiles carry equal emphasis within each group.
- **API detail:** Wider cards use bold titles, short explanatory paragraphs, and bottom-aligned Learn more links.
- **Conversion:** Trial actions appear in the header, hero, and gradient closing panel with consistent white-button treatment.
### Typography
- **Family:** A clean sans serif appears throughout; exact identity is unverified.
- **Hero heading:** Approximately 44–46 px bold with 53–55 px line-height.
- **Section headings:** Around 38–40 px bold with 48 px leading. Introductory copy is approximately 18 px with 26 px line-height.
- **Subgroups and cards:** Group labels are around 18 px; detail-card headings are approximately 18 px semibold and body about 15–16 px with 22 px leading.
- **Tile labels:** Approximately 14 px gray text centered beneath logos.
- **Footer and CTA:** Footer links are about 13–14 px with open spacing; the closing message is approximately 50–54 px bold across two lines.
### Colors & surfaces
- **Measured palette:** Sampled source colors include pale blue #EAF5FD, white #FFFFFF, slightly stronger pale blue #DCEFFC, hero blue #3F9AF7, related blue #419BF7, and black #000000.
- **Semantic use:** Saturated blue grounds the hero; pale blues distinguish source/output catalog regions. White tiles and explanatory cards provide clear local surfaces.
- **Text:** Hero and closing-panel text is white; directory headings/body are black, with muted gray tile names.
- **Artwork:** The hero uses a dark-blue central mark, pale connecting paths, multicolor service logos, and small decorative dots.
- **Depth:** Most catalog tiles are flat with subtle rounding. Stronger gradient/depth appears in the hero illustration and final CTA panel.
### Components
- **Integration tiles:** Approximately 268 × 114 px, white, with 8 px radii. A bounded logo around 50 px occupies the upper center, with the name below.
- **Catalog grid:** Four equal columns with around 22–24 px gaps. Partial final rows retain the same alignment.
- **Custom tile:** A large gray plus and Create your own label use the same tile dimensions as branded services.
- **Detail cards:** Two equal cards span the grid width, approximately 560 × 260 px, with 34 px padding, bold heading, paragraph, and lower Learn more link.
- **Hero CTA:** A white rectangle approximately 228 × 60 px with 5–6 px radii, black uppercase label, and generous padding.
- **Closing panel:** Approximately 1200 × 445 px, with roughly 30 px corner radii and a teal-to-blue gradient.
- **Footer:** Narrow text columns, small black social icons, a partner badge, and legal/status links form a structured closing directory.
### Visual rhythm
- **Container:** Main catalog content spans roughly 1140 px with about 150 px side gutters.
- **Section spacing:** Large 100–140 px pauses distinguish headings and groups; cards repeat with tighter 22–24 px spacing.
- **Tile cadence:** Equal heights and centered logos normalize varied service identities.
- **Text cards:** Longer explanations introduce horizontal two-column breaks within the four-column logo rhythm.
- **Closure:** A large gap separates the final resource cards from the gradient CTA, followed by spacious footer columns and a broad lower margin.
### Responsive
- **Observed limit:** Only desktop is shown; actual breakpoints and integration-link behavior are unverified.
- **Recommended grid:** Reduce four columns to two and then one while preserving group labels and tile order.
- **Recommended hero:** Stack messaging and illustration, scale the headline fluidly, and simplify connectors when necessary.
- **Recommended detail cards:** Stack API/resource cards and let their height follow copy; retain clear link placement.
- **Recommended footer:** Reflow grouped links and legal items with 20–24 CSS px mobile gutters, keeping trial buttons comfortably tappable.
### Adaptation guidance
- **Preserve:** Keep the clear source/output taxonomy, consistent logo tiles, wide explanatory cards, and bright blue conversion framing.
- **Build:** Use reusable integration-tile, category-group, resource-card, and CTA components with shared spacing and logo bounds.
- **Assets:** Use authentic service marks and preserve their proportions. Treat the hero connector diagram as illustrative rather than a working integration interface.
- **Accessibility:** Give tiles descriptive link names, provide image alternatives, ensure focus visibility, and verify gray-label contrast.
- **Validate:** Confirm font, true CSS scale, long service names, responsive column changes, and catalog completeness. Listed integrations are observed screenshot content, not verified current availability.
## 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.
SaaSFrame
