[META][UX] Killer menu features.

[klonos]

This is a list of UX issues that are related to menus. Implementing these features will make us stand out when compared to Drupal and aim to cause the same awe and respect as layouts.

• Make menu items translatable in core #225 | Make menu items translatable in core.
• [UX] Provide a menu-centric workflow for creating the website structure (à la content_menu) #434 | [META][UX] Provide a menu-centric workflow for creating the website structure (à la content_menu).
  • [UX][D8] Allow menu items to be created even if no page exists at that path #422 | [UX] Allow menu items to be created even if no page exists at that path.
• Add Menu Block features to core (feature parity with D8). #845 | Add Menu Block features to core (feature parity with D8).
• [UX] Allow bulk-adding/editing vocabulary terms and menu items. #1006 | [UX] Allow bulk-adding/editing vocabulary terms and menu items.
• [D8][UX] Merge Special Menu Items module functionality in core (allow <nolink> and <separator> menu items). #1840 | [UX] Merge Special Menu Items module functionality in core (allow <nolink> and <separator> menu items).
• Add a menu-styles API into core #1457 | [UX] Provide responsive drop-down menus out of the box.
• Add icons to the Admin Bar #1841 | Add icons to the Admin Bar
• Allow adding (font-)icons to menu items #3819 | Allow adding (font-)icons to menu items
• [UX] Layouts: Allow menu "source" to be changed from within any menu block #3820 | [UX] Layouts: Allow menu "source" to be changed from within any menu block

Not killer-features but resolving annoyances compared to the respective Drupal UX:

• [UX][D8] Merge the "List links" and "Edit menu" operations into a single administration page. #475 | [UX] Clean up & simplify the menu administration by merging the "List links" and "Edit menu" operations into a single administration page.
• [UX] Allow bulk deleting menu links. #732 | [UX] Allow bulk deleting menu links.
• [UX] Menu items: Do not replace the menu item path alias with the respective node ID. #1793 | Menu items: Do not replace the menu item path alias with the respective node ID.
• [UX] Remove the menu settings page #1278 | [UX] Remove the menu settings page
• [D8][UX] Menus: convert the "Path" text field to an autocomplete field. #2007 | [UX] Menus: convert the "Path" text field to an autocomplete field.
• [D9][UX] Add a user-friendly parent menu browser in the content add/edit form. #3029 | [UX] Add a user-friendly parent menu browser in the content add/edit form.
• Allow limiting access to menu items per-role #4465 | Allow limiting access to menu items per-role
• [D9][UX] Remove the weight field from the menu item edit form and the node edit form #4466 | [D9][UX] Remove the weight field from the menu item edit form and the node edit form

Not killer-features per se, but for "marketing purposes":

• [UX][WP][D8] Allow the admin bar to be docked in various sides of the screen #1842 | [UX] Allow the admin bar to be docked in various sides of the screen (feature parity with D8).

Feel free to add more issues with menu-related feature requests.

[wesruv]

Going to help with this, starting with responsive menu out of the box.

[biolithic]

Keep in mind void menu exists in contrib
On May 19, 2016 4:02 PM, "wesruv" [email protected] wrote:

Going to help with this, starting with responsive menu out of the box.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#1839 (comment)

[klonos]

@wesruv 👍 ...let me know when you have a sandbox or private repo branch you want testing and feedback for.

@biolithic thanx, I wasn't aware of void_menu. Sounds like its features could/should be merged in special_menu_items:

Based off of the work done in special_menu_items and menu_firstchild

...I'm particularly interested in this:

...The benefit to using this module over special_menu_items for this is that your menus will not require any additional styling to account for the added span tags used by special_menu_items,...

So the issue here IIUC is that special_menu_items adds span tags that make it harder for the menu items provided by it to work out of the box with themes.

...and will be W3C valid because every anchor must have an href attribute.

This statement is not true : https://w3c.github.io/html/links.html#links-created-by-a-and-area-elements

NOTE
The href attribute on <a> and <area> elements is not required; when those elements do not have href attributes they do not create hyperlinks.

[biolithic]

I've just used Void Menu module for projects, that's all.

On Thu, May 19, 2016 at 6:34 PM, Gregory Netsas [email protected]
wrote:

@wesruv https://github.com/wesruv 👍 ...let me know when you have a
sandbox or private repo branch you want testing and feedback for.

@biolithic https://github.com/biolithic thanx, I wasn't aware of
void_menu. Sounds like its features could/should be merged in
special_menu_items:

Based off of the work done in special_menu_items and menu_firstchild

...I'm particularly interested in this:

...The benefit to using this module over special_menu_items for this is
that your menus will not require any additional styling to account for the
added span tags used by special_menu_items,...

So the issue here IIUC is that special_menu_items adds span tags that make
it harder for the menu items provided by it to work out of the box with
themes.

...and will be W3C valid because every anchor must have an href attribute.

This statement is not true :
https://w3c.github.io/html/links.html#links-created-by-a-and-area-elements

NOTE
The href attribute on and elements is not required; when those
elements do not have href attributes they do not create hyperlinks.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#1839 (comment)

[klonos]

Forgot to tick the "drop-down menus out of the box" task of the list 😉