Breadcrumbs are a single-line trail of links from a root page down to the one being read, separated by a repeated glyph, showing where the current page sits in a hierarchy and giving one click back to every level above it. The last item is where you already are, so it is not a link. The trail describes structure, not the route somebody took to arrive: two different things that get confused because both look like a line of page names.
The separator is chosen once for a product and never changes at runtime, which is why this family ships seven of them rather than one: a slash reads as a path, a chevron as travel, a pair of stacked dots as nesting with no direction at all. Length is the other half of the problem. Past a certain depth a trail has to fold, and it folds in the middle, the root and the current page carry the meaning, and the steps between them are what you can afford to put behind an ellipsis.
Docs are entered mostly from search, deep in a tree the reader never walked. The trail says which section they landed in and offers the parent page, which is often the overview they were actually looking for.
Folders are places, so the trail doubles as navigation: every crumb is a real listing, and the current folder's own control can offer its siblings without making anyone climb back up a level first.
Configuration pages bury a panel two or three levels under a section. A heading says what the panel is. Only the trail says which section owns it, and what else lives beside it at the same depth.
A product page sits under a chain of categories that each list something real. The trail turns those into one-click listings, and it is also how a crawler learns the shape of the catalogue behind the page.
No. The last crumb is the page you are already on, so it should not be a link; mark it as the current item so assistive technology announces it that way. It can still carry an affordance of its own, such as a control listing sibling pages, but clicking the label itself ought to do nothing at all.
Fold the middle, never the ends. The root and the current page carry the most meaning, so keep both and replace the steps between them with an ellipsis that expands the full trail when clicked. Wrapping onto a second line also works, though it costs vertical space at exactly the width where space is scarcest. Do not let the trail scroll sideways off screen.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Breadcrumbs are a single-line trail of links from a root page down to the one being read, separated by a repeated glyph, showing where the current page sits in a hierarchy and giving one click back to every level above it. The last item is where you already are, so it is not a link. The trail describes structure, not the route somebody took to arrive: two different things that get confused because both look like a line of page names.
The separator is chosen once for a product and never changes at runtime, which is why this family ships seven of them rather than one: a slash reads as a path, a chevron as travel, a pair of stacked dots as nesting with no direction at all. Length is the other half of the problem. Past a certain depth a trail has to fold, and it folds in the middle, the root and the current page carry the meaning, and the steps between them are what you can afford to put behind an ellipsis.
Docs are entered mostly from search, deep in a tree the reader never walked. The trail says which section they landed in and offers the parent page, which is often the overview they were actually looking for.
Folders are places, so the trail doubles as navigation: every crumb is a real listing, and the current folder's own control can offer its siblings without making anyone climb back up a level first.
Configuration pages bury a panel two or three levels under a section. A heading says what the panel is. Only the trail says which section owns it, and what else lives beside it at the same depth.
A product page sits under a chain of categories that each list something real. The trail turns those into one-click listings, and it is also how a crawler learns the shape of the catalogue behind the page.
No. The last crumb is the page you are already on, so it should not be a link; mark it as the current item so assistive technology announces it that way. It can still carry an affordance of its own, such as a control listing sibling pages, but clicking the label itself ought to do nothing at all.
Fold the middle, never the ends. The root and the current page carry the most meaning, so keep both and replace the steps between them with an ellipsis that expands the full trail when clicked. Wrapping onto a second line also works, though it costs vertical space at exactly the width where space is scarcest. Do not let the trail scroll sideways off screen.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.