The bundle supports two distinct levels of collapse behaviour, both driven by flags on theDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/nowo-tech/DashboardMenuBundle/llms.txt
Use this file to discover all available pages before exploring further.
Menu entity and rendered with Bootstrap 5 markup.
Top-level collapse (collapsible)
When the Collapsible flag is enabled on a menu, the entire menu is wrapped in a block with a toggle button. Clicking the button expands or collapses the full <ul> tree.
The generated markup looks like this:
- The toggle button label is the menu’s name (or code as fallback).
- The
dashboard-menu-toggle-iconspan is a hook for a CSS chevron. class="collapse show"when expanded;class="collapse"when collapsed.
Default state (collapsible_expanded)
The Collapsible expanded flag controls whether the menu starts open or closed:
collapsible_expanded | Initial state |
|---|---|
true (default) | Menu is open on page load |
false | Menu is collapsed on page load |
Nested item collapse (nested_collapsible)
When Nested collapsible is enabled, each item that has children gets its own toggle button beside the label. Children are rendered inside a Bootstrap collapse <div>.
class="collapse show"), regardless of the default expanded state.
Section items and nested collapse
Items with type Section (a non-clickable group header) also get a toggle button whennested_collapsible is enabled. The chevron is placed after the section label:
Chevron styling
Both toggle types provide a<span> element for a CSS-driven chevron. Add this CSS (or adapt it to your design system):
Configuring collapse options
All three flags are set on the Menu entity in the dashboard (gear icon → Configuration tab). There is no global YAML equivalent — the settings are per-menu.| Flag | Effect |
|---|---|
collapsible | Wrap menu in a toggle block |
collapsible_expanded | Start expanded (true) or collapsed (false) |
nested_collapsible | Add per-item toggles for items with children |
menuConfig array returned by dashboard_menu_config(), so custom templates can read them: