AFFiNE — Local document workspace

Documents & KnowledgeSee it liveapp.affine.pro

An unsigned workspace opens a getting-started document beside a compact navigation rail, with a visible notice that the content is stored locally.

AFFiNE — Local document workspace — captured interface — Viewport capture · opening screen

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

Creative tools

Why this pattern works

Document editors that introduce features inside an editable workspace.

Design notes

Surface: AFFiNE unsigned local workspace and Getting Started document.
Navigation: Left rail includes search, all documents, journals, settings, and organization tools.
Layout: Persistent sidebar beside a spacious document canvas and narrow document toolbar.
Density: Low in the document, compact in the navigation.
Color: White and soft gray with a pale red local-storage notice.
Type: Bold document title, readable body copy, small sidebar labels.
Pattern: Teach the editor through a starter document while keeping the same navigation as the working product.
States: Local browser storage is explicitly disclosed; this is not a signed-in cloud workspace.
Don't: Do not hide the distinction between local storage and synchronized data.

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 withI want to

Tech stack

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: AFFiNE — Local document workspace
Source: https://app.affine.pro/
Swipefile reference: https://swipefile.design/ref/saas-ui-affine-workspace/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: AFFiNE unsigned local workspace and Getting Started document.
- nav: Left rail includes search, all documents, journals, settings, and organization tools.
- layout: Persistent sidebar beside a spacious document canvas and narrow document toolbar.
- density: Low in the document, compact in the navigation.
- color: White and soft gray with a pale red local-storage notice.
- typography: Bold document title, readable body copy, small sidebar labels.
- pattern: Teach the editor through a starter document while keeping the same navigation as the working product.
- states: Local browser storage is explicitly disclosed; this is not a signed-in cloud workspace.
- dont: Do not hide the distinction between local storage and synchronized data.

Useful for: Document editors that introduce features inside an editable workspace.

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

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

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Document editors that introduce features inside an editable workspace.

AFFiNE — Local document workspace

Make it your own

Keep exploring