NavBridge Pro

A headless storefront still needs a real navigation menu — ideally a mega menu with columns, promo blocks and icons, not just a flat list of links. NavBridge Pro adds those controls to every Magento category and exposes the entire navigation structure over GraphQL, so your Astro (or any headless) frontend can build a rich, multi-column mega menu from a single query — driven by merchants in the normal category admin, with no front-end redeploy.

Compatibility

Magento

Open Source 2.4.9 GA (and later 2.4.x).

PHP

Tested on 8.4 and 8.5.

Headless

Two dedicated GraphQL queries + native category fields.

Merchant-driven

Per-category controls in the standard category editor.

What it adds to each category

Open any category and you’ll find a NavBridge Pro Settings panel:

Control	What it does
Enable Mega Menu	Marks this top-level category as a mega-menu trigger (its children are returned grouped).
Mega Menu Columns	How many columns (1–5) the storefront should lay the children out in.
CMS Block Identifier	A CMS block to render in the mega menu’s promo area (e.g. a seasonal banner).
Navigation Icon	An icon (≤2 MB, jpg/png/gif/svg) shown next to the nav item.

Store-scoped, like every category field

Each control is per store view — switch the Scope selector at the top of the category page to give a German or B2B store a different mega-menu layout, columns or promo block from the default.

Serving navigation to a headless storefront

Mega menu

navBridgeMegaMenu returns the top-level, in-menu categories; any marked as a mega menu come back with their children and layout hints already attached.

{
  navBridgeMegaMenu {
    id name url_path
    nav_bridge_is_mega
    nav_bridge_columns
    nav_bridge_cms_block
    nav_bridge_icon
    children { id name url_path }
  }
}

Full tree

navBridgeCategoryTree returns the whole active category tree (optionally depth-limited, or mega-only) as a nested structure ready to render.

{
  navBridgeCategoryTree(depth: 2) {
    id name level
    nav_bridge_columns
    children { id name children { id name } }
  }
}

On native queries

The four nav_bridge_* fields are also added to Magento’s native categories / categoryList queries, so if you already fetch categories you can just request the extra fields — no separate call needed.

{ categories(filters: {ids: {eq: "41"}}) {
    items { id name nav_bridge_is_mega nav_bridge_columns }
} }

Set it up

1. Open Catalog → Categories and pick a top-level category.

2. Expand NavBridge Pro Settings, turn on Enable Mega Menu, pick a column count, and (optionally) set a promo CMS block and icon. Save.

3. From your storefront, query navBridgeMegaMenu — the category comes back with its children, column count and promo block, ready to render as a mega menu.

Global controls under Nav Pro

There’s also a Stores → Configuration → AgenticEcom · Headless & Astro → Nav Pro section with a master Enabled switch, a Default Mega Menu Columns value (used when a category doesn’t set its own), and a Category Allow/Deny group — choose All except excluded or Only included and pick the categories — to scope exactly which categories reach the storefront mega-menu.

Safe & correct

Only active, in-menu categories

Both queries filter to active categories (and the mega menu to include-in-menu), so a disabled or hidden category never appears in your navigation.

Nested tree, done right

navBridgeCategoryTree builds a proper parent→child tree from the category path, with an optional depth limit and a mega-only filter for lean menu payloads.

FAQ

Do I have to use the dedicated queries?

No. The nav_bridge_* fields are merged onto Magento’s native categories and categoryList queries, so if your storefront already loads the category tree you can just add the extra fields. The navBridgeMegaMenu / navBridgeCategoryTree queries are there when you want a ready-shaped menu in one call.

Will disabled categories show in the menu?

No — both resolvers filter to active categories, and the mega-menu query additionally requires include in menu, so anything hidden from the storefront stays out of the navigation.

Can different store views have different mega menus?

Yes — every NavBridge field is store-scoped, so each store view can have its own mega-menu layout, column count, promo block and icons. Set the Scope selector on the category page before editing.

What does the column count actually do?

It’s a layout hint your storefront reads (nav_bridge_columns, 1–5) to decide how many columns to arrange a category’s children into. Rendering lives in your theme/storefront, so you stay in full control of the markup. Verified clean on PHP 8.4 and 8.5.