The Pudding — Newspaper Grid Editorial

Editorial GridVisit sitepudding.cool

Data-journalism editorial: strong grid, mixed serif/sans, charts as content.

The Pudding — Newspaper Grid Editorial — captured interface — Page excerpt · scroll inside to explore

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

Design notes

Mood: Smart, journalistic, substantive. Content-first storytelling with visual rigor.
Colors: Paper/white base, ink black, one or two editorial accents for data highlights. Restrained so charts and photos pop.
Type: Serif for headlines/body (magazine feel) mixed with a sans for labels, captions, and UI. Strong hierarchy, drop-caps, pull quotes.
Layout: Multi-column newspaper grid, bylines, dek/standfirst, inline charts and figures, sidebars. Dense but well-ruled and scannable.
Motion: Scrollytelling: charts animate and annotate as you scroll, sticky graphics with stepped narration. Motion serves the story.
Texture: Rules/dividers, boxed figures, captions, halftone or duotone imagery. Print-inspired, structured.
Imagery: Editorial photography with duotone treatments, plus chart/figure graphics. Tool: Pexels for photos (duotone them); build charts in code (SVG/D3); kie-ai for illustrated figures where needed.
Don't: No sparse landing-page hero with three words, no decorative motion, no color for color's sake. Let content lead.

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 Pudding — Newspaper Grid Editorial
Source: https://pudding.cool
Swipefile reference: https://swipefile.design/ref/pudding-editorial-grid/
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: Smart, journalistic, substantive. Content-first storytelling with visual rigor.
- colors: Paper/white base, ink black, one or two editorial accents for data highlights. Restrained so charts and photos pop.
- typography: Serif for headlines/body (magazine feel) mixed with a sans for labels, captions, and UI. Strong hierarchy, drop-caps, pull quotes.
- layout: Multi-column newspaper grid, bylines, dek/standfirst, inline charts and figures, sidebars. Dense but well-ruled and scannable.
- motion: Scrollytelling: charts animate and annotate as you scroll, sticky graphics with stepped narration. Motion serves the story.
- texture: Rules/dividers, boxed figures, captions, halftone or duotone imagery. Print-inspired, structured.
- dont: No sparse landing-page hero with three words, no decorative motion, no color for color's sake. Let content lead.

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

The Pudding — Newspaper Grid Editorial

Make it your own

Keep exploring