← Previous8 / 15Next →

Unabyss FAQ Page

UnabyssShared memory for every AI tool you use: one live context from your apps, served to Claude, ChatGPT and Cursor over MCP.

Design with AI

Create a new design inspired by Unabyss FAQ Page, 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 761 words

# Design from Reference: Unabyss FAQ Page

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

## Reference

- **Product:** Unabyss
- **Category:** FAQ Page
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/b26e5d15143aaf8bfb25-1600.webp)
- **Source:** https://unabyss.com/faq

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

## Unabyss — shared visual language

- **Theme**: dark-only marketing site. Near-black warm background (#191817), cards one step lighter (~#1F1E1C) with 1px hairline borders (white at ~8% opacity) and 16–20px radii.
- **Typography**: Lexend throughout. Headlines 600 weight, ~60px on desktop, tight tracking; a two-line hero where the second line drops to a muted grey (~#8A8784) for contrast. Body copy 16–17px, light grey, generous line height. Small uppercase labels with very wide letter spacing ("WORKS WITH", "BACKED BY"); wordmark set in spaced capitals.
- **Accent**: a restrained warm gold/amber (#E8B33A-ish) used for highlight strokes, glowing rings, pill outlines ("confidential", "You own it") and connector lines; a green status dot for "In sync".
- **Components**: pill-shaped floating nav bar with a separate pill logo chip; white solid pill CTAs with a ↗ arrow icon; dark rounded logo tiles for integrations (Claude, ChatGPT, Cursor, Gmail, Slack, Notion, GitHub…); tag chips; mini UI mock cards ("Your context", "Unabyss · MCP") built from bars and status labels rather than screenshots.
- **Layout**: centered hero, then bento grids of feature cards mixing a short heading, one-line copy and an illustrative widget; inline brand icons placed inside headlines.
- **Tone**: calm, technical, confident; short declarative headings, developer-friendly vocabulary (MCP, context, memory).

### Overall aesthetic

- **Style:** Calm, narrow-column FAQ page on the dark brand canvas; structure comes from group headings and evenly spaced accordion rows.

### Page composition

- **Header:** Eyebrow, centered 56px H1, short intro, compact search field aligned to the column.
- **Groups:** Four sections with left-aligned 30px titles, each a stack of 4–7 accordion rows in a ~760px column.
- **End:** Amber-outlined support card with icon label, title, copy and two buttons; footer.

### Typography

- **Scale:** H1 56px/600 (-0.67px), group titles 30px/600, questions 16px/500, body 16px/300.

### Colors & surfaces

- **Backgrounds:** #0F0F0F/#191817; rows slightly lighter with hairline borders and 12px radii.
- **Accent:** #FCD34D/#FEF3C7 for the eyebrow and support card outline.

### Components

- **Accordion row:** Full-width rounded row, question left, chevron right, 8px gap between rows.
- **Support card:** 24px radius, amber outline, white pill plus ghost pill buttons.

### Responsive

- **Mobile:** Same single column at full width; buttons in the support card stack.

### Adaptation guidance

- **Reuse:** Group questions by user journey stage and finish with a human contact card rather than a generic CTA.

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

Visit live page

Tech Stack

Cloudflare

Added on

November 12, 2026

A centered FAQ grouped by topic

The FAQ page uses a centered 56px headline and a short intro, then a small search field, followed by four groups (Getting Started, How It Works, Permissions & Privacy, Using Unabyss) laid out in a narrow single column for easy scanning.

Accordion rows with plain questions

Each question sits in its own dark rounded row with a chevron, phrased the way users would ask it ("Is my data safe?", "Can I export my context files?"), and group titles are left-aligned above each stack.