-
Notifications
You must be signed in to change notification settings - Fork 167
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
Adjust spacing and size of logo section and deprecate the dense variant #5252
Adjust spacing and size of logo section and deprecate the dense variant #5252
Conversation
@lyubomir-popov So there isn't actually a 6.5rem value in our Sass variables; I used |
I would hardcode 6.5rewm. This is not a value we would be reusing anywhere outside, so no need for a variable. |
c1e3b16
to
719a789
Compare
@lyubomir-popov Done, but it's worth noting that using a value outside the small/medium/large range impacts the use of spacing around the component as well. Let me know if you're okay with this. |
@lyubomir-popov Using a new arbitrary value of 6.5rem disturbs a bit the spacing of logo section. We already have 3 different sizes defined for regular variant on 3 breakpoints, with medium being 6rem. So why introduce another that is just 0.6rem bigger? Also, we have this "offset" built in that pulls the logos closed together vertically, which is always by 1/8th of the size. Like 8rem desktop: 1rem offset, 6rem medium 0.75rem offset. The value of 6.5rem does not work well with this math. If we use 6.5/8 we get into small fractions that will throw us off the baseline grid. |
|
Current implementation (not looking at dense variant):
@lyubomir-popov what exactly do you suggest changing to 6.5rem value? logo size on desktop? what about others? |
6.5rem/1rem on medium and desktop, small remains as is |
f1a11d3
to
eef3714
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.
Small suggestion, but lookin good!
Done
Fixes #5157
QA
Check if PR is ready for release
If this PR contains Vanilla SCSS code changes, it should contain the following changes to make sure it's ready for the release:
Feature 🎁
,Breaking Change 💣
,Bug 🐛
,Documentation 📝
,Maintenance 🔨
.package.json
should be updated relative to the most recent release, following semver convention: