Klim Type Foundry — Retail fonts

Creative ToolsSee it liveklim.co.nz

The catalogue has zero product photography — the typeface's own letterforms, set at poster scale inside a full-bleed colour band, are the only image on the page.

Klim Type Foundry — Retail fonts — captured interface — Page excerpt · scroll inside to explore

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

Why this pattern works

The one pattern worth stealing whole: full-bleed colour bands as the row unit, with the product name set live in its own typeface at huge scale on the left. Because the specimen IS the swatch there's no need for a thumbnail, a card or a border — use this for any catalogue where the content itself is already the strongest possible visual (typefaces, but also palettes, fabric swatches, finishes).

Design notes

Surface: Klim Type Foundry, Retail Fonts catalogue page
Navigation: One tier. A plain black top bar: wordmark 'Klim Type Foundry' left, a single 'Fonts' link beside it at the same size and weight, a hamburger glyph right. No dropdown, no breadcrumb, no visible search — the page under it does all the navigating.
Layout: Full-bleed, full-width bands stacked with zero gap and no max-width container anywhere. Each band spans edge to edge; its height is set by how many styles it lists, not by a fixed row grid.
Density: Sparse by design. One product per band, three fixed columns inside it (name / style list / buy), and a lot of dead flat colour left as negative space around the type.
Color: Colour is the entire product. Each band is a different flat, saturated fill — blood red, near-black, burnt orange, near-black again, light grey — chosen per typeface, no gradient, no image ever laid over it. Foreground text just flips between black and off-white to stay legible on whatever fill it sits on.
Type: The typeface name is set IN the actual typeface at ~64-80px — the only place on the page where type-as-content and type-as-chrome are the same pixels. Style names and 'Buy' sit at ~14px in a plain utility sans, so the display name stays 4-5x louder than everything else in the band.
Pattern: The band as both product photo and buy button: no thumbnail, no rendered mockup, no card — the live typeface rendering the vendor's own name is the entire piece of merchandising.
States: No empty, loading or logged-out state visible — this is a static catalogue; every band always carries at least a name and one Buy link, so there's nothing to design for absence.
Don't: Don't add a card, a border, an image swatch or a hover-elevated shadow to the band. The instant it looks like a 'product card' instead of a flat colour field, the specimen-as-photo trick collapses back into generic ecommerce.

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: Klim Type Foundry — Retail fonts
Source: https://klim.co.nz/retail-fonts/
Swipefile reference: https://swipefile.design/ref/klim-foundry/
Captured: 2026-08-01. 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 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: Klim Type Foundry, Retail Fonts catalogue page
- nav: One tier. A plain black top bar: wordmark 'Klim Type Foundry' left, a single 'Fonts' link beside it at the same size and weight, a hamburger glyph right. No dropdown, no breadcrumb, no visible search — the page under it does all the navigating.
- layout: Full-bleed, full-width bands stacked with zero gap and no max-width container anywhere. Each band spans edge to edge; its height is set by how many styles it lists, not by a fixed row grid.
- density: Sparse by design. One product per band, three fixed columns inside it (name / style list / buy), and a lot of dead flat colour left as negative space around the type.
- color: Colour is the entire product. Each band is a different flat, saturated fill — blood red, near-black, burnt orange, near-black again, light grey — chosen per typeface, no gradient, no image ever laid over it. Foreground text just flips between black and off-white to stay legible on whatever fill it sits on.
- typography: The typeface name is set IN the actual typeface at ~64-80px — the only place on the page where type-as-content and type-as-chrome are the same pixels. Style names and 'Buy' sit at ~14px in a plain utility sans, so the display name stays 4-5x louder than everything else in the band.
- pattern: The band as both product photo and buy button: no thumbnail, no rendered mockup, no card — the live typeface rendering the vendor's own name is the entire piece of merchandising.
- states: No empty, loading or logged-out state visible — this is a static catalogue; every band always carries at least a name and one Buy link, so there's nothing to design for absence.
- dont: Don't add a card, a border, an image swatch or a hover-elevated shadow to the band. The instant it looks like a 'product card' instead of a flat colour field, the specimen-as-photo trick collapses back into generic ecommerce.

Useful for: The one pattern worth stealing whole: full-bleed colour bands as the row unit, with the product name set live in its own typeface at huge scale on the left. Because the specimen IS the swatch there's no need for a thumbnail, a card or a border — use this for any catalogue where the content itself is already the strongest possible visual (typefaces, but also palettes, fabric swatches, finishes).

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

Klim Type Foundry — Retail fonts

Make it your own

Keep exploring