Giuliomax Menu Builder

Two ways. In a block or FSE theme, open the editor, click the + inserter, search for MenuX and drop the block where you want the navigation — no code. In a classic theme or page builder, paste the [menux] shortcode into any page, post, widget or template. To place a location-specific menu, pick the location in the block sidebar or pass it to the shortcode: [menux location="footer"].

Yes, genuinely free. Every feature — mega menus, the WooCommerce cart, all 50 themes, the Announcement Bar with countdown, the Footer Builder, accessibility, Google Fonts — is included with no paywall, no "upgrade" banners in the builder, no ads and no watermark on your menu. If it saves you time, a small voluntary donation is welcome, but nothing is locked behind it.

No. In the builder open the 📋 Import WP tab, pick your existing menu and click ↓ Import — all items, including one level of sub-items, land in MenuX ready to style. It takes about ten seconds.

MenuX renders its own menu wherever you place the block or shortcode; it doesn't touch your theme's menu. To hide the old one, remove the Navigation block from your header in the Site Editor (FSE themes), or unassign the menu from its theme location in Appearance → Menus (classic themes). Classic themes that call wp_nav_menu() — such as GeneratePress, OceanWP, Neve or Kadence — can instead use the WP Menu Integration panel to swap the theme menu automatically.

One configuration drives four locations — Primary, Footer, Sidebar and Mobile — and you assign each item to a location in the builder. For finer control, per-item page conditions let you show an item only on specific pages, so the same menu adapts page by page.

Yes. Every item has a visibility dropdown (everyone, logged-in, logged-out, or any specific WordPress role) plus a Schedule & Conditions section: a From/To date range, a daily time window (e.g. show "Lunch Menu" only 12:00–15:00, midnight-crossing supported), device targeting and campaign (UTM) rules. Ideal for member areas, limited-time promos and mobile-only items.

Open ⚡ Mega Menu, enable the toggle on a top-level item, then click ⚡ Edit Columns. Add up to 4 columns of headings, links (with icon and description), dividers, images or shortcodes. The 🎨 Appearance tab gives that specific panel its own background, colors and spacing, and ✨ Presets loads one of 20 ready-made industry templates. On mobile it folds into a clean accordion.

Yes to all three. Use the native MenuX block in the Site Editor and block editor; paste [menux] into Elementor, Divi, WPBakery or any classic theme. The menu is rendered server-side as plain HTML, so WP Rocket, LiteSpeed, W3 Total Cache and similar caching plugins can cache it freely.

Yes. MenuX detects installed multilingual plugins automatically and lets you set a label per language on each menu item.

Yes. The cart icon is part of the menu output, so it works with any theme whether you place the menu via the block or the [menux] shortcode. The mini-cart uses WooCommerce's native fragments for live, no-reload updates, and stays silent until WooCommerce is installed.

Open MenuX → Footer. The Setup Wizard builds a complete footer in under a minute across four steps (layout, theme, content, bottom bar). Then add the MenuX — Footer block to your footer template part, or paste [menux_footer] in a classic theme or page builder. Seven section types are available — About, Links, Contact, Social icons, Opening hours, Newsletter and Custom HTML — with 21 curated themes.

Add a Newsletter section and paste your list manager's form submission URL into the Form action URL field (for Mailchimp, the action="…" value from your embed code). MenuX renders a standard HTML form that posts directly to your provider — no API key, no server-side code. Leave the field blank and the form is skipped.

Yes. A single master toggle enables a full WCAG 2.2 AA layer: keyboard navigation, a visible focus ring, a skip link, ARIA labels, adequate touch-target sizes, reduced-motion support and a high-contrast mode.

No. The menu HTML and CSS are generated server-side, Font Awesome is bundled locally (no external request), and Google Fonts load only if you choose one. There's no heavy framework, so the footprint stays light and caching-friendly.

By default the plugin makes zero external requests — no tracking, no analytics, no cookies, no CDN calls. The only optional external connection is Google Fonts, and only if you explicitly select one in the Typography settings (see the External Services section). With no Google Font selected, there is nothing to add to your privacy policy.

Use Import / Export to save your full configuration — items, styles, mega menus, cart, announcement and footer — to a JSON file, then import it on another site to recreate everything exactly (it also doubles as a backup). Deactivating the plugin keeps everything; deleting it removes all its options and cached data from your database. If you might return, export first.

Yes. Target the .menux-container wrapper and its child elements from your theme's stylesheet or the Customizer's Additional CSS field.