-
Notifications
You must be signed in to change notification settings - Fork 317
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
Admin Dashboard Components (Sidebar) #1316
base: development
Are you sure you want to change the base?
Admin Dashboard Components (Sidebar) #1316
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks to @hazeltonbw for the idea of adding a sidebar. A couple of comments:
- Please try to keep this PR consistent with the new PR Admin components clean (without sidebar) #1324 so those changes are not lost.
- Could the description be updated so it is clear this only desires to add the sidebar and is open for comment on the idea?
This proposes to add a sidebar to the admin settings page. I think it is an interesting idea but wanted to seek input from others:
I appreciate any thoughts and your doing this. (This mirrors a msg posted on our Discord channel.) |
This PR completely changes the layout of the admin settings page and therefore does not need most of the changes in PR #1324. However, changes to the translations and settings are kept consistent with that PR. |
Description
In this PR the main focus was to streamline the admin panel to make it more user friendly.
This PR introduces a new sidebar that organizes each setting into their own category, making it easy for admins to find the settings they need to change.
This PR supersedes #1310 as it contained commits relating to editing users, which is not related to these changes.
Please leave any comments/suggestions. Thank you
Several comments/issues have been addressed that were brought up in PR #1310
Partially Addresses: #890
Type of change
These changes will require an update to this documentation page
Checklist