Luma — Discover events

Events & BookingSee it livelu.ma

Every card on the page is a plain white rectangle with a 1px border — the only color anywhere lives inside the small circular category glyphs, and there are exactly eight of them. Restraint is the entire visual strategy.

Luma — Discover events — captured interface — Page excerpt · scroll inside to explore

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

Search & discovery

Why this pattern works

The category-card format — a single illustrated glyph, a bold name, and a count, nothing else — as the fastest possible browse affordance for a large catalog. Steal it wholesale for any discovery page needing a category grid: it works precisely because it refuses to add a description, a CTA, or a hover state beyond what's already there.

Design notes

Surface: Discover Events landing page, logged out
Navigation: One tier. A borderless top bar: wordmark left, plain right-aligned items (live time, a text nav link, a Sign In pill) — no icon rail, no sidebar, no tabs. The page is a single scrolling document, header included.
Layout: Single fluid column, max-width centered, no fixed regions — the entire page including the header scrolls together. Two stacked 3-column card grids separated by one hairline rule and generous vertical whitespace.
Density: Loose. Category cards run ~80px tall with generous internal padding; wide gutters mean 8 cards read as a light list, not a dense wall. Featured-calendar cards run taller to fit a 2-line description.
Color: A single lilac-to-white vertical gradient behind everything at the top of the page, fading to solid white by mid-scroll. Every card is neutral — white fill, black text, grey meta — and the only saturation on the entire page lives inside each category glyph, each a different hue.
Type: One sans family. The page title is the only large type (~38px bold); section headers sit at ~20px bold; card titles ~15-16px semibold; counts and descriptions ~13px grey. Hierarchy is pure size-stepping, never color or decoration.
Pattern: Glyph-plus-label category cards on a bare page: the illustrated icon does all the visual differentiation work so the layout itself can stay completely flat and identical card to card.
States: Logged out: Sign In pill top right, Follow buttons (not Following) on every featured-calendar card, page fully populated with no empty or loading state visible.
Don't: Don't add a second gradient, a shadow, or a hover-elevate effect to make the cards feel more 'alive.' The whole point is that a plain 1px-bordered rectangle is enough once the glyph is doing the work — extra chrome here reads as compensating, not polishing.

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: Luma — Discover events
Source: https://lu.ma/discover
Swipefile reference: https://swipefile.design/ref/luma-discover/
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: Discover Events landing page, logged out
- nav: One tier. A borderless top bar: wordmark left, plain right-aligned items (live time, a text nav link, a Sign In pill) — no icon rail, no sidebar, no tabs. The page is a single scrolling document, header included.
- layout: Single fluid column, max-width centered, no fixed regions — the entire page including the header scrolls together. Two stacked 3-column card grids separated by one hairline rule and generous vertical whitespace.
- density: Loose. Category cards run ~80px tall with generous internal padding; wide gutters mean 8 cards read as a light list, not a dense wall. Featured-calendar cards run taller to fit a 2-line description.
- color: A single lilac-to-white vertical gradient behind everything at the top of the page, fading to solid white by mid-scroll. Every card is neutral — white fill, black text, grey meta — and the only saturation on the entire page lives inside each category glyph, each a different hue.
- typography: One sans family. The page title is the only large type (~38px bold); section headers sit at ~20px bold; card titles ~15-16px semibold; counts and descriptions ~13px grey. Hierarchy is pure size-stepping, never color or decoration.
- pattern: Glyph-plus-label category cards on a bare page: the illustrated icon does all the visual differentiation work so the layout itself can stay completely flat and identical card to card.
- states: Logged out: Sign In pill top right, Follow buttons (not Following) on every featured-calendar card, page fully populated with no empty or loading state visible.
- dont: Don't add a second gradient, a shadow, or a hover-elevate effect to make the cards feel more 'alive.' The whole point is that a plain 1px-bordered rectangle is enough once the glyph is doing the work — extra chrome here reads as compensating, not polishing.

Useful for: The category-card format — a single illustrated glyph, a bold name, and a count, nothing else — as the fastest possible browse affordance for a large catalog. Steal it wholesale for any discovery page needing a category grid: it works precisely because it refuses to add a description, a CTA, or a hover state beyond what's already there.

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

Luma — Discover events

Make it your own

Keep exploring