Skip to main content

Menu Builder v2

Improvement

We would like to create a new version of Menu Builder, which overhauls both the existing UI as well as behind the scenes structure… no small update! We are excited to get your input and feedback to help shape its future.

Below we will outline our current plan for the future based on any older feature requests relating to Menu Builder along with any feedback we have collected to date.

If you have any questions, ideas or input on what you would like to see in Menu Builder next, please let us know by commenting on this feature request. Discussion is also welcome!

—

Structure

  • Remove the use of database items on Menu - json instead for structure

  • Simplify the menu layout structure

  • Update the default layout to cater to drop downs

  • Add either a optional text field to add a logo, or ideally custom fields (at a minimum: Link Title (text), Link Icon (file), Onclick (text))

  • Add the ability to enable/disable menu items

UI / UX

  • Keep existing drag & drop functionality

  • Data from across the site needs to be accessible, including search and filter functionality

  • Ability to add a blank empty new menu item

  • Ability to add items directly into a specific location in the menu, rather than adding a new item at the top level and then needing to move it to the desired location.

  • Ability to split menu into columns or groups and access those from the layout

Data that needs to be accessible to the user when adding menu items:

  • Pages

  • WebApp items

  • Module items

  • Category pages

Posted by Martin Sanderson ·
Status: Next up12 comments

Log in to comment and vote

Comments12

  • Rox Dawson

    •

    Jul 27, 2023

    Some really good ideas here. I initially thought I would like broader than Pages, WebApps, Modules and Categories, with Content Sections, Code Snippets etc also included as my thoughts around creating Mega Menus.

    I love the idea of JSON for the data, enable / disable (great for getting ready for a site update), ability to search/filter for the item to add (important for larger sites), accessibility considerations and Custom fields so it is extensible and future proof.

    Important for the design of any of the non Site Manager components is ease of use for less technical people / end users, who will end up managing the site.

  • Luke Wakefield changed status to Planned
    Team•

    Jun 20, 2023

  • Matt Jones

    •

    Apr 24, 2023

    I've just thought, it might be useful to be able to assign secure zones to menu items, as that would allow the menu to display items only to those with correct level of authorization without custom code.

    Nice to have: it could inherit that setting from the page you selected when adding to the menu, but perhaps allow for it to be overwritten.

  • Matt Jones

    •

    Dec 12, 2022

    I don't understand what is meant by this bullet point: "Ability to add items directly in the menu so you can output specifically in the branch you need - useful for larger menus" Please can you clarify?

    Agree this sounds like a great idea. It will be especially helpful with builidng more interesting SiteBuilder Layouts.

    One small feature whuch might help with this would be an optional text field to add a logo (perhaps as SVG) to a menu item https://roadmap.siteglide.com/core-platform/p/menu-builder-improvements. Josh's idea of custom fields solves this from the perspective of most users, but for SiteBuilder it's helpful if we have a few core fields which can work across agencies and sites.

    • Martin Sanderson

      •

      Dec 12, 2022

      Matt Jones: Sure :)

      I don't understand what is meant by this bullet point: "Ability to add items directly in the menu so you can output specifically in the branch you need - useful for larger menus" Please can you clarify?

      ^ this feedback refers to the ability to add an item directly into any location of the menu, rather than needing to add it at the top level and then go and move it to the desired location. I've updated the OP to make this a little clearer.

      optional text field to add a logo - great idea thanks, I've added this to the OP.

  • Josh Carter

    •

    Dec 12, 2022

    Looking forward to hearing more about this!

    Custom fields for this would be a big win, with the usual data types.

    • Martin Sanderson

      •

      Dec 12, 2022

      Josh Carter: great idea thanks I've included that.

  • Matt Walter changed status to In Review
    Team•

    Nov 10, 2022

  • Matt Walter changed status to In Review
    Team•

    Apr 6, 2022

  • Matt Walter changed status to In Review
    Team•

    Apr 6, 2022

  • Urszula Richards

    •

    Sep 28, 2020

    Bumping this one up, in case it is not a big thing to do. It creates extra work for us to recreate created menu items, particularly when we are testing something and want to switch on and off - off if it isn't working and on if it is. We need to completely remove an item and recreate it each time currently.

  • Devon Reehl

    •

    Aug 3

    •

    Merged request

    •

    1 vote

    Menu Builder improvements

    Some things that could make Menu builder better:

    Create an Item - Currently I have to click on a page that exists and then rename or relink it - I should be able to create a menu item that’s blank.

    Accordion functionality - It’s nice to have, but it’s very cumbersome working with large menus because each time you come back to the menu the accordions default to open and you have to scroll or look through them.

    Page list - Allow us to search pages to filter the long list (if this UI setup is still used)