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

Four Card Feature

sass/scss
TheRoboRobin•160
@TheRoboRobin
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 specific areas of your project would you like help with?

I'd like feedback on the organization and cleanliness of my code. Does my responsive design work? Is everything readable and make sense? Could I have structured the grid for the cards better?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Akiz-Ivanov•450
    @Akiz-Ivanov
    Posted 4 months ago

    Hello @TheRoboRobin, great job on the challenge. 💪

    If you want to make your code more organized, consider splitting your SCSS into separate files (e.g. _variables.scss or _layout.scss) and importing them. While this isn't essential for small projects, it can help with better organization.  

    The responsiveness is great! Great idea for the tablet screens layout. On laptop screens (1024-1200px) the cards feel a bit too close to the edges, it's not a big deal, but adding a little bit of padding on the sides would be great.

    There’s a brief moment between 880px and 894px when the first card shrinks, causing the layout to appear slightly unbalanced. This can probably be fixed quickly by adding "align-items: stretch" to this media query:

    &__cards {
    	@media only screen and (max-width: $screen-medium) {
          grid-template-columns: repeat(2, minmax(20rem, 1fr));
          align-items: stretch;
        }
    }
    

    There's also a little accessibility issue here in the header:

    <h2 class="heading-secondary">Reliable, efficient delivery</h2>
    <h1 class="heading-primary">Powered by Technology</h1>
    

    Having <h2> before <h1> can confuse the screen readers. Heading levels should follow a logical hierarchy. A <h1> should always be the top-level heading.

    In this design it looks like both lines are part of the same header, so it would be better practice to put both inside h1 and style them with css.

    <h1>
      Reliable, efficient delivery
      <span>Powered by Technology</span>
    </h1>
    

    To place them on separate lines, you can use either the <br> tag or apply display: flex with flex-direction: column to the <h1>.

    Overall, it's a great solution. 🥳 Wishing you the best with your coding journey!

    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