Title: Menus office hours recap (Jan 28)
Author: Dave Martin (lessbloat)
Published: January 29, 2013
Last modified: February 7, 2013

---

 [  ](https://profiles.wordpress.org/lessbloat/) [Dave Martin (lessbloat)](https://profiles.wordpress.org/lessbloat/)
2:53 pm _on_ January 29, 2013     
Tags: [3.6 ( 65 )](https://make.wordpress.org/core/tag/3-6/),
[menus ( 31 )](https://make.wordpress.org/core/tag/menus/)   

# Menus office hours recap (Jan 28)

We’re still in the process of determining the best direction for menus in 3.6 (mock
ups and ideas welcome!).

My hope is that we can stay true to the [WordPress Philosophy](https://wordpress.org/about/philosophy/#clean)
by optimizing the experience for the majority of users, and leaving edge cases for
plugins to handle.

One issue at this stage is that I can only guess as to what the majority looks like.
I’m going to attempt to gather some data from WordPress.comWordPress.com An online
implementation of WordPress code that lets you immediately access a new WordPress
environment to publish your content. WordPress.com is a private company owned by
Automattic that hosts the largest multisite in the world. This is arguably the best
place to start blogging if you have never touched WordPress before. [https://wordpress.com/](https://wordpress.com/)
as to how many users have one menu vs. more than one vs. none. This should give 
us some additional insight into the best way to approach menus.

For this weeks meeting my goal was to list out, and then (roughly) prioritize the
biggest pain points associated with menus. Since I have little data at this point,
this prioritization is based on the assumption that the vast majority of users have
either no menus or one menu.

Here’s how I prioritized things, please weigh in if you disagree:

 * One of the biggest disconnects I’ve seen is the concept of “theme locations”.
   Adding a menu, and then assigning it to a theme location seems broken.
 * Trying to have menu management + editing + theme location assignment all on the
   same page is overwhelming.
 * Tabs don’t work for users with lots of menus to manage, and they confuse some
   users (who think they represent menu items within a single menu). Side note: 
   when we tested menu management via a drop down (instead of tabs), users didn’t
   notice the drop down, and wondered where the menus they had already created were.
   A “manage menus” tab appears to work for users, but it seems heavy for users 
   with just a single menu.
 * Switching themes poses a problem for menus in that there is no concept of a base
   menu. Every theme determines their own default menu, and even though two menus
   may have a single primary menu, you still have to re-assign your menu to that
   theme location whenever you switch a theme.
 * Users have a hard time visualizing how the menu changes they are making actually
   impact their blogblog (versus network, site)/site.
 * Having to scroll to see all of the menu item metaMeta Meta is a term that refers
   to the inside workings of a group. For us, this is the team that works on internal
   WordPress sites like WordCamp Central and Make WordPress. boxes in the left column
   can be annoying, and it can make discoverability for items below the fold harder.
 * If you have a long menu (with lot’s of menu items), you may be scrolling unreasonably
   down from the left to the right column.
 * The fact that you can add menus to a custom menu widgetWidget A WordPress Widget
   is a small block that performs a specific function. You can add these widgets
   in sidebars also known as widget-ready areas on your web page. WordPress widgets
   were originally created to provide a simple and easy-to-use way of giving design
   and structure control of the WordPress theme to the user. is not exposed anywhere.

Did I miss anything?

[#3-6](https://make.wordpress.org/core/tag/3-6/), [#menus](https://make.wordpress.org/core/tag/menus/)

### Share this:

 * [  Threads ](https://make.wordpress.org/core/2013/01/29/menus-office-hours-recap-jan-28/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/core/2013/01/29/menus-office-hours-recap-jan-28/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/core/2013/01/29/menus-office-hours-recap-jan-28/?share=bluesky)
 * [  X ](https://make.wordpress.org/core/2013/01/29/menus-office-hours-recap-jan-28/?share=x)
 * [  Facebook ](https://make.wordpress.org/core/2013/01/29/menus-office-hours-recap-jan-28/?share=facebook)
 * [  LinkedIn ](https://make.wordpress.org/core/2013/01/29/menus-office-hours-recap-jan-28/?share=linkedin)

 1.   ![](https://secure.gravatar.com/avatar/89bee1fa0a46ca3d923a0900048d920791949a66b779aca338268ddb3e7b5e52?
      s=32&d=mm&r=g)
 2.    [cvernon](https://profiles.wordpress.org/cvernon/)  3:26 pm _on_ January 29,
      2013
 3.   1.
       I agree theme locations isn’t working as it is now defined and managed.
 4.   Most sites I make & use have only one menu, so I do not declare theme locations
      at all in the theme. This is how it should work, that you don’t need to understand
      the concept of theme locations unless you have many menus and know how you want
      to organize them. This should all be hidden by default.
 5.   I like the idea of have the “base menu” concept just be a single menu that is
      not assigned a theme location, OR no menu at all in which case the fallback is
      to pull from all pages structure. Then if someone wants to get more complicated
      there should be another level of complication with multiple menus, in which case
      we want theme locations.
 6.   2.
       Also, the way the wp_nav_menu() behaves differently [generates different 
      htmlHTML HyperText Markup Language. The semantic scripting language primarily
      used for outputting content in web browsers., accepts different arguments] whether
      or not any menu is declared [just takes the existing pages], or whether the menu
      is assigned to a theme location. This is a template tagtag A directory in Subversion.
      WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.),
      the common convention of tags in version control systems. (Not to be confused
      with post tags.) issue but relates to how menus are managed in the adminadmin(
      and super admin) & database.
 7.   ![](https://secure.gravatar.com/avatar/c5a8ef92e2c96e80ead10c58086bdbfcd803797e40e45a409a8ff50d83bfb586?
      s=32&d=mm&r=g)
 8.    [deltafactory](https://profiles.wordpress.org/deltafactory/)  3:41 pm _on_ January
      29, 2013
 9.   I agree with every point here. Two more thoughts, based more in the pluginPlugin
      A plugin is a piece of software containing a group of functions that can be added
      to a WordPress website. They can extend functionality or add new features to 
      your WordPress websites. WordPress plugins are written in the PHP programming
      language and integrate seamlessly with WordPress. These can be free in the WordPress.
      org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
      or can be cost-based plugin from a third-party./api area:
 10.  The steps required to implement a “custom menu widgetWidget A WordPress Widget
      is a small block that performs a specific function. You can add these widgets
      in sidebars also known as widget-ready areas on your web page. WordPress widgets
      were originally created to provide a simple and easy-to-use way of giving design
      and structure control of the WordPress theme to the user.” are not obvious. At
      first glance at the code, it seems to rely on a complex interaction of both PHPPHP
      The web scripting language in which WordPress is primarily architected. WordPress
      requires PHP 7.4 or higher and JavascriptJavaScript JavaScript or JS is an object-
      oriented computer programming language commonly used to create interactive effects
      within web browsers. WordPress makes extensive use of JS for a better user experience.
      While PHP is executed on the server, JS executes within a user’s browser.
       [https://www.javascript.com](https://www.javascript.com/).
      The solution might be in documentation rather than changes to the code, but it’s
      still an area I would like to see improved.
 11.  I would really like to see some additional filters to enable better caching alternatives.
      Even with an object cache, constructing a large menu results in a high number
      of cache hits. I have seen some opportunities to cache the menu item objects 
      or even static HTMLHTML HyperText Markup Language. The semantic scripting language
      primarily used for outputting content in web browsers. and greatly improve that
      part of the page output.
 12.  If these requests aren’t out of scope, I can assist/suggest specific changes 
      to code.
 13.   * ![](https://secure.gravatar.com/avatar/5b77f265befadaec031a2d894cb8c689b0c686704546084a261b7fff7f25540a?
         s=32&d=mm&r=g)
       *  [Bob Gregor](https://profiles.wordpress.org/bobbravo2/)  10:00 pm _on_ January
         29, 2013
       * +1 on the unclear menu management APIAPI An API or Application Programming
         Interface is a software intermediary that allows programs to interact with
         each other and share data in limited, clearly defined ways.! I had almost 
         forgotten how I had to reverse engineer the custom menu widgetWidget A WordPress
         Widget is a small block that performs a specific function. You can add these
         widgets in sidebars also known as widget-ready areas on your web page. WordPress
         widgets were originally created to provide a simple and easy-to-use way of
         giving design and structure control of the WordPress theme to the user. to
         create a pluginPlugin A plugin is a piece of software containing a group of
         functions that can be added to a WordPress website. They can extend functionality
         or add new features to your WordPress websites. WordPress plugins are written
         in the PHP programming language and integrate seamlessly with WordPress. These
         can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
         or can be cost-based plugin from a third-party. menu item interface. Not clear
         at all.
 14.  ![](https://secure.gravatar.com/avatar/3621c46ef536910def30bd4ab2a23ee4933f309907584c2e671bef8241b1e615?
      s=32&d=mm&r=g)
 15.   [Philip Arthur Moore](https://profiles.wordpress.org/philiparthurmoore/)  3:
      43 pm _on_ January 29, 2013
 16.  >  One issue at this stage is that I can only guess as to what the majority looks
      > like. I’m going to attempt to gather some data from WordPress.comWordPress.
      > com An online implementation of WordPress code that lets you immediately access
      > a new WordPress environment to publish your content. WordPress.com is a private
      > company owned by Automattic that hosts the largest multisite in the world. 
      > This is arguably the best place to start blogging if you have never touched
      > WordPress before. [https://wordpress.com/](https://wordpress.com/) as to how
      > many users have one menu vs. more than one vs. none. This should give us some
      > additional insight into the best way to approach menus.
 17.  If my quick-and-dirty digging is correct, then only a very tiny handful of themes
      on WordPress.com use more than one menu in any significant manner, which means
      that the number of users who use more than one menu should be even smaller.
 18.   * Theme Locations: [https://gist.github.com/4665137](https://gist.github.com/4665137)
       * wp_nav_menu() usage: [https://gist.github.com/4665142](https://gist.github.com/4665142)
       * register_nav_menus() usage: [https://gist.github.com/4665147](https://gist.github.com/4665147)
       * register_nav_menu() usage: [https://gist.github.com/4665151](https://gist.github.com/4665151)
       * Fallback Menu Usage: [https://gist.github.com/4665165](https://gist.github.com/4665165)
 19.  I’d highly recommend approaching this problem with the direction that users will
      primarily need one custom menu for their blogblog (versus network, site), with
      the caveat that I’m sure the case could be made for more if a theme is more CMS-
      centric.
 20.   * ![](https://secure.gravatar.com/avatar/df4e84176d328d48e01ba995e523b1f219143d215f68c9f323e2b2bb78062720?
         s=32&d=mm&r=g)
       *  [lessbloat](https://profiles.wordpress.org/lessbloat/)  4:14 pm _on_ January
         29, 2013
       * Thanks for pulling this together Philip!
       * > If my quick-and-dirty digging is correct, then only a very tiny handful 
         > of themes on WordPress.comWordPress.com An online implementation of WordPress
         > code that lets you immediately access a new WordPress environment to publish
         > your content. WordPress.com is a private company owned by Automattic that
         > hosts the largest multisite in the world. This is arguably the best place
         > to start blogging if you have never touched WordPress before. [https://wordpress.com/](https://wordpress.com/)
         > use more than one menu in any significant manner
       * A couple thoughts:
          - My guess is that this is true for themes in general. So, I’m not sure how
            far off it is compared to wp.org usage.
          - Menus can also be added within widgets. My guess is that out of users who
            have multiple menus, chances are the majority of them only have one theme
            location menu, in addition to one or more custom menu widgets (again, just
            a hunch).
          - Even if all we get out of this is a better picture of how many users have
            no menus vs. one menu, I’d still find that hugely insightful.
       * > I’d highly recommend approaching this problem with the direction that users
         > will primarily need one custom menu for their blogblog (versus network, 
         > site)
       * My gut agrees with you 100%. But it never hurts to at least attempt to back
         assumptions up with some data 😉
          - ![](https://secure.gravatar.com/avatar/5b77f265befadaec031a2d894cb8c689b0c686704546084a261b7fff7f25540a?
            s=32&d=mm&r=g)
          -  [Bob Gregor](https://profiles.wordpress.org/bobbravo2/)  10:02 pm _on_
            January 29, 2013
          - My experience with theme / custom WordPress development has shown that 
            98% of my client sites (wp.org) use just 1 menu location / no menu widgets.
          - ![](https://secure.gravatar.com/avatar/3ddae941d25b362e02f9870d27cbb848c7dbb57a56a8297fbb2f9c3db8cc63a6?
            s=32&d=mm&r=g)
          -  [Ricky Lee](https://profiles.wordpress.org/rickylee/)  12:23 am _on_ January
            31, 2013
          - Having built close to 100 themes since release of Menus, I can say 1 primary
            and 30% of time using depth=1 for footer menu is correct. Just started 
            using Theme Location attribute since switching to _s as our base theme 
            before we gave clients Editor level permissions and named menu “Main”.
 21.  ![](https://secure.gravatar.com/avatar/67bb030a417af66d3124160e28a0fdcc59b6f130e75e84b0cd1a2cdd98daea98?
      s=32&d=mm&r=g)
 22.   [Frankie Jarrett](https://profiles.wordpress.org/fjarrett/)  4:01 pm _on_ January
      29, 2013
 23.  Great to see this list of pain ponts in priority. The more I think about it, 
      the more I am liking the concept of a “base menu”.
 24.  I just have a few more to add, which could perhaps fall under something already
      mentioned above, but I wanted to mention them anyway.
 25.  1. Some users are finding it difficult to figure out how to nest menu items and
      create levels. There is no visual representation on the Menus screen that would
      suggest items can be clicked and dragged to the right to perform nesting.
 26.  2. When adding a new item to a menu it is automatically appended to the end. 
      This can create headaches for menus that are very long. It would be great to 
      see the UIUI User interface supporting drag and drop of the items directly into
      the menu list, similar to how widgets are placed in a sidebarSidebar A sidebar
      in WordPress is referred to a widget-ready area used by WordPress themes to display
      information that is not a part of the main content. It is not always a vertical
      column on the side. It can be a horizontal rectangle below or above the content
      area, footer, header, or any where in the theme. area.
 27.  3. Requiring that users go to Screen Options in order to select additional item
      fields (class, description, etc.) seems counterintuitive. It would seem that 
      a simple “view more/view less” accordion could reveal the additional fields on
      a per-item basis.
 28.  ![](https://secure.gravatar.com/avatar/ca20d16a7871a44d060a80ad572c90be25dd5b73212b0a839fb0474e623ee357?
      s=32&d=mm&r=g)
 29.   [Joey Kudish](https://profiles.wordpress.org/jkudish/)  4:58 pm _on_ January
      29, 2013
 30.  > I’m going to attempt to gather some data from WordPress.comWordPress.com An
      > online implementation of WordPress code that lets you immediately access a 
      > new WordPress environment to publish your content. WordPress.com is a private
      > company owned by Automattic that hosts the largest multisite in the world. 
      > This is arguably the best place to start blogging if you have never touched
      > WordPress before. [https://wordpress.com/](https://wordpress.com/) as to how
      > many users have one menu vs. more than one vs. none.
 31.  I went ahead and got this data for you. I selected 4 random sets of 1000 WordPress.
      com blogs that have had wp-adminadmin (and super admin) activity in the month
      of January 2013. I then calculated for each blogblog (versus network, site) how
      many menus they have (total, so regardless of how that menu is being used) and
      collated the results. 75.78% of blogs have no menus; 18.23% have 1 menu; 5.925%
      have more than 1 menu.
 32.  I put together the full breakdown of my calculations here: [https://docs.google.com/spreadsheet/ccc?key=0AszYZoR3BU_jdHJmZHRTQ19PcGdHSWhhempWRzBDeHc#gid=0](https://docs.google.com/spreadsheet/ccc?key=0AszYZoR3BU_jdHJmZHRTQ19PcGdHSWhhempWRzBDeHc#gid=0).
 33.  Let’s keep in mind that this is WordPress.com users and not self-hosted users,
      and I suspect there is a significant higher amount of “power users” on the .org
      side, who use menus differently, via widgets (which is possible on WP.com), and
      by calling directly `wp_nav_menu` in their custom themes/plugins (which is not
      possible on WP.com).
 34.  Hope this helps with deciding how to proceed.
 35.   * ![](https://secure.gravatar.com/avatar/df4e84176d328d48e01ba995e523b1f219143d215f68c9f323e2b2bb78062720?
         s=32&d=mm&r=g)
       *  [lessbloat](https://profiles.wordpress.org/lessbloat/)  5:48 pm _on_ January
         29, 2013
       * Very cool. Thanks so much for tackling this @jkudish! Even with your disclaimers
         in mind, I find this data insightful.
       * Here’s a pie chart of the breakdown:
       * ![](//i2.wp.com/f.cl.ly/items/3A1j3t2Z1M0z1l1t172g/menus-breakdown.jpg)
 36.  ![](https://secure.gravatar.com/avatar/6845456dbc9056f20a4cd50a6b95db78f2ae31df5c0601c613ee5b8939c41a82?
      s=32&d=mm&r=g)
 37.   [Jon Brown](https://profiles.wordpress.org/jb510/)  5:50 pm _on_ January 29,
      2013
 38.  Maybe a crazy idea and maybe overly influenced by my personal preference for 
      building on Genesis… But what about getting rid of theme locations all together
      in favor of a single primary menu location that automatic tied to the primary
      menu and making the rest widgetWidget A WordPress Widget is a small block that
      performs a specific function. You can add these widgets in sidebars also known
      as widget-ready areas on your web page. WordPress widgets were originally created
      to provide a simple and easy-to-use way of giving design and structure control
      of the WordPress theme to the user. areas? (note I think the widget UIUI User
      interface is in far greater need of a make over than the menus, but that’s definitely
      OT here). My initial thought is additional menu areas would show up on the widget
      page and custom menu widget widgets could be dragged in?
 39.  I’d thought a while back that menus should be more like links were. An interface
      to build the link list/menu, but not the interface that actually places menus/
      links on the page/theme.
 40.  Note, don’t know that I love the idea, I typically build custom themes with 3
      menu areas (above headerHeader The header of your site is typically the first
      thing people will experience. The masthead or header art located across the top
      of your page is part of the look and feel of your website. It can influence a
      visitor’s opinion about your content and you/ your organization’s brand. It may
      also look different on different screen sizes., below header, footer), but separating
      placement of menus and construction of menus sounds like a great idea.
 41.  ![](https://secure.gravatar.com/avatar/df4e84176d328d48e01ba995e523b1f219143d215f68c9f323e2b2bb78062720?
      s=32&d=mm&r=g)
 42.   [lessbloat](https://profiles.wordpress.org/lessbloat/)  8:32 pm _on_ January
      29, 2013
 43.  So, what if we used the number of menus a user has to determine what they should
      see. Here are my latest thoughts:
 44.  
      ### If they have 0 menus
      
 45.  _About 76% of users would see this (based on [WordPress.com’s stats](https://make.wordpress.org/core/2013/01/29/menus-office-hours-recap-jan-28/#comment-7828))._
 46.  They’d see:
 47.  [[
 48.   * We’d auto populate the “blank slate” view with all of their existing pages.
         However, this menu is not actually created until they click “Save Menu”. If
         they navigate away from this page without clicking “Save Menu”, they will 
         still technically have zero menus.
       * If they have only one theme location, we’d just use the theme location name(
         i.e. primary) as the menu name, and we’d auto assign this menu to their theme
         location upon saving.
       * We’d hide all “manage menus” functionality
       * And test using an accordion for the menu item options on the left (vs. metaMeta
         Meta is a term that refers to the inside workings of a group. For us, this
         is the team that works on internal WordPress sites like WordCamp Central and
         Make WordPress. boxes).
 49.  So, if a user (with zero menus) came to the screen above, and immediately clicked“
      Save Menu”, they’d see:
 50.  [[
 51.  
      ### If they have 1 menu
      
 52.  _About 18% of users (based on WordPress.comWordPress.com An online implementation
      of WordPress code that lets you immediately access a new WordPress environment
      to publish your content. WordPress.com is a private company owned by Automattic
      that hosts the largest multisite in the world. This is arguably the best place
      to start blogging if you have never touched WordPress before. [https://wordpress.com/](https://wordpress.com/)’
      s stats)._
 53.  They’d see
 54.  [[
 55.   * We’d take them directly to the edit screen for that menu.
       * We’d hide all “manage menus” functionality
 56.  So, based on the above approach (and the stats from WordPress.com), **94% of 
      users would never see the management screen**.
 57.  
      ### If they have more than 1 menu
      
 58.  After landing on menus, they’d see something like this:
 59.  [[
 60.  Clicking on a menu would take them to something like:
 61.  [[
 62.  Clicking the blue “Menus” headerHeader The header of your site is typically the
      first thing people will experience. The masthead or header art located across
      the top of your page is part of the look and feel of your website. It can influence
      a visitor’s opinion about your content and you/ your organization’s brand. It
      may also look different on different screen sizes. link (vs. showing tabs here),
      or the “menus” link under “Appearance” in the left nav would take them back to
      the manage menus view.
 63.  
      ### When adding a menu
      
 64.  Users would see:
 65.  [[
 66.  and then after creating their menu, if they had a single menu:
 67.  [[
 68.  If they had multiple menus, we’d link up “Menus” in the header.
 69.  
      ### Other considerations
      
 70.  **Switching themes**
 71.  If a user has one menu, and the new theme has one theme location, and the user
      has no custom menu widgets, can we just auto-assign the existing menu to the 
      theme location upon switching?
 72.  **Long menus (with lot’s of items)**
 73.  This makes menus hard to manage because you have to scroll to see all of your
      menu items, and when you add new menu items, they are added to the bottom by 
      default.
 74.  My preference (again based on usage stats) would be to keep this in pluginPlugin
      A plugin is a piece of software containing a group of functions that can be added
      to a WordPress website. They can extend functionality or add new features to 
      your WordPress websites. WordPress plugins are written in the PHP programming
      language and integrate seamlessly with WordPress. These can be free in the WordPress.
      org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
      or can be cost-based plugin from a third-party. territory. This seems like it
      would make a great little plugin that could:
 75.  1) Add collapsable tree functionality for menu items
       2) modify the “Add to Menu”
      button under each menu option to be a split button “Add to top”/”Add to Bottom”,
      and 3) include drag and drop of menu items from the left.
 76.  I don’t feel like this functionality should be exposed to the majority of users.
 77.  Thoughts?
 78.   * ![](https://secure.gravatar.com/avatar/ca20d16a7871a44d060a80ad572c90be25dd5b73212b0a839fb0474e623ee357?
         s=32&d=mm&r=g)
       *  [Joey Kudish](https://profiles.wordpress.org/jkudish/)  8:57 pm _on_ January
         29, 2013
       * This seems like the logical way to proceed based on everything that we’ve 
         talked about and worked on thus far. I’ll try to gather more usage stats about
         how users use menus from WordPress.comWordPress.com An online implementation
         of WordPress code that lets you immediately access a new WordPress environment
         to publish your content. WordPress.com is a private company owned by Automattic
         that hosts the largest multisite in the world. This is arguably the best place
         to start blogging if you have never touched WordPress before. [https://wordpress.com/](https://wordpress.com/)
         before our next office hours on Thursday.
          - ![](https://secure.gravatar.com/avatar/5b77f265befadaec031a2d894cb8c689b0c686704546084a261b7fff7f25540a?
            s=32&d=mm&r=g)
          -  [Bob Gregor](https://profiles.wordpress.org/bobbravo2/)  10:17 pm _on_
            January 29, 2013
          - Thanks for those stats! Any chance you can find some stats on # of menu
            items?
          - I think that will be very indicative of how we proceed with the UIUI User
            interface.
          - heres another view of the data you shared: [http://cl.ly/image/143B0G3x2y3A](http://cl.ly/image/143B0G3x2y3A)
            definitely looks like a normal distribution.
             * ![](https://secure.gravatar.com/avatar/ca20d16a7871a44d060a80ad572c90be25dd5b73212b0a839fb0474e623ee357?
               s=32&d=mm&r=g)
             *  [Joey Kudish](https://profiles.wordpress.org/jkudish/)  2:47 pm _on_
               January 30, 2013
             * Yes, I’ll gather more stats by Thursday afternoon and will include #
               of menu items per menu in that stat as well. Stay tuned.
       * ![](https://secure.gravatar.com/avatar/df4e84176d328d48e01ba995e523b1f219143d215f68c9f323e2b2bb78062720?
         s=32&d=mm&r=g)
       *  [lessbloat](https://profiles.wordpress.org/lessbloat/)  2:12 pm _on_ January
         30, 2013
       * Here’s an alternate flow that we may consider for when users have more than
         one menu. It ditches the management screen altogether in favor of a drop down.
       * [[
       * We tested [using a drop down](https://core.trac.wordpress.org/ticket/23119#comment:2)
         before (and it tested poorly), but I don’t think we put enough emphasis on
         it. It’s worth testing again, as long as it doesn’t overwhelm users (having
         so much on the same page).
       * I also played around with adding check boxes under “use in”, as technically
         a user could use a single menu in multiple theme locations. I wonder if we
         could allow the user to select a widgetWidget A WordPress Widget is a small
         block that performs a specific function. You can add these widgets in sidebars
         also known as widget-ready areas on your web page. WordPress widgets were 
         originally created to provide a simple and easy-to-use way of giving design
         and structure control of the WordPress theme to the user. placement from this
         screen as well via a check box. If they checked “Main SidebarSidebar A sidebar
         in WordPress is referred to a widget-ready area used by WordPress themes to
         display information that is not a part of the main content. It is not always
         a vertical column on the side. It can be a horizontal rectangle below or above
         the content area, footer, header, or any where in the theme.”, we’d auto-add
         a custom menu widget to the botom of the main sidebar widget area, and set
         the title of the custom menu widget as the name of the menu.
          - ![](https://secure.gravatar.com/avatar/27e1ec1c5ddd320f2cca5aa10cdf696b132db9230fa77ed87df5ca3c3ba6cbd9?
            s=32&d=mm&r=g)
          -  [Scott Taylor](https://profiles.wordpress.org/wonderboymusic/)  6:18 pm
            _on_ January 30, 2013
          - I like the dropdown at the top when there’s > 1 menus
       * ![](https://secure.gravatar.com/avatar/846d7a5465e8a3dbc89b56b75d63e8285504db5a889cb764c3bb6e351bbf9deb?
         s=32&d=mm&r=g)
       *  [kwight](https://profiles.wordpress.org/kwight/)  8:14 pm _on_ January 30,
         2013
       * Do we even need the Optional Settings part in the 0 menus layout, as that’s
         default behaviour anyways?
       * Also, +1 for your handling of long menus in pluginPlugin A plugin is a piece
         of software containing a group of functions that can be added to a WordPress
         website. They can extend functionality or add new features to your WordPress
         websites. WordPress plugins are written in the PHP programming language and
         integrate seamlessly with WordPress. These can be free in the WordPress.org
         Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
         or can be cost-based plugin from a third-party. territory.
 79.  ![](https://secure.gravatar.com/avatar/846d7a5465e8a3dbc89b56b75d63e8285504db5a889cb764c3bb6e351bbf9deb?
      s=32&d=mm&r=g)
 80.   [kwight](https://profiles.wordpress.org/kwight/)  8:11 pm _on_ January 30, 2013
 81.  +1 for the Dropdown. I expect it would test better in this format, as it’s distinguishable
      from the other side metaboxes (by, um, not being on the side), unlike the current
      layout.
 82.  ![](https://secure.gravatar.com/avatar/5b77f265befadaec031a2d894cb8c689b0c686704546084a261b7fff7f25540a?
      s=32&d=mm&r=g)
 83.   [Bob Gregor](https://profiles.wordpress.org/bobbravo2/)  9:17 pm _on_ January
      30, 2013
 84.  part of the problem with the discussion is that there is a large variety of use
      cases. Here is a visual: [http://cl.ly/image/3t0i3g2Y1G0y](http://cl.ly/image/3t0i3g2Y1G0y)
 85.  The # of menus data shows the right column to be the typical use case. # of items
      data is TBD
 86.  ![](https://secure.gravatar.com/avatar/e05110ddfc422ecfc3c68f61f2b08a404343ef8514fed12b460fc9c9aaa47d27?
      s=32&d=mm&r=g)
 87.   [Helen Hou-Sandi](https://profiles.wordpress.org/helen/)  9:25 pm _on_ January
      30, 2013
 88.  As much of a problem as theme locations are, I don’t think moving the assignment
      into the editing of a given menu is the solution. We are then adding a problem
      of what happens if multiple menus are assigned to the same location, because 
      it then becomes possible to do so.
 89.  Have some other thoughts I need to chew on. Will comment again when I have sentences
      🙂
 90.   * ![](https://secure.gravatar.com/avatar/df4e84176d328d48e01ba995e523b1f219143d215f68c9f323e2b2bb78062720?
         s=32&d=mm&r=g)
       *  [lessbloat](https://profiles.wordpress.org/lessbloat/)  3:37 am _on_ January
         31, 2013
       * I had two thoughts here. If a theme location currently has a menu assigned
         to it, we could :
       * 1) append the name of that menu (perhaps at #999), something like:
       * ![](//i1.wp.com/f.cl.ly/items/2Y2d3n0B1V1e1u1o1C1g/currently-assigned.jpg)
       * and/or…
       * 2) onclick trigger a JSJS JavaScript, a web scripting language typically executed
         in the browser. Often used for advanced user interfaces and behaviors. confirmation
         modal that says something to the effect of, “Are you sure you want to change
         your primary theme location from “Primary Menu” to “Main Navigation”?”.
 91.  ![](https://secure.gravatar.com/avatar/87f8c2bbfabbae3462bbab2c83ce82763c7ff91bc632b64f3af7e24d929633f6?
      s=32&d=mm&r=g)
 92.   [Aaron D. Campbell](https://profiles.wordpress.org/aaroncampbell/)  10:41 pm
      _on_ January 30, 2013
 93.  There was plenty of discussion at the beginning of dev chat: [https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2013-01-30&sort=asc#m543523](https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2013-01-30&sort=asc#m543523)
 94.  It seems like [http://f.cl.ly/items/3y2I0T1q2u3d3G3O0X1h/menus-multiple-select.png](http://f.cl.ly/items/3y2I0T1q2u3d3G3O0X1h/menus-multiple-select.png)
      is pretty close and worth testing, with the one concern being the settings where
      a menu is assigned to a location.
 95.  ![](https://secure.gravatar.com/avatar/de70e9de702178bf758acb9e4265259c2772bd01b7581cc656fa37c222787e09?
      s=32&d=mm&r=g)
 96.   [Robert Chapin (miqrogroove)](https://profiles.wordpress.org/miqrogroove/)  
      10:59 pm _on_ January 30, 2013
 97.  It’s still difficult to add tags to a menu. I tend to fall back on making a list
      of custom URLs when I can’t find things. It’s usually easier and faster too.
 98.  Assigning menus is definitely broken. Every time I activate a theme on a new 
      site it looks messed up. There should be menus assigned by default when assignments
      are missing.
 99.   * ![](https://secure.gravatar.com/avatar/87f8c2bbfabbae3462bbab2c83ce82763c7ff91bc632b64f3af7e24d929633f6?
         s=32&d=mm&r=g)
       *  [Aaron D. Campbell](https://profiles.wordpress.org/aaroncampbell/)  11:13
         pm _on_ January 30, 2013
       * Go to Screen Options, check the “tags” box, and then add them like you add
         anything else (check boxes on left and use “Add to Menu” button).

Comments are closed.

# Post navigation

[← Editorial Flow office hours today Tuesday at 1800…](https://make.wordpress.org/core/2013/01/29/editorial-flow-office-hours-today-tuesday-at-1800/)

[Post Formats UI Update, 1/28 →](https://make.wordpress.org/core/2013/01/30/post-formats-ui-update-128/)