Skip to content
Submitted about 4 years ago

Four Card Section

William Anthony•240
@wpittman06
A solution to the Four card feature section challenge
Preview (opens in new tab)Code (opens in new tab)

Solution retrospective

I followed along with a random tutorial that brought me to this challenge out of happenstance. This is my 3rd(?) challenge in which I followed along with another dev and I learned a lot in regards to breaking down a project. My questions would be in regard in how he set up his code? He nested his CSS (which i didn't know you could do) would this be the recommended way if your just using vanilla HTML/CSS? is it just preference? Is it situational? My other question is SASS vs CSS this is my second time using SASS and I've enjoyed it. I'm wondering in terms of usability and learning curve, should I learn SASS in conjunction with CSS? Or should i learn Vanilla CSS properly and THEN utilize SASS? what are your thoughts? Do you prefer one over the other? or is it project based? I'm Also having issues with getting my repository to Vercel, if anyone has any suggestions please help a noob out, i assure the code works i've opened it locally but I'm breaking something when i link it to Vercel.

Code

Please log in to post a comment

Log in

Community feedback

  • Grace•32,130
    @grace-snow

    I learnt scss at the same time it's very simple and no more complex to learn as it is basically css anyway. I would recommend against nesting though (that is a scss feature) except for things like media-queries, pseudo elements (like :before) and pseudo states (like :hover). A lot of people run into horrible specificity wars in their css because of nesting, so my advice is to avoid it, especially when first learning.

    It's very hard to advise on how to fix your deployment without much more information and screenshots of what you're doing. Maybe ask in the Slack workspace (help channel as you can include screenshots and links there)

  • P
    Patrick•14,265
    @palgramming

    Sass allows one to write CSS in ways that many find easier to maintain and faster to write but for Sass to be useful it has to be converted to native CSS and that is why Sass it a Pre-Processor it takes its syntax that is basically an extension of CSS and then converts the Sass code to usable CSS that the browsers can understand

    babel does a similar thing for JavaScript it takes code that is new or extended that is not support by the browsers yet and then converts it to native js code that the browsers can understand. Maybe by looking and seeing how Babel works will help you to understand Sass https://babeljs.io/

    The more you understand about regular CSS the better you will be long term Same goes with JavaScript the more you understand plain JS the more you will be able to understand other JS frame works and libraries that add their own style to the js

  • Rizwan Mustafa•155
    @rizwanmustafa

    Seems like the website is down!

Join 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