-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
PDP UI Fixes #1647
Comments
Here's some design work that I reviewed with @aaronjudd yesterday. There are a few elements I'm still working on but some of it can be implemented now as an iteration.
Still refining:
|
Moving of the toolbar and some design iteration: |
@aaronjudd is there an ETA on these new visuals? Will it be longer than 3 weeks? Thanks! |
@lcampanis we've been working on and releasing portions, but now that the UIX @rymorgan design is ready we need to break these out into smaller components so that we can track... |
Thanks @aaronjudd. If I may comment on one thing, is the experience around the Publish flow, which is still a bit confusing.
That's all food for thought, hope you find it useful. |
We've had this same discussion a dozen times, and you've nailed some of the issues we're thinking about. I'm imaging the eventual flow, is that a product is published by you to your shop (the current paradigm), and the publish UX will include additional options (probably as a publish button dropdown option) for other publishing workflows, such as publish to marketplace (which would be a step to will add/remove from a catalog collection). This does raise the question, why couldn't the same button state just have a "Hide/Unpublish" as well.. We could probably just merge that functionality, but I like the idea of keeping a visibility property, as this can then be relied upon for merchandising (ie, it could be the publication changing transforming the visibility). The revisions structure was also meant to track visibility of individual values, and @mikemurray started on that before the UX got even more difficult. |
Tickets to complete epic. |
Closing as we look at the PDP again and rethink some of these flows. |
Re-opening as there are uncompleted tasks in this issue (or a lot more direction on how the follow up is going to take place..) |
@rymorgan might be worth creating a new issue with the remaining tasks. I'll let you close this one if you decide to do that. |
|
The text was updated successfully, but these errors were encountered: