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

Four Card Section Challenge

Ayomide philip•180
@Ayomide-Philip
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?

Being able to think outside of what i was taught.

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

How to make the second and last card in the same container, i overcome it by justing putting them in the same div

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

@media query

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    JOSIANE FERMAO•170
    @josifermaodev
    Posted 10 months ago

    Your code, from what I can see, is a bit disorganized in the HTML section, lacking indentation.

    Indentation is a concept used in programming to organize and structure source code in a clear and readable way. It consists of adding spaces or tabs at the beginning of each line of code, in order to create a visual hierarchy that makes the program easier to understand.

    using your code as an example, instead of doing it like this:

    <div class="card-container">
      <div class="card green">
        <h3>Supervisor</h3>
      <p>  Monitors activity to identify project roadblocks</p>
      <img src="./images/icon-supervisor.svg" alt="Supervisor">
      </div>
    

    the correct one would be:

    <div class="card-container card-green">
        <h3>Supervisor</h3>
        <p>Monitors activity to identify project roadblocks</p>
        <img src="./images/icon-supervisor.svg" alt="Supervisor">
    </div>
    

    ➡️And explaining your doubt: A media query checks the specified condition and applies the styles defined within it only if the condition is true.

    Examples:

    1. Adjust style for screens smaller than 599px:
    @media (max-width: 599px) {
      body {
        background-color: lightblue;
      }
    }
    

    In this example, the body background will change to lightblue on screens with a width of 600px or less.

    1. Adjust style for screens larger than 600px:
    @media (min-width: 600px) {
      body {
        background-color: lightblue;
      }
    }
    

    In this example, the body background will change to lightgreen on screens with a width of 600px or more.

    1. Adjust the style for screens between 600px and 1440px wide:
    @media (min-width: 600px) and (max-width: 1440px) {
      body {
        background-color: lightblue;
      }
    }
    

    In this example, the body background will change to lightblue on screens with width between 600px and 1440px.

    Good job!

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub