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

Four card feature section master using CSS & HTML

Khalid Khabouz•190
@KhalidKhabouz
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Thank you for stopping by, this is the final result of this challenge, using CSS, HTML, flexbox, media queries.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted over 3 years ago

    Hey, awesome work on this one. The desktop layout looks great, it is responsive though if go to like 770px upwards, not really an issue but just that the cards get differ in their sizes. You could go with something like a 2x2 layout so that it will be equal size. Mobile state looks great as well.

    Here are some suggestions for the site:

    • The header on this one could just be replaced by div and be inside the main tag this layout looks like just a single content or main-content. Typically, a primary header consists of the site-logo, navlinks and some other controls for the site.
    • For the h1, you don't need to use br tag inside it to make the second text wrapped in another row, for this you could just use max-width on it. Adjust the value on it until you get the desired look. Just remember to add margin: 0 auto on it so that it will be centered.
    • For the section tag, you could just remove this since a section tag is not informative enough unless it is labelled using aria-labelledby attribute or when there is already a visible heading tag on a section/part of the layout. So for this, a div could replace the section.
    • Since you are using ul tag, you should have created a 4 li tag and not 3 since visually, there are 4 items right. Use 4 li tag and use grid on the ul so that you could place each item properly like on the design.
    • For the colored top of each card, you could just use the ::before or ::after of each li tag. This way, you won't have to create an extra span tag inside it.
    • For each icon of the card, you could just hide them since they are only acting as decoration. Decorative images are just images that doesn't contribute to the overall content of the site. They should be hidden for screen-reader at all times by using alt="" and aria-hidden="true" to the img tag or only aria-hidden="true" if you are using svg instead of img tag.

    Aside from those, great job again on this one.

    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