Consider how to use 'Shortcuts' and 'Create' menus distinctly

Created on 20 December 2024, 4 months ago

Problem/Motivation

The new 'Create' menu in navigation is a handy way to provide links to create things. Similarly, 'Shortcuts' allows providing links to create common items, as well as other tasks that don't involve creating.

Currently, the 'Shortcuts' menu is almost entirely links to create things. Should these be moved to the 'Create' menu? But if we do that, we are left with only 'Extend your site'.

Proposed resolution

Agree on a strategy for this so the links are not duplicated and recipes can take a consistent approach, and then make any changes required.

📌 Task
Status

Active

Component

User Interface

Created by

🇦🇺Australia pameeela

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @pameeela
  • 🇮🇳India diwakar07

    To improve the current implementation of Shortcuts, a good starting point could be to retain the essential options, such as 'Extend your site' and 'Setup a redirect,' while removing other shortcuts related to recipes which it is already available under the 'Create' menu to eliminate redundancy.

  • 🇦🇺Australia pameeela

    @diwakar07 that's what I said in the issue summary. But 'Set up a redirect' is also a 'Create' task. So this would leave only one thing in the shortcuts menu, which is not ideal.

  • Merge request !363Resolve #3495202 "Remove shortcuts" → (Merged) created by pameeela
  • 🇦🇺Australia pameeela

    Discussed with @ckrina in Slack and we agreed to remove Shortcuts for now. Updated IS (and I think ckrina will comment further tomorrow, just wanted to get it moving in the meantime).

  • 🇺🇸United States phenaproxima Massachusetts

    For the record, no code objections from me. I'll leave the RTBC to someone else (probably @ckrina) but I'm fine with committing this as-is.

  • Pipeline finished with Failed
    3 months ago
    Total: 2051s
    #384339
  • 🇮🇳India rushiraval

    Yes, Shortcuts is confusing with same option available in create. So We should remove duplication. But we have to provide shortcut module with CMS but it should not be installed. If any user require for any other shortcut then It may be useful.

  • 🇬🇧United Kingdom catch

    This will also as a side effect improve the loading of the navigation toolbar, see 📌 Consider a more substantial shortcuts placeholder Active (which partially improves it). I did notice the duplication when testing that issue, better to free up the vertical space.

  • 🇺🇸United States phenaproxima Massachusetts
  • 🇪🇸Spain ckrina Barcelona

    Agreed that they perform the same task nowadays and it's confusing. Keeping a Shortcuts menu doesn’t make a lot of sense:

    • If clients want an specific project menu, they can create one and place it there. AFAIK even per role.
    • If they really want Shortcuts, this menu is confusing because doesn’t behave as users expect.

    From ours tests with Navigation, it was clear most users understood “Shortcuts” as “own”(per user) items or customizable per role, but also it’s supported by @pcambra's research in 🌱 Improvements on Shortcut module Active (His research also shows other improvement the Shortcuts module needs and that I would love to get done eventually).

    So agreed on having a real “most visited” or “favorites” feature, as a long hanging fruit in the next months. Meanwhile, I’d disable the Shortcuts module.

    Moving to RTBC to +1 this, but I think the MR shows a conflict that will need to be resolved.

  • 🇺🇸United States phenaproxima Massachusetts
  • Pipeline finished with Skipped
    3 months ago
    #385782
  • 🇺🇸United States phenaproxima Massachusetts

    Good simplification, and the fact that we removed the Shortcut module means there's a slight performance improvement afoot too. Merged into 1.x and cherry-picked to 1.0.x. Thanks!

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024