What it does

avo-menu

Lay out your Avo sidebar the way your team actually works, instead of settling for the auto-generated list of resources. Menu Editor gives you a Ruby DSL in config/initializers/avo.rb: set config.main_menu and build the navigation from sections, groups, resources, dashboards, and plain links, in the order and grouping that match how people use the app.

Each item carries its own options: an icon from Heroicons or Tabler, a visible block that can call your Pundit policies so people only see what they can reach, a hotkey for keyboard navigation, and collapsable sections and groups. Nest links under a resource for sub-items, or drop in all_resources and all_dashboards when you want the full set with a few exclusions.

The sidebar is where it earns its keep, but the same DSL drives more than the sidebar: reshape the header menu and the profile menu with the same building blocks, and more menus are on the way. It is a DSL your agent configures in a few lines, and it stays in sync with Avo as both evolve.

See it in action

Avo sidebar built with Menu: sections, groups, resources, and dashboards

What you get

Build the sidebar in Ruby with section, group, resource, dashboard, and link in config.main_menu
Nest links under a resource for sub-items, or pull the full set with all_resources, all_dashboards, all_tools
Per-item icons from Heroicons or Tabler on sections, links, resources, and dashboards
visible blocks that call your authorization policies, so people only see items they can open
Collapsable and default-collapsed sections and groups for dense admin apps
Keyboard hotkeys on resources, links, and dashboards for fast navigation
The same DSL for the header menu and profile_menu, not just the sidebar, with more menus on the way

Why it pays off

Ship a curated, role-aware sidebar this afternoon instead of generating a menu component and its authorization wiring from scratch.
As your resources and dashboards change and Avo upgrades, the same menu DSL keeps working, and improvements to it reach your app with bundle update.
Visibility runs through your existing policies, so access control lives in one place instead of being duplicated in custom menu markup.
The same menu DSL in every app your agents build, instead of a different navigation layer generated each time.