vocab.design

layout

Content shelf

also called carousel row (community), swimlane (community), reel (every-layout), tray (community), netflix rows (community)

A horizontally scrolling row of cards, one row per category, stacked down the page so each row is browsed sideways.

A shelf is a row that holds more than it shows. Each row is one category, the row scrolls sideways on its own, and the rows stack down the page, so a catalogue of thousands becomes a page a reader can skim vertically and then dig into horizontally. The shape is old (a rack of records, a shelf of spines) and it earned its place on screen for a practical reason: a grid of everything forces one ranking on the whole library, while a stack of shelves lets every category keep its own. Every Layout calls the primitive a reel and gives the minimum honest implementation: a flex row, overflow-x: auto, and scroll snapping if the items are wide enough to want it.

Three neighbours are worth keeping straight, because the words get swapped constantly. A filmstrip is a rail of thumbnails beside a larger view, and picking one changes that view; a shelf has no larger view, and picking an item leaves the page. A carousel rotates one item at a time through a single frame, usually on a timer; a shelf shows many items at once, moves only when the reader moves it, and never advances by itself. And the cards on a shelf are not what makes it a shelf: swap them for thumbnails or plain text rows and the pattern is unchanged, because the pattern is the row and its sideways reading.

The honest cost is the far end. A shelf hides most of every row behind an edge, and the reader’s effort per item climbs with its index: item one is seen by nearly everyone, item twenty by almost nobody. Stacking twelve shelves does not fix that, it multiplies it, and the result is a page with hundreds of items on it and a handful that anyone will ever reach. That is fine when the ordering is genuinely good and awful when the shelf is being used to avoid an editorial decision. Watch for the pattern where a shelf exists so nothing has to be cut.

Two implementation details decide whether a shelf is usable at all. It must be reachable without a pointer that can drag: real focusable items so the keyboard can walk the row, and buttons or pagination affordances so a mouse without a horizontal wheel is not stuck. And the edge has to say there is more, through a partly visible next card, a fade, or an arrow, because a row that ends flush with its container reads as a row that ends. Scroll snap per item makes it feel deliberate; scroll snap per page makes it feel like a carousel again.

A note on the borrowed name. “Swimlane” for a shelf comes from process diagrams, where a lane is a horizontal band holding everything one actor does, and that is the sense that fits here: one band, one category, running sideways. It gets used for the vertical column of a kanban board at least as often, which is the opposite axis, so the word tells a reader almost nothing on its own. Shelf, row, or tray is unambiguous.

Which word?

If you wantsay
many categories, each with too many items to stackcontent shelf
a thumbnail rail that drives a big previewfilmstrip
a set of items shown a few at a time in a rowcarousel
endless peers you skim rather than navigatefeed layout
items that belong to exactly one stage at a timekanban board

Sources