7 references · 16 captured

FAQ

Question stacks, accordion-style FAQ blocks.

01 · Accordion

Native <details>

Native HTML, single-open behaviour. Affordance is a typographic + / -, not a chevron.

Questions

The ones we’re asked most often.

Is Inspo free?
Yes - open source, MIT, owned by Together AI. Free in every tier. The tiers differ in how much of the stack you run yourself.
How do I install the MCP server?
`npx inspo init` detects Claude Code, Cursor, Codex, and Zed configs and appends the server entry. It opens your browser once to authenticate the hosted instance.
Can I self-host?
Every dependency (Postgres, blob storage, the worker) has a free tier or local equivalent. The worker runs anywhere Chromium runs. See /about for the runbook.
Where does the catalogue come from?
Curated by hand from a seed list of sites. The worker captures desktop and mobile, extracts palette + type ramp + tech, runs a vision-LLM pass for tags, then waits for curator review.

02 · Two-column

Q-left, A-right

Every Q&A on display. Reads as a magazine interview, not a help-desk index.

FAQ

The ones worth answering out loud.

Why open source?: Because the reference layer should belong to the field, not a vendor. MIT, owned by Together AI, free to fork.
Why MCP and not a REST API?: Both, actually. The MCP wraps the same query surface a REST API exposes - the value is in the catalogue, not the protocol.
Who is this for?: Designers and the coding agents they work alongside. The website is for humans - browse, study, copy a DESIGN.md. The MCP is for agents - same catalogue, addressed by tool calls.
What about copyright?: Screenshots of public web pages for editorial commentary is well-established. We credit designers and respect takedown requests.

03 · Numbered

Ordered manifesto FAQ

Asked, briefly answered. Numbered prefix in mono - reads as a list of arguments.

Asked, briefly answered

Is the catalogue ever-growing?
Yes - but slowly. Curation is the moat, not coverage.
Can I submit a site?
Soon. v1 is curator-only; v2 opens an /extract endpoint with auth + rate-limiting.
Does it work offline?
The catalogue ships baked into the bundle as static JSON, so /screens and /sites render without a database. Search remains client-side.

04 · Search-led

Filter input + open list

Search beats accordion when the FAQ runs long. Filtered, empty, and focus states all handled.

Questions

Filter to what you’re actually asking.

Is Inspo free?: Yes - open source, MIT, free in every tier.
How do I install the MCP?: `npx inspo init` writes the server entry into your editor's config.
Can I self-host?: Every dependency has a free tier or local equivalent.
Where does the catalogue come from?: Curated by hand from a seed list, then captured by the worker.
What models does the worker use?: Together AI Gemma for tagging; Voyage-style embeddings for semantic search.
Does it work offline?: Catalogue ships as static JSON, so /screens renders without a DB connection.
How do I add a site?: Append it to apps/worker/src/seed-urls.ts and open a PR.
What about copyright?: Editorial commentary precedent is well-established. We credit and respect takedown requests.

05 · Category tabs

Sliced by audience

Questions sliced by audience (Designers, Engineers, Curators). Useful when the FAQ serves multiple roles.

Questions, sliced

Who’s asking.

Can I just browse without an account?: Yes. Everything in the gallery is public - no signup required.
Where do I find palettes?: Open any site detail page; the brand palette band shows the extracted swatches.

06 · Compact

Q-only with inline reveal

Q-only by default; click expands A inline. Dense scanning for short answers.

Brief answers

The short version of everything.

07 · FAQ + CTA

Closing conversion

Three Q&A rows followed by a quiet conversion strip. Converts readers who got most of the way through.

FAQ

Still asking, after all this.

Is the catalogue ever wrong?: Sometimes. Audit runs every few weeks; bad captures get re-shot or rejected. Open an issue if you find one.
Can I use this commercially?: Yes. MIT licence. Use the catalogue, the components, the worker - own your fork.
Will the schema change?: Slowly, and only with a migration path. Drizzle migrations live in packages/db/src/migrations.

Question we didn’t answer?

From the archive

The same pattern, cropped from real production sites.