Lists
This module handles two related jobs. First, it gives the project a small set of reusable list patterns: plain resets, section indexes, feeds, and browseable catalogs. Second, it provides three ways to lay long lists out across multiple columns when a single vertical stack becomes too tall to scan comfortably.
Use native <ul> and <ol> whenever the default document flow is enough. Reach for these classes when the list needs a clearer visual role, richer item metadata, or a deliberate multi-column layout. Definition lists (<dl>) are covered with the special text elements — they are a text pattern, not a list pattern.
Small building blocks
.list-unstyled
The base reset for structural lists. It removes bullets and left padding but keeps the semantic list markup intact.
- Navigation remains a real list
- Bullets disappear
- Indentation resets to zero
Use it for navigation blocks, groups of links, table-of-contents lists, and any custom list pattern where the marker would be visual noise.
.list-title
The label of a list group, declared on an <h5>: uppercase and bold, above an unstyled list, inside .list-group-pack columns, or as the title of an .index-list. It has no margin or padding of its own: the list follows directly under it, and all other spacing belongs to the surrounding context. A link inside it reads as the label, with no underline or highlight and the label's color; only the pointer shows it is a link.
Reference
- Specification
- Changelog
- Migration Notes
<h5 class="list-title"><a href="/reference/">Reference</a></h5>
Index lists
.index-list
index-list is the compact "section title + short link list" pattern used for table-of-contents style navigation. The title is the thing you scan first; the items underneath stay tight and quiet.
The markup is deliberately plain: a .list-title label on an <h5>, then a bare <ul> — the component styles its own ul/li (no markers, no indent, no margin between entries), because any list item inside an index list is an index entry by definition; no extra classes needed. The block itself owns the bottom rhythm (margin-bottom), so stacked index lists separate cleanly — it is also the canonical content unit inside .list-group-pack columns.
Use it when each list needs a named category above it. If the items themselves need metadata or a richer browse-to-pick reading, move up to .catalog-list.
Multi-column list layouts
All three utilities below solve the same problem in different ways: a list is too tall to read comfortably as one vertical stack. The right choice depends on what you want to control.
| Utility | Mechanism | You control | Best for |
|---|---|---|---|
.list-columns |
CSS columns | column count | One long flat list |
.list-group-pack |
CSS columns, balanced | min column width | Several grouped sublists that must stay intact |
.list-fixed-rows |
CSS grid | row count | Exact number of rows, usually TOCs |
How to choose quickly
- Use
.list-columnswhen you have one long plain list and just want it to become shorter on screen. - Use
.list-group-packwhen the list is made of named groups and each group should stay whole. - Use
.list-fixed-rowswhen you want a strict visual rhythm, for example exactly 3 or 4 rows. For a fixed two-column layout (most commonly a table of contents), set--list-rowsto half the item count — the columns come out equal-width automatically.
In short: .list-columns controls columns, .list-group-pack protects groups, .list-fixed-rows controls rows.
.list-columns
The default packer for a single flat list. It removes markers, flows items into two columns by default, and can be expanded with .list-columns-3, .list-columns-4, or .list-columns-5.
A note on prose columns. This page documents list-oriented column tools. The generic prose utility is .prose-columns — deliberately not featured here, because Rare Styles treats running prose in multiple columns as an exception, not a default reading pattern. Its reference will land with the text-content documentation pass.
On mobile, the base utility collapses to one column; the wider variants collapse to two.
- Amsterdam
- Berlin
- Copenhagen
- Dublin
- Edinburgh
- Frankfurt
- Geneva
- Helsinki
- Istanbul
- Lisbon
- Madrid
- Oslo
- Prague
- Stockholm
- Vienna
- Warsaw
- Zurich
Use it when mechanical balancing is acceptable. If list items belong to named groups that must not split across a column edge, use .list-group-pack instead.
.list-group-pack
For grouped sublists with subheadings. This utility balances the groups across the columns and keeps each child block intact with break-inside: avoid, so a label and its items travel together. The canonical child is an .index-list — the packer arranges the columns and sets the 16px gap under each group, the index lists carry the content.
The pack needs no height: on a desktop it fits as many columns as the container allows, and you can tune their minimum width with --list-group-pack-min. A height utility on it has no effect.
On narrow viewports the number of columns is fixed: 2 on mobile, 3 on tablet.
Foundations
- Tokens
- Typography
- Colors
- Grid
Components
- Buttons
- Cards
- Panels
- Tables
- Tags
Navigation
- Header
- Sidebar
- Breadcrumbs
Decorations
- Highlights
- Frames
- Badges
.list-fixed-rows
The grid-based option. Instead of choosing a column count, you choose the number of rows with the custom property --list-rows. The browser then fills columns automatically in source order.
This is useful when visual rhythm depends on a fixed row count rather than on balanced columns.
On mobile the fixed-row contract is dropped: the list reflows into two equal columns in row order. If two columns are too tight or too loose for your items, override the count with the responsive grid utilities — mobile:grid-cols-1, mobile:grid-cols-3, and so on — right on the same element.
- Clarify module purpose
- Document the public classes
- Add live examples
- Check naming consistency
- Verify responsive behavior
- Link the next typography page
Two equal columns (tables of contents)
A two-column table of contents is just a fixed-rows list whose row count is half the item count. With eight entries and --list-rows: 4, the grid fills four rows and wraps into two equal-width columns — .list-fixed-rows sizes its implicit columns with minmax(0, 1fr), so they stay equal without any extra class.
Earlier releases shipped a dedicated .list-fixed-rows-2col modifier for this. It was removed in v0.6.15 because the base utility now equalizes its columns on its own — set --list-rows instead.
- What the library is for
- Installation
- Tokens
- Typography
- Layout
- Components
- Navigation
- Decorations
Feed lists
.feed-list, .feed-list__item, .feed-list__title, .feed-list__meta
A feed is a chronological vertical stream — and a navigation surface, not body copy. Authors put content into a feed precisely because it deserves the reader's attention, so the pattern spends visual budget on it: full-size titles and generous vertical whitespace between line-separated items signal that the entries are valuable. Each item gets a top rule, a title, and a quiet meta line that keeps dates and tags from competing with the title. The pattern is intentionally narrow: it is for updates, logs, changelogs, or knowledge-base streams where sequence matters more than per-item detail.
Use a feed when each item is mostly "date + title + optional tags". If readers need to compare entries as options rather than follow them as a timeline, .catalog-list is usually the better fit.
.feed-list__clean
Add feed-list__clean next to feed-list to drop the rule between items, for a short list where whitespace alone separates the entries: <div class="feed-list feed-list__clean">.
Catalog lists
.catalog-list, .catalog-list__item
The browseable list pattern for catalogs, search results, documentation indexes, portfolios, and other "pick one of these" situations. The component is deliberately minimal: it owns the item rhythm, the title and the meta line — nothing else. Tag chips sit inline in the meta line; any extra content (a short summary paragraph, a nested list) is host content and renders with document defaults.
.catalog-list__title
The entry title. The visual anchor of each record.
.catalog-list__meta
Muted supporting metadata. Links inside stay muted too, so they remain part of the meta line instead of competing with the title. .tag chips can sit directly in the meta line — no dedicated wrapper needed.
Master milestone list for upcoming cleanup, namespace work, and docs-driven audits.
Curated record of imported list patterns, resolved naming forks, and remaining integration work.
The summary paragraphs above are plain <p> elements — host content, not component API.
.catalog-list--nest
Indents everything under the title, so each entry reads as a parent with its nested contents: the children of the thing named in the title. Use it for file trees, API surfaces, section maps, and other hierarchical indexes.