Feature Request: V4 atomic navigation menu

[rajin-skele]

Describe the Problem

Elementor V4’s atomic approach would benefit from a native navigation menu built from reusable atomic parts.

Current navigation solutions tend to behave like monolithic widgets. This makes it harder to style individual parts consistently, reuse them across projects, manage responsive states, and let AI tools understand or modify the menu structure.

A navigation menu is a core site component, so it should work naturally with V4’s atomic styling system, global classes, variables, and responsive controls.

Propose a Solution

Introduce a native Elementor V4 atomic navigation menu component composed of independently configurable parts, such as:

• Navigation wrapper
• Menu list
• Menu item
• Link
• Dropdown trigger
• Dropdown panel
• Menu icon
• Mobile menu toggle
• Mobile menu panel

Each part should support V4 atomic styling, global classes, variables, responsive controls, hover/focus/active states, nested menus, and dynamic WordPress menus.

The component should also provide accessible keyboard navigation, correct ARIA behavior, mobile menu controls, and predictable support for sticky headers and responsive layouts.

Ideally, the structure should be inspectable and editable by AI/MCP tools so an agent can understand and modify the navigation without treating it as an opaque widget.

Additional Context

This request is specifically about the Elementor V4 atomic architecture, not only adding another monolithic navigation widget.

A modular navigation component would make it easier to build consistent headers, reuse menu patterns, maintain design systems, and generate or modify navigation through AI tools.

Related ideas include atomic V4 components, AI/MCP-compatible Elementor structures, and reusable design-system-based components.

Agreement

• I confirm I have read and followed all the guidelines and instructions outlined in the Feature Request form.
• I agree that my discussion may be closed without further action if it doesn't meet all the requirements outlined in the Feature Request form.

[AF1QUE]

@nicholaszein, sorry to mention you directly here, but can this be prioritized and included in the upcoming Q4 roadmap release? We are really struggling to create navigation menus because of the lack of atomic navigation elements. I hope you understand. Thanks!

[afnanmishu]

@nicholaszein i really need Menu + Mega Menu as well. Especially a Mega Menu where we can use standard atomic elements, classes, variables, and responsive controls.

Feels like one of the main missing pieces for building full V4 headers right now.