-
-
Notifications
You must be signed in to change notification settings - Fork 316
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
General styling updates #473
Comments
We plan to do this after the design for the 11. User Management milestone, so marking as blocked until then. |
@kgodey, I've added the list of placeholder issues that we will need to address to complete the app's styling. Please let me know if it makes sense. |
@ghislaineguerin I assume each of these is for redesigning that particular element. It looks good to me. I assume we'll also be making further changes once we add new features. Things that I don't see here (but may be covered in other items that I'm not noticing):
Do you want to turn this into a meta-issue and create sub-issues for each of the issues so you can tackle them one at a time? |
I'm going to close this issue since we're covering this the various "demo readiness" issues like #1604. |
Problem
Currently, we've been focusing Mathesar design work on functionality and user interactions. The visual style is pretty basic and should be improved.
Proposed solution
We should update the design that we have for Mathesar so far with improved visual styles. There aren't a lot of hard requirements, and this issue involves taking some time to focus on how Mathesar looks.
The solution requires the following aspects of the UI to be defined:
Additional context
Components to style
The text was updated successfully, but these errors were encountered: