Menus

The dropdown menu holds the actions that do not deserve standing room in a toolbar. Items cascade in a beat behind the panel rather than arriving with it, which is what makes a menu read as a list the eye can run down instead of a block that appears. Every item closes its menu on select through context, so nested compositions behave without extra wiring.

npx shadcn@latest add @minflow/menu

Where to use it

Overflow actions on rows and cards, behind an ellipsis handle.
Toolbar groupings: export formats, view options, account actions.
Two or three actions that all matter equally? Show them as buttons; a menu costs a click to reveal what was already affordable.

Variations

Plain list

The default. A handful of flat actions, each with a glyph the eye catches before it reads the word.

With labels

When the items fall into groups. A heading is cheaper than splitting one menu into two handles.

Nested flyout

For a set of close variations, such as export formats, that would otherwise double the length of the parent list.

Aligned to the trailing edge

When the handle sits at the right of its container. Aligning the panel to that edge keeps it inside the layout instead of pushing past it.