USE CASE · NAVIGATION WITH AI
Build a Divi 5 mega menu with AI and DiviOps
Build a mega menu your team can keep editing in Divi. Use DiviOps to group related pages on desktop, give phone visitors a simple list and keep key actions easy to find. In this walkthrough, our own header shows what the agent helped build, where we used custom code and what we checked before release.

SCREENSHOT · OUR PUBLISHED DESKTOP MENU

The Use Cases panel on diviops.com groups six workflows with coordinated icons, short descriptions and a link to the full collection. Open full-size screenshot ↗
Start with what visitors need to find
Start with what people come to find. Our visitors needed features, practical examples, documentation and reusable layouts. Putting every link in the top bar would have made it harder to scan.
We grouped those destinations under Product, Use Cases and Resources. Pricing, Account and Get Started stayed one click away. Product fit in a compact panel. Use Cases needed two columns with room to explain each workflow.
That gave the agent a brief to work from. Make it easier to find the right page, use the site’s existing styles and keep the menu editable in Divi.
From navigation brief to working header
Map the destinations
Choose clear groups and give each link a useful role. Keep the main action easy to find.
Inspect and build a draft
Let the agent inspect the header, available modules and design references before preparing an isolated staging version.
Refine the details
Review panel widths, icons, text wrapping, spacing and chevrons against the existing site.
Test, then integrate
Check desktop, phone and keyboard behaviour. Integrate the reviewed header on staging before approving production.
Give your agent the navigation brief and design references
Connect your AI client to WordPress through DiviOps so it can inspect the header and build a draft on staging. Our navigation used native Divi Section, Row, Column, Group, Text, Image and Dropdown modules.
We matched the link labels, descriptions and approved icons to our Use Cases cards. Once the menu opened correctly, we refined the dropdown arrows and fixed a small clipping issue on phones.
Give Claude Code or Codex your audience, destination list, brand references and approval boundaries. Keep the decisions in your project documentation so the next person can update the menu with the same brief.
Keep links and labels editable in Divi
The native Dropdown module opens the panel. Its links, labels and icons are still Divi modules your team can edit. We used styles scoped to the header and panels, plus a small helper that manages the expanded state, Escape, focus return and the mobile menu toggle.
DiviOps helped build and refine the header. The finished behavior relied on our installed Divi version, the scoped styles and the helper. Shared presets cover part of the styling. Test your own header before replacing it site-wide.
If your menu already works, pick one bounded improvement. Clarify a panel, fix a phone issue or make a key link easier to find.
Give phone visitors an inline menu
On desktop, the larger panel opens over the page. On a phone, the menu becomes a vertical list and its panels open inline. The original menu kept ordinary links and click or tap controls. We added desktop hover after these screenshots.
SCREENSHOT · PHONE NAVIGATION

The same Use Cases links become a single vertical list. This authentic phone-width capture shows the reviewed mobile navigation. Open full-size screenshot ↗
Test the menu before it goes live
On our site, we checked that opening another category closed the previous panel, clicking outside dismissed it and pressing Escape returned focus. With the keyboard, we opened a category and reached its first link. On a phone, Escape closed the active category before it closed the main menu.
We also checked that the panels fit the screen, the icons loaded and the page stayed within the viewport. We repeated the checks after putting the menu in the global header. The original header went live on 16 September 2026. The screenshots show that version. When we added desktop hover later, we checked keyboard controls and phone taps again.
These checks cover our menu. Test your own layout, keyboard controls and phone behavior before release.
Try it with your own navigation brief
Pick one navigation problem to solve and connect your AI client to staging. Adapt the prompt to your site and the tools you have. DiviOps is in public beta.
