Design comparison
Solution retrospective
Again, I'm using light theme on VS code. (⌐■_■)
What challenges did you encounter, and how did you overcome them?Not used to sass. I'm trying to adapt on it.
What specific areas of your project would you like help with?Any opinion helps. A little help on how to use sass effectively will help me a lot! Go easy on me though. Cheers! (ノ◕ヮ◕)ノ*:・゚✧
Community feedback
- @0xabdulkhaliqPosted 7 months ago
Hello there 👋. Congratulations on successfully completing the challenge! 🎉
- I have a suggestion regarding your code that I believe will be of great interest to you.
BODY MEASUREMENTS 📐:
- Use
min-height: 100vh
forbody
instead ofheight: 100vh
. Setting theheight: 100vh
may result in the component being cut off on smaller screens, such as mobile devices in landscape orientation. Since this component is big enough to fill the screen the component will be surely cutt-off which may cause the users a terrible experience, it might need to addressed quickly.
- For example; if we set
height: 100vh
then thebody
will have100vh
height no matter what. Even if the content spans more than100vh
of viewport.
- But if we set
min-height: 100vh
then thebody
will start at100vh
, if the content pushes thebody
beyond100vh
it will continue growing. However if you have content that takes less than100vh
it will still take100vh
in space.
.
I hope you find this helpful 😄 Above all, the solution you submitted is great !
Happy coding!
Marked as helpful1@DaTheDumbGuyPosted 7 months ago@0xabdulkhalid Thanks for the feedback~ I get what you are saying. Fixed height can cause trouble later when the content overflows, and I fixed the height of the body for the main to take its height (height: 100%) to center the content of the main, considering the content of the page is just that.
With your suggestion, actually I didn't think about using min-height that way. I usually use min/max on media queries and max on content I want to limit the width for responsiveness.
I changed the min-height of the main to 100vh, according to your suggestions. Thanks again! Your suggestion is really great. Cheers! ( •̀ .̫ •́ )✧
0 - @R3ygoskiPosted 7 months ago
Hello @DaTheDumbGuy (This sounds so disrespectful x_x), first of all, I'd like to congratulate you on the project. It turned out very similar to the proposed design, almost identical. Congratulations.
About your Sass, it honestly looks good. I didn't see anything so incorrect. You're using @forward, which is good, and @use, which is also good. You're separating it into partial files, so it's correct and well-organized. Congratulations.
Now just a small tip related to Semantic HTML, your
<div class="card_stat">
, could be replaced by a<ul>
, because if you look closely, each item within stat is related.And again, congratulations on your project and another congrats for making your project in light mode. I hope your eyes are okay. If anything I said isn't clear, please comment below, and I'll try to help you in the best way possible.
Marked as helpful1@DaTheDumbGuyPosted 7 months ago@R3ygoski Hey there~ my username is kind of weird, its fine lol. 〜( ̄▽ ̄〜)
I did change the
card_stat
toul
and you are right, thesection
tag looks odd there. I got used to using thesection
and didn't think it through before using it there. Thanks for pointing that out!About the Sass, I'm currently studying not long ago, and it takes a lot of my time organizing things and learning where to put things. With your feedback, I guess I'm doing good. I watched Kevin Powell on YouTube explaining about @forward/use, that's why I'm using them.
Anyway, thanks again! Your feedback ease lots of my worries regarding how I use Sass. By the way, my eyes are good. They are bleeding but it's fine. (⌐■_■)
1 - @DaTheDumbGuyPosted 7 months ago
I read on someone's work having a suggestion of using
mix-blend-mode: multiply
on the image overlay. I never heard about it, but it works perfectly. ¯_(ツ)_/¯0
Please log in to post a comment
Log in with GitHubJoin our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!
Join our Discord