-
Notifications
You must be signed in to change notification settings - Fork 40
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
Design new UI component for highlighting new features #4877
Comments
Here are some preliminary options in different colors and how they might be displayed on the website. Would like front-end feedback on how the placement might work, specifically on datatable filter panels. I believe we are limited in our placement there. I'm leaning towards the versions with full-color shapes with white text and icons. |
@JonellaCulmer I like where you're going with this. A few things to consider with the design:
|
Yes to all of the CSS concerns! Not a fan of the red options because of the alert/error/warning usage of red on the web. Incorrect form field, red. Can't submit order, red. Must agree to whatever, red. Service interruption, red. I kinda like the idea of using only the bell for smaller devices and expanding to show the word on user taps, but then what if that triggers a line break, like if the bell fits nicely on the right side of the text but the text would make the icon too wide and then need to wrap. Never easy. Customizing the 'new!' alerts per user would be super tricky and would require cookies and/or GTM. How many times do we show an alert? For how long? If someone loads a page but immediately has to reload, would the 'new' alert go away? Would new visitors see every notice? Returning user after six months, would they see every new feature for the last half year? Would users who block or clear cookies & storage see everything new every visit or nothing new ever? But if we add something new to a template page (like a committee page), seeing an alert on every committee page for a sprint or two could get super annoying |
@patphongs @rfultz Thanks for your feedback. Based on your comments, I modified the layout a bit and removed the "new" circle indicator. This could now just link to the "what's new" page without explaining that new stuff has appeared. Alternatively, if we still want the indicator, we can just leave it up for a week and take it down, but we'd be constantly changing it every time we have a release. Doesn't seem workable at this point and removing seems the easiest course. For the layout CSS challengs, I rearranged the placement. Do you think this will resolve some of the issues surrounding the inline |
@JonellaCulmer , I am generally in agreement with what's been said above. My vote is for orange, seems like red and green should be reserved for error/success type messages. And for some reason, green makes me think it would be clickable. |
Closing in favor of the followup tasks: |
What we're after:
To help showcase new features, we should design a component that highlights those features.
Completion criteria:
The text was updated successfully, but these errors were encountered: