-
Notifications
You must be signed in to change notification settings - Fork 9
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
[Feature] Admin department page styling #11853
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.
Some comments related to copy.
}), | ||
}} | ||
add={{ | ||
linkProps: { | ||
href: paths.departmentCreate(), | ||
label: intl.formatMessage({ | ||
defaultMessage: "Create Department", | ||
id: "ZbpbD6", | ||
defaultMessage: "Create new department", |
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.
New is implied when creating something. Can we remove the word new?
columnHelper.accessor("departmentNumber", { | ||
id: "departmentNumber", | ||
filterFn: "weakEquals", | ||
header: intl.formatMessage({ | ||
defaultMessage: "Department #", | ||
id: "QOvS1b", | ||
defaultMessage: "Number", |
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.
Everywhere else in the forms, it is referred to as Department number. Should it not be kept the same for consistency?
defaultMessage: "Search departments", | ||
id: "bUyxJi", | ||
description: "Label for the departments table search input", | ||
defaultMessage: "Search by keyword", |
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.
What is a keyword?
defaultMessage: 'Use the "Create Department" button to get started.', | ||
id: "yat9wx", | ||
defaultMessage: | ||
'Use the "Create new department" button to get started.', |
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.
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.
Nice work as always π
For some reason the nav menu's z-index is overlapping the overlay only on the edit page, when the page is loading π (why isn't it happening on the other pages too π). To fix this, we can create a new issue or just set them to "2" in lines NavigationMenu-L45 and NavigationMenu-L184
const departmentName = getLocalizedName( | ||
departmentData?.department?.name, | ||
intl, | ||
); | ||
|
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.
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.
This is a good catch. I could have this be an empty string or "Loading" or something if you want.
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.
OK, I added the loading string
loading title for view page
As discussed with Josh, I just removed the navbar that was built-in to the hero and x3 of top padding. This should sidestep most of the issues you noticed. |
π€ Resolves #11478
π Introduction
Updates the styling of the admin department pages and adds a new "view department" page.
π΅οΈ Details
I've rolled a few more things into this one.
I reduced the bottom padding on the new hero to x2. I've also removed the built-in navbar and x3 of top padding.
I created a new CardSectioned component. Visually it is based on CardBasic and it is broken up like PreviewList. It's not very flexible right now because we didn't receive any designs for it. Hopefully it can become a standard component that is reused widely someday.
π§ͺ Testing
πΈ Screenshot