Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Marketplace Menus: πŸͺ©πŸ₯‚πŸΎβœ¨ and next steps #2426

Open
4 tasks done
rosschapman opened this issue May 27, 2024 · 0 comments
Open
4 tasks done

Marketplace Menus: πŸͺ©πŸ₯‚πŸΎβœ¨ and next steps #2426

rosschapman opened this issue May 27, 2024 · 0 comments
Assignees
Labels
🌱 Ready for Dev Stuff we are able to move forward on

Comments

@rosschapman
Copy link
Contributor

rosschapman commented May 27, 2024

πŸš€πŸ˜€πŸ₯³πŸ‘ŒπŸ½ Menus are a thing now!

Last week we released the first iteration of improving the ordering experience on the Marketplaces. This effort was initially kicked off with a request from our client Piikup for more control over how Marketplace Products were displayed, including product order and gouping: #2340. Effectively this meant allowing configuration of menus -- a common behavior of retail web applications.

Here's all the bodacious, beautiful code from this initial release:

  1. Adds positioning Gem Β #2390
  2. Adds is_group and position column to Marketplace TagsΒ #2391
  3. Removes Bazaar association from TagsΒ #2408
  4. Space admins can create "Menu/Product Groups" and reorder them for display on their marketplaceΒ #2361

✨🀩🌿 Menus twisted our arm to refactor

Beyond enabling better segregation of products into menu "sections" (eh, terminology WIP) (ie sub-menus, or topical groupings), this work provided additional utility as a vessel for interrogations of our domain model and marketplace management UI. Like, the relationship of Tags to a Bazaar, and how tag and menu management can be more humanistic and less an expression of the datastore.

βœ¨πŸŒΈπŸžπŸ›οΈπŸ₯‘ Coming up

There's more work to do. Here's a sketch of what's obviously missing and what questions still need answering.

πŸ€—πŸ‘‰ Tasks ready to go

πŸ’­πŸ€”πŸ€¨πŸ§πŸ§  Tasks that need more thought/design

  • ❓Better interfaces for managing tags and menus, and possible better integration with Product admin
    • Clarify the distinct interfaces for managing menus and tags
      • Eg: right now you mark tags as a menu tag after creation.
      • But there should probably one-step user action for creating a menu tag.
      • It's not clear how to add a menu. Can you guess from this page?
        image
    • Calls to action are hidden
      • Eg: Right now existing tags are just hyperlinked to an edit screen, so it's not easily discoverable what actions you can take on a tag from the main Product Tags page
    • There's no clear workflow from adding tags to adding them to products. As hinted in this section heading, it's worth exploring better integration of product and tag management in a single interface.
    • Enriched tag data
      1. Possible: count of products assigned with tag (Done: Marketplace Tags enhancementsΒ #2431)
      2. At a glance the user should gain a better understanding of their marketplace menus and products
  • ❓ The domain language is a mess at the code and interface level. We arrived at "menu group," which is better than "product tags." But "menu group" is redundant and tautological.

References to feedback from @anaulin:

@rosschapman rosschapman changed the title Marketplace Menus: Next Steps Marketplace Menus: πŸͺ©πŸ₯‚πŸΎβœ¨ & next steps May 28, 2024
@rosschapman rosschapman changed the title Marketplace Menus: πŸͺ©πŸ₯‚πŸΎβœ¨ & next steps Marketplace Menus: πŸͺ©πŸ₯‚πŸΎβœ¨ and next steps May 28, 2024
@rosschapman rosschapman self-assigned this May 31, 2024
@anaulin anaulin added the 🌱 Ready for Dev Stuff we are able to move forward on label Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🌱 Ready for Dev Stuff we are able to move forward on
Projects
None yet
Development

No branches or pull requests

2 participants