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

Four Card Feature Section with HTML and CSS

P
Dexter Niles•140
@dexterniles
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?

I'm starting to feel much more comfortable with styling based on viewport width. Overall i think this came out really nice but there are still some little things that I need to work on adjusting.

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

Spacing for mobile continues to be an issue. I can't seem to find the right sizing combination to make it look nice. Maybe its the layout im using?

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

Spacing and adaptive sizes. Most of the stuff in here is hard coded which i know is a no no but I don't know how to do it any other way atp. Any and all help is welcomed!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Mnqobi Thusi•150
    @CodexLoop
    Posted about 2 months ago

    Your Four Card Feature Section project is clean, responsive, and visually well-structured, with clear typography, consistent spacing, and effective use of color-coded borders. It adapts smoothly across screen sizes, showcasing a solid grasp of modern frontend design. To polish it further, consider centering the section on wider screens, adding subtle hover effects for interactivity, including a favicon, and ensuring accessibility best practices like contrast checks and alt text for icons. Overall, it’s a strong, portfolio-worthy UI component—just a few tweaks away from being production-ready.

    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