Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Four card feature with flexbox and grid layout (HTML & CSS only)

Duy Anh Le•120
@leanhduy
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?

Receive feedback & suggestion from fellow developers for previous challenges and be able to apply those suggestions to this challenges.

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

Applying grid system for both the cards container and the cards themselves seemed to work on firefox, but the elements alignment is messed up in other browsers (chrome & edge). I fixed them by changing the display of the cards from grid system to flexbox.

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

If you can point out anything that violates the best practices of HTML and CSS in my code, I would be very appreciated and gladly learn from it.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kane•210
    @Kane2881
    Posted about 1 year ago

    Great job on finishing the project. I suggest you to add max-width property on the container so it won't stretch to the whole screen. If you want to learn more about the property, I advice you to watch Kevin Powell on youtube. He makes amazing videos about CSS. I like that you used width with percentage so the site will be responsive. Welcome to the fun world of CSS!

  • Metin Ahmet Erkeleş•150
    @metinahmeterkeles
    Posted about 1 year ago

    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

Oops! 😬

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

Log in with GitHub