You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current settings experience in Akash Console is a bit confusing, with different settings grouped into one screen and some settings accessible through separate paths.
This issue proposes reorganizing the settings into dedicated pages, improving navigation, and creating a unified structure to reduce user confusion and make the interface scalable for future additions.
1. Status Q:
Profile and templates (Accessible when signed in from the "Top nav" - right corner - dropdown)
Settings (Accessible when wallet is connected - through the item "Settings" on the sidebar)
2. Unify Settings Access
As we see above - currently, there are two different "Settings" paths:
From the sidebar (wallet connected)
But, when users switches to CC payments, the "Settings" item disappears from the sidebar
From the top navigation dropdown (when signed-in)
Where we also have three options "Settings", "Templates" and "Favourites" leading to the same "Settings" page.
Solution:
Unify the settings into a single path and consistent structure.
Ensure the "Settings" option is always available, regardless of the payment method.
Integrate "Profile settings" into the "General" page of the unified settings structure.
Proposed UI/UX Changes:
Split the current settings into separate pages, similar to how “Authorizations” has its own page. These pages should be accessible via a vertical or horizontal navigation menu, replacing the current arrangement of switches.
4. Mockups
A couple of mockups to see how a redesigned "Settings" experience would look like (with some new additions - just to see how it behaves if we add more options):
General
- note, the sidebar menu is from the issue https://github.com//issues/553
Ceritificates
General
These suggestions are just a starting point to spark some discussion and keep improvements in the pipeline. If you have any feedback, ideas please share!
The text was updated successfully, but these errors were encountered:
The current settings experience in Akash Console is a bit confusing, with different settings grouped into one screen and some settings accessible through separate paths.
This issue proposes reorganizing the settings into dedicated pages, improving navigation, and creating a unified structure to reduce user confusion and make the interface scalable for future additions.
1. Status Q:
Profile and templates (Accessible when signed in from the "Top nav" - right corner - dropdown)
Settings (Accessible when wallet is connected - through the item "Settings" on the sidebar)
2. Unify Settings Access
As we see above - currently, there are two different "Settings" paths:
From the sidebar (wallet connected)
But, when users switches to CC payments, the "Settings" item disappears from the sidebar
From the top navigation dropdown (when signed-in)
Where we also have three options "Settings", "Templates" and "Favourites" leading to the same "Settings" page.
Solution:
Unify the settings into a single path and consistent structure.
Ensure the "Settings" option is always available, regardless of the payment method.
Integrate "Profile settings" into the "General" page of the unified settings structure.
Proposed UI/UX Changes:
Split the current settings into separate pages, similar to how “Authorizations” has its own page. These pages should be accessible via a vertical or horizontal navigation menu, replacing the current arrangement of switches.
link: https://ui.shadcn.com/examples/forms
link: https://ui.shadcn.com/examples/dashboard
3. Here are the proposed pages:
4. Mockups
A couple of mockups to see how a redesigned "Settings" experience would look like (with some new additions - just to see how it behaves if we add more options):
These suggestions are just a starting point to spark some discussion and keep improvements in the pipeline. If you have any feedback, ideas please share!
The text was updated successfully, but these errors were encountered: