Are.na — Plain-Document Manifesto

A homepage that reads like a typed memo: small black text, lettered lists, floating screenshots, and acres of whitespace.

Source capture · 2026-09-05Open full image ↗

Design notes

Mood

Anti-marketing sincerity. A quiet, literate document addressed to a reader, not a funnel — closer to a letter than a landing page.

Colors

White canvas, small near-black sans text, mid-grey secondary text, one dark-indigo button; floating screenshots supply faint desaturated colour. Effectively monochrome.

Type

One small clean sans held at essay sizes throughout — bolded run-in heads ('How it works', 'The secret'), lettered lists (a. b. c.), numbered manifesto items, underlined inline links. Hierarchy from weight and indentation, never from scale.

Layout

A narrow centered text column with an enormous top margin and no hero. Product screenshots break the column and float free with soft ambient shadows, annotated by quiet side labels (Capture / Arrange / Search / Connect). Ends on a numbered manifesto list.

Motion

Essentially none; at most a slow fade on the floating screenshots. The reading rhythm is the motion.

Texture

Flat document white; the only depth on the page is the soft shadow pooling under floating UI panels.

Imagery

Almost none — the page IS text. The only visuals are real product-UI screenshots floated on white with soft diffuse shadows, containing small muted content thumbnails. Tool: capture or compose actual UI screenshots; kie-ai Seedream only for the muted, desaturated archive imagery inside mock UI panels. No hero art, no stock photography, no icons.

Don't

No hero, no cards, no icon sets, no gradients, no display type, no shouting CTAs — one small button is all the selling this style permits.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withAny AI toolCodexClaudeCursorChatGPTGeminiv0 / LovableI want toBuild a screenAudit my UIWrite a design brief

Tech stackUse the existing project stackReact / Next.jsAstroVue / NuxtSvelte / SvelteKitHTML / CSS / JavaScriptSwiftUIFlutter

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text# My project [Describe the product, audience, and screen you want to improve] Stack: Use the existing project stack Task: Implement the interface and verify the result in the existing project. ## Tool guidance (Any AI tool) Use available project tools to inspect, implement, and test. State any unavailable capabilities. # Design reference: Are.na — Plain-Document Manifesto Source: https://www.are.na Swipefile reference: https://swipefile.design/ref/arena-index/ Captured: 2026-09-05. This is a dated reference, not a claim about the current live product. Capture scope: a page excerpt. Do not infer unseen sections or interactions. ## Objective Adapt the visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets. ## Reference notes - mood: Anti-marketing sincerity. A quiet, literate document addressed to a reader, not a funnel — closer to a letter than a landing page. - colors: White canvas, small near-black sans text, mid-grey secondary text, one dark-indigo button; floating screenshots supply faint desaturated colour. Effectively monochrome. - typography: One small clean sans held at essay sizes throughout — bolded run-in heads ('How it works', 'The secret'), lettered lists (a. b. c.), numbered manifesto items, underlined inline links. Hierarchy from weight and indentation, never from scale. - layout: A narrow centered text column with an enormous top margin and no hero. Product screenshots break the column and float free with soft ambient shadows, annotated by quiet side labels (Capture / Arrange / Search / Connect). Ends on a numbered manifesto list. - motion: Essentially none; at most a slow fade on the floating screenshots. The reading rhythm is the motion. - texture: Flat document white; the only depth on the page is the soft shadow pooling under floating UI panels. - dont: No hero, no cards, no icon sets, no gradients, no display type, no shouting CTAs — one small button is all the selling this style permits. ## Acceptance criteria - Existing project conventions, design tokens, working functionality, and unrelated changes are preserved. - Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product. - Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap. - Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled. - Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported. - Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service. ## Quality bar Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Copy promptDownload .md

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.