Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 4 years ago

Responsive, GRID, SASS

Samyr Oliveira Ribeiro•215
@SamyrOR
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello everybody, i expect you have a nice day.

Here go another challenge, all feedback well be welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Szymon Rojek•4,540
    @SzymonRojek
    Posted over 4 years ago

    Hi Samyr,

    View code button is not referencing to the GitHub files (maybe there is a general problem with it today). There is another way to arrange the blocks differently - column on mobiles, then two rows with two boxes (for tablets) and final design version on desktop, what do you think about it? Also, try to fix the HTML issues report above.

    Greetings :D

  • Basile Raiwet•175
    @BasileRaiwet
    Posted over 4 years ago

    Hi Samyr !

    Great work ! I just see some points you can improve :

    • About semantics : avoid to use many h1 on the same page. h1 and h2 are here for the title and subtitle of the section. So It's better if you use h3 (or other, depend of the situtation) for the boxes titles
    • about the container width : design is based on a 1110px grid and I think it's better to limit the width of the container to this size because if your solution stretch to 80% of the viewport with (like it is actually), the result could be really different on larger screens. (As an example, look how this page container is defined. It's, I think, the most common way to define container width)

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

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

Oops! 😬

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

Log in with GitHub