-
Notifications
You must be signed in to change notification settings - Fork 2
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
Replace Icomoon & font-awesome with Google Material Fonts #2093
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2093 +/- ##
==========================================
- Coverage 88.00% 83.41% -4.59%
==========================================
Files 328 171 -157
Lines 14767 9833 -4934
Branches 1031 1031
==========================================
- Hits 12995 8202 -4793
+ Misses 1533 1392 -141
Partials 239 239 Continue to review full report at Codecov.
|
cea8645
to
c1e467b
Compare
4e4729a
to
115e4d4
Compare
@briangrossman & @abdulkdawson , We might need you to review this PR where we are basically replacing all the Font-Awesome and Icomoon Icons with Google Material Fonts. I've mentioned the reason for doing it in the PR description's Background Context part. Please have a look and let me know if you approve of these changes. |
@arslanashraf7 Thank you for the detailed list of changes. All of the changes you show above look good to me. Looks like we're switching from filled-in arrows and not-filled-in close buttons to not-filled-in arrows and filled-in close buttons. :) That's fine. And the replacement This is all good from a look and feel perspective. |
@briangrossman Thanks for reviewing the designs, Also your perceptions are right on moving towards basic outline icons. Now, I'll just wait on @gsidebo's review to take this change into master. |
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 looks great! Just the one comment
static/js/components/TopAppBar.js
Outdated
@@ -22,7 +22,7 @@ const shouldShowLoginSignup = location => | |||
) | |||
|
|||
const TopAppBar = ({ currentUser, location }: Props) => ( | |||
<header className="header-holder"> | |||
<header className="header-holder" style={{ height: 98 }}> |
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.
The purpose of setting a height on the header is to have an element of the correct height occupying the space before the header-related Javascript is loaded. Setting the height here doesn't help with that. You need to add this height to an element in the HTML template
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.
You're right, I've updated it, I've moved this to HTML templates where TopAppBar
was used and where it was possible to set fixed height without effecting responsiveness. It definitely saved us some layout shifts now.
a206e59
to
52f8815
Compare
cms/templates/catalog_page.html
Outdated
@@ -5,7 +5,7 @@ | |||
{% block title %}Catalog | {{ site_name }}{% endblock %} | |||
|
|||
{% block headercontent %} | |||
<div id="header"></div> | |||
<div id="header" style="height: 98px"></div> |
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.
I'm pretty sure we can just add this to the #header
selector in static/scss/detail/header.scss
instead of inlining it in all of these files
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.
Looks like a great suggestion, I'll change/test it in CSS and will update the PR shortly.
52f8815
to
b588f3b
Compare
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.
Looks great! 👍
@gsidebo Thanks for the quick review. |
b588f3b
to
94eadc3
Compare
94eadc3
to
c97afab
Compare
Pre-Flight checklist
Screenshots and design review for any changes that affect layout or styling
Testing
What are the relevant tickets?
#2065
What's this PR do?
Replaces the usage of Icomoon & font-awesome with Google Material Icons.
How should this be manually tested?
Need to verify the icons and their usage is intact.
Need to verify that there is not a lot of difference between the look & feel of the Icons used through Google Material Font
Any background context you want to provide?
In past we were using icons from 3 different sources Google Material, Icomoon & Font-Awesome. Now, While we are in the process of improving the performance of the website so we decided to use the icons just from Google Material Fonts which will provide use some performance improvement since we'll have to load just Google Font reducing the page load time taken by Icomoon & Font-Awesome.
Screenshots (if appropriate)
Old
New
Old
New
Old
New
Old
New
Old
New
Old
New
Mobile Screenshots
Old
New
Old
New
Old
New
Old
New
Old
New
Old
New