The Public Domain Review

Editorial GridVisit sitepublicdomainreview.org

Archival imagery leads a newspaper-like composition, while narrow side columns provide context and a subscription route without replacing the central story.

The Public Domain Review — captured interface — Viewport capture · opening screen

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

Why this pattern works

Archival imagery leads a newspaper-like composition, while narrow side columns provide context and a subscription route without replacing the central story.

Design notes

Mood: Editorial and content-led
Colors: White background, dark text and muted historical artwork.
Type: Elegant serif masthead and editorial typography with compact navigation.
Layout: Centered feature image and headline with narrow informational columns on both sides.
Motion: A still opening-viewport capture. Visit the original source to inspect motion and scrolling.
Texture: The captured imagery supplies visual character; surrounding interface decoration stays restrained.
Don't: Adapt the hierarchy and composition to your own content. Use your own identity, text and imagery.

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: The Public Domain Review
Source: https://publicdomainreview.org/
Swipefile reference: https://swipefile.design/ref/expand-the-public-domain-review/
Captured: 2026-09-08. 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 visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- mood: Editorial and content-led
- colors: White background, dark text and muted historical artwork.
- typography: Elegant serif masthead and editorial typography with compact navigation.
- layout: Centered feature image and headline with narrow informational columns on both sides.
- motion: A still opening-viewport capture. Visit the original source to inspect motion and scrolling.
- texture: The captured imagery supplies visual character; surrounding interface decoration stays restrained.
- dont: Adapt the hierarchy and composition to your own content. Use your own identity, text and imagery.

Useful for: Archival imagery leads a newspaper-like composition, while narrow side columns provide context and a subscription route without replacing the central story.

## 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 visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Archival imagery leads a newspaper-like composition, while narrow side columns provide context and a subscription route without replacing the central story.

The Public Domain Review

Make it your own

Keep exploring

Help improve Swipefile?