Right arrow head, path

Right arrow head, path is a Breadcrumbs block from Orvain UI, built for React and Vue with a matching Figma frame.

Best for

A drive or file tree, where the trail is a path you can walk and copy

Anatomy

A drive path with the approved folder icon on every crumb · the folder you are in lists below as walkable rows with file icons, sizes and edit dates · open a folder to go down, a crumb to go up, the list swaps with a short stagger · a Copy path button that turns into Copied and back

MCPConnect the MCP server

In the Orvain Library

Get Right arrow head, path for your product

The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.

  • React
  • Vue
  • Figma frame
  • Orvain MCP

About this block

Part of Breadcrumbs

What’s inside

04parts

The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.

  1. A drive pathwith the approved folder icon on every crumb
  2. The folder you arein lists below as walkable rows with file icons, sizes and edit dates
  3. Open a folder to go downa crumb to go up, the list swaps with a short stagger
  4. A Copy path buttonthat turns into Copied and back

Responsive behaviour

620 px

Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.

1440pxDesktop · 12 columns

When to use it

Where Breadcrumbs earns its place

Reach for Breadcrumbs

  • Content sits more than two levels deep and people arrive mid-tree from search
  • A file or asset browser where each parent is a real place you can open
  • Settings panels nested under sections, where the page heading alone does not say which section owns them
  • You need a way back up that costs one line instead of a sidebar

Reach for something else

  • A flat site with one level of sections: the trail only repeats the nav, so let the nav's own active state do it
  • A linear process like a checkout or an application: a step indicator shows progress and what remains, which ancestry cannot
  • The trail would be the only navigation on the page: breadcrumbs supplement a nav rather than replace one

Accessibility

06to keep

What the block ships with. Hold on to these as you make it yours.

  • Named controlsEvery icon-only button keeps a text label, so a screen reader can say what it does.
  • Keyboard firstEvery control is reachable with Tab, and its focus ring stays visible.
  • More than colourA state never rides on colour alone; a mark or a word goes with it.
  • Contrast holdsRetheme freely, but keep text at or above the contrast it ships with.
  • Calm motionFor visitors who ask for reduced motion, things simply appear.
  • Room to hitTargets stay at least 24px, with space between neighbours.

Notes for AI

1 line

Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.

Add the Orvain “Right arrow head, path” block to this page: a drive path with the approved folder icon on every crumb, the folder you are in lists below as walkable rows with file icons, sizes and edit dates, open a folder to go down, a crumb to go up, the list swaps with a short stagger, a Copy path button that turns into Copied and back.

Works in
Connect the MCP

Questions about Right arrow head, path.

What is the Right arrow head, path block?

Right arrow head, path is a Breadcrumbs block from Orvain UI, built for React and Vue with a matching Figma frame. Best for a drive or file tree, where the trail is a path you can walk and copy.

What is the Right arrow head, path block made of?

Is the Right arrow head, path block responsive?

Is the Right arrow head, path block accessible?

How do I add the Right arrow head, path block to my project?

When should I not use a Breadcrumbs block?

More Breadcrumbs blocks

All Breadcrumbs

Chevron

The default trail: docs, file browsers, nested settings

Right arrow head

Denser chrome, where the separator should sit closer to the crumb behind it

Forward slash

Paths and URLs, where the trail is a literal address

Dot

Quiet trails that sit under a page title and should not compete with it

Double dot

Trails that need a mark with no direction: a hierarchy read by nesting, not by travel

Arrow head

The same arrow with even spacing on both sides

More vertical

Toolbars where the separator should read as a rule rather than a glyph

Chevron, folded

Docs and file browsers whose trail can be longer than its room

Dot, under a title

Page headers where the trail must stay quiet and never change the header's height

More vertical, folded toolbar

Document toolbars with avatars and a Share action beside the trail

Chevron, opens

Docs sites and file explorers, where a level should be one pick away

Forward slash, switcher

Dev-tool headers: workspace, project and branch, each one switch away

Double dot, switcher

Help centres: move to another section or article without going back up

Arrow head, editor path

Code editors and file browsers: the bar is the fastest way between files

Double dot, peek

Trails where a level needs a hint before you leave the page

Right arrow head, glide

Settings and admin pages, where the trail should read like the segmented controls around it

Dot, sticky

Long articles and docs, where the header trail scrolls away

Arrow head, back

App headers and phones, where the way back matters most

More vertical, glide toolbar

Document toolbars with Preview and Share next to the trail

Forward slash, address

File and route paths, where people may want to type the address

The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.