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

Four Card Responsive using 3 grids

justine1607•140
@justine1607
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?

the most I am proud off is how I align the 1st card to be exactly the same as the design, i was not expecting that i can make it like that i thought it would be so hard do it.

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

the one i mentioned above that I think is the challenge I have encountered. I overcome this challenge by motivating my self that i can really make it

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Djamel1133•910
    @Djamel1133
    Posted 9 months ago

    ok ...Keep it up and see you next challenge.

    Marked as helpful
  • P
    Kamran Kiani•2,780
    @kaamiik
    Posted 9 months ago
    • I see your heading like this: A h2 tag that has a strong tag inside of it. I think the whole is a heading.

    • Maybe It's better that your cards heading be a h3. It seems a one level reduce with your top page heading.

    • I suggest you add a proper CSS reset to your style. Andy Bell and Josh Comeau both have a good one.

    • Use rem for your font-size and max-width instead of px.

    • Your grid layout need 4 rows. It's better for your layout because If your content changes, your grid items will mess up. Check this link on discord: https://discord.com/channels/824970620529279006/1214884151728152577/1215761500225011872

    • Instead of height: 100vh; It's better to use min-height: 100vh. This works better.

  • Djamel1133•910
    @Djamel1133
    Posted 9 months ago

    Great job, and what clean code! I really liked it.

    I completed the same challenge on Frontend Mentor, and they asked me to provide feedback to other coders on it. So, I have a few questions if you don't mind:

    1. Why didn't you use variables for font-size and font-weight as you did for colors?
    :root {
      /* Primary colors */
      --Red: hsl(0, 78%, 62%);
      ...
      /* Font weights */
      --font-weight-small: 200;
      ...
      /* Font sizes */
      --font-size-small: 1rem;
      ...
      /* Spacing */
      --spacing-small: 1rem;
      ...
    }
    
    1. Why did you use px instead of rem?
      margin-bottom: 76px; 
      margin-top: 15px; 
      gap: 15px;
      ...
    

    You could also use calc or clamp for more flexibility. Check out this article: Typography in Web Design.

    1. Why did you use a div inside another div in your HTML code? Why not insert HTML elements within a single div like this:
    <div class="card__supervisor">
      <h3>Supervisor</h3>
      <p>Monitors activity to identify project roadblocks</p>
      <img src="images/icon-supervisor.svg" alt="Magnifying glass icon with an eye in the center">
    </div>
    

    Finally, I picked up some tricks from your code to optimize mine. Thank you, and well done again!

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

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