Juice-shop: [🎭] UI harmonization towards facelifted design

Created on 29 Dec 2019 · 19Comments · Source: bkimminich/juice-shop

Some old screens as well as all screens newly added during GSoC 2019 might currently not be in visual harmony with the facelifted/UX-improved designs by @MarcRler. Their components should be checked for compliance and if needed be reworked towards the same Material design and usability goals.

[ ] accounting
[x] address
[x] address-create
[x] address-select
[x] administration
[x] basket
[ ] challenge-solved-notification
[ ] challenge-status-badge
[x] delivery-method
[ ] deluxe-user
[x] error-page
[x] forgot-password
[x] oauth
[x] order-completion
[ ] order-history
[x] order-summary
[x] payment
[x] payment-method
[x] photo-wall
[x] product-details
[x] product-review-edit
[x] purchase-basket
[x] recycle
[x] saved-address
[x] saved-payment-methods
[ ] score-board
[ ] server-started-notification
[ ] token-sale
[x] track-result
[x] user-details
[x] wallet

desiglayout help wanted technical debt user interface

Source

bkimminich

All 19 comments

This issue has been automatically marked as stale because it has not had recent activity. :calendar: It will be _closed automatically_ in one week if no further activity occurs.

stale[bot] on 12 Jan 2020

@bkimminich I'd like to work on this issue. Just wanted to know if I am guessing it right?

all the components u have mentioned are to be refactored (in terms of UI)
the improved designs should be similar to or in concordance with "facelifted/UX-improved designs by @MarcRler"

Where can I get the idea about "facelifted/UX-improved designs" And once I get this, all I have to do is improve each component's UI, right?

ridhishjain on 2 Feb 2020

All components _not listed_ above are considered "facelifted" and can serve as examples.

bkimminich on 2 Feb 2020

In general the goal is a consistent look and feel that is in accordance with https://material.io/design/ guidelines.

bkimminich on 2 Feb 2020

Thanks for the help!
I'll split the work into a number of PRs, one for each component, so that it'll be in segments and easy to cope.

ridhishjain on 2 Feb 2020

👍1

This issue has been automatically marked as stale because it has not had recent activity. :calendar: It will be _closed automatically_ in one week if no further activity occurs.

stale[bot] on 16 Feb 2020

This is part of the upcoming OWASP Projects Summit work items.

bkimminich on 24 Feb 2020

@MarcRler, I just noticed that the screen flow when doing a deluxe-upgrade is a bit weird: It's logging you out, throwing you back to the login screen and not showing any confirmation message that you successfully upgraded. I won't open a separate ticket for it, as the deluxe-user screen is not yet done, but please take a look at this when you get to it. Thanks!

bkimminich on 12 Mar 2020

👍1

This issue has been automatically marked as stale because it has not had recent activity. :calendar: It will be _closed automatically_ in one week if no further activity occurs.

stale[bot] on 26 Mar 2020

@MarcRler I'll not merge the current facelift for the upcoming v10.1.0 which will hopefully be released tomorrow, we'll save it for one of the next releases, ok?

bkimminich on 26 Mar 2020

This issue has been automatically marked as stale because it has not had recent activity. :calendar: It will be _closed automatically_ in one week if no further activity occurs.

stale[bot] on 9 Apr 2020

This issue has been automatically marked as stale because it has not had recent activity. :calendar: It will be _closed automatically_ in one week if no further activity occurs.

stale[bot] on 25 Apr 2020

Let's try the _motivational tweet_ approach to get this one eventually resolved for good... https://twitter.com/owasp_juiceshop/status/1283530731097030658 👼

bkimminich on 16 Jul 2020

@bkimminich could I take the accounting component?
Thanks!