Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 8 months ago

Four card feature section [HTML & SASS]

sass/scss
Oscar Rodolfo Chávez•170
@OscarRodolfoUMG
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

To make it look as similar as I could to the design, I'm sure there are other ways and at one point I thought it would end up ugly, but it turned out pretty :D

What challenges did you encounter, and how did you overcome them?

The first was that I read that sass was used for CSS and the truth is that it is a very interesting support, I'm sure it can be used better, then the cards, I tried several ways but in the end it looked good with Grid, it also needed quite a bit of responsiveness, I have to review how to review it better at "local"

What specific areas of your project would you like help with?

Mmm, in the responsive sizes, I would like everything to maintain a scale and decrease or increase it, I wonder if it is possible, and if it is, it may not be as simple as I imagine XD

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Rahexx•940
    @Rahexx
    Posted 8 months ago

    Good job on this challenge! I agree that the result looks nice and is close to the original design. Although it’s a slightly smaller version, with more practice, I'm confident your skills will improve, and your applications will get even closer to the design specifications.

    Here are a few tips that might be useful:

    1. Consider using the BEM methodology for naming classes. Names like "L1" or "L2" don’t convey much meaning, so using BEM can make your classes more descriptive and maintainable. (BEM 101)[https://css-tricks.com/bem-101/]
    2. Limit the use of h1 tags to one per page. An h1 represents the main title of the page, so avoid using multiple h1 tags. Instead, use smaller headings like h2 or h3 where needed.
    3. Remember to use descriptive alt attributes for accessibility. For instance, "Supervisor_Icon" doesn’t provide much information to visually impaired users. Instead, a description like "magnifying glass with an eye inside" would be more helpful.
    4. Consider using semantic HTML tags such as section instead of a div for a card. This can improve the semantic structure of your page.
    5. Great job using @mixins! To take this further, try reading about responsive design breakpoints. By setting multiple breakpoints and adapting styles progressively, you’ll achieve a layout that’s even closer to the design on all screen sizes. Overall, great job!
    Marked as helpful

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
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub