← Previous12 / 27Next →

Respan Documentation

RespanThe fastest open-source AI gateway, with built-in observability and evals

Design with AI

Create a new design inspired by Respan Documentation, 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 834 words

# Design from Reference: Respan Documentation

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

## Reference

- **Product:** Respan
- **Category:** Documentation
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/bec23e2caa5fc2d3e52a-1600.webp)
- **Source:** https://www.respan.ai/docs/documentation/overview

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

## Respan — shared visual language

- **Theme**: dark, developer-first marketing site. Near-black page (#000000 / #1E1E23 surfaces, #2E2E33 hairline borders) with a thin announcement bar ("Launching the open-source gateway") in letter-spaced type above a slim top nav (logo "[ . ] Respan", Product, Models, Docs, Pricing, Resources; GitHub stars, "Book a demo", white "Dashboard").
- **Typography**: Inter everywhere. Hero H1 72px/600 with very tight tracking (-3.24px); page H1 64px/600 (-1.6px); content-page H1 40px/500 (-1px). Body 14–16px in light greys (#F9FAFC, #B1B3BC). Roboto Mono for code samples, numbers and small labels.
- **Colors**: monochrome greys with saturated accents used inside product mocks and customer cards: blue #2679F3 / #1B3FE0, green #0D7C5C, purple #8F74E0, pink and red for charts; periwinkle #6483F0 for highlighted plans.
- **Components**: 36px buttons with 6px radius (white primary, #1E1E23 secondary); 12px-radius cards on #1E1E23; live code blocks with a "Copy" button and syntax colors; logo strips; testimonial cards with photos on bright color fills; a giant pixelated "[ . ] Respan" wordmark above a dense multi-column footer.
- **Layout**: centered ~1200px content, left-aligned heroes on product pages, long scrolling pages alternating code, product mocks and metric callouts ("Up to 70% off tokens", "1,000+ models").
- **Tone**: technical and blunt, numbers first ("The fastest OSS AI gateway", "Built for AI agents. Break less. Ship more.").

## Respan app (platform.respan.ai) — product UI

- **Theme**: dark app, page #151519, panels #1E1E23, raised #26262B, borders #2E2E33; text #F9FAFC and #B1B3BC; accent periwinkle #6483F0.
- **Typography**: Inter for UI (13–14px), "Respan Mono" for numbers, model ids and code.
- **Sidebar**: project switcher ("saasframe"), a "Finish setup 2 of 3" checklist card, then Inbox, API keys, Gateway, Models, Metrics, Logs, Users & identifiers, Playground, Prompts, Datasets, Red teaming, Settings; an "Open source" GitHub card and a "Credits" card ($0.00, "Auto reload off") at the bottom; a status bar with Community, Docs, Book a demo, version and "Ask Respan agent".
- **Components**: 28px compact buttons with 4px radius, filter chips, isometric line illustrations for empty states, data tables with tiny mono numbers.

### Overall aesthetic
- **Style:** dark self-hosted documentation (Nextra) matching the marketing site.

### Page composition
- **Top bar:** logo, "Docs", search, "Ask AI", "Live demo".
- **Body:** left nav, content column with H1, lead, prompt block, 2x2 cards, feedback line, footer links.

### Typography
- **H1:** Inter 40px/46px w600, -1.4px. **Body:** 16px/27.2px.
- **Code/prompt:** Roboto Mono 13px.

### Colors & surfaces
- **Cards:** #1E1E23 with 8–12px radius; nav active item highlighted in grey.

### Components
- **Prompt block:** mono text with "Copy prompt".
- **Link card:** icon, title, one line.

### Responsive
- **Mobile:** sidebar collapses into a menu; cards stack.

### Adaptation guidance
- **Lesson:** give agents a one-line setup prompt on the first docs page, next to the human quickstart.

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

Vercel

Added on

November 12, 2026

Docs that start with a prompt to copy

Respan's documentation overview, "Quickstart", describes the product in one line and then offers a "Copy prompt" block: "Set up Respan for me: fetch and follow this guide", meant to be pasted into a coding agent.

Four product cards

Gateway, Observability, Security and Span-02 each get a short card ("Call 1000+ models through one API.") linking to their section.

Classic three-part docs layout

A left sidebar with sections (Quickstart, MCP/CLI, Gateway, Observability, Admin, Changelog), the content column with "Copy page", and top links to API reference, GitHub and Dashboard, plus search and "Ask AI".