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

Basic four card feature section using simple HTML and CSS.

BozJR•260
@BozJR
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?

Im most proud that i completed it ! this was a little struggle though NGL !

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

I think I've got the HTML locked in now its just remembering the CSS features to help move things around and then figure out why things cant move around is what I find difficult.

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

More help is needed for the the CSS flexbox cause just when I think I have it I DONT! I tried so many ways to get this right but the only way I could figure out was to swap 2 x elements around in my HTML which I know should not be the case but every other method i tried resulted in the same wrong action so this was my only choice! see my code compared to OG code to know what I mean.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dylan•290
    @dquinn089
    Posted 12 months ago

    Your code looks fantastic, and you've done a great job with the layout and styling! Here are a couple of tips for potential improvements:

    Accessibility Improvement: Consider adding descriptive alt attributes to your <img> tags to improve accessibility for screen reader users. This simple change enhances the user experience for a broader audience.

    Consistent Color Variables: Great job using CSS variables for colors! For consistency and readability, use lowercase for all custom property names (e.g., --very-dark-blue instead of --Very-Dark-Blue). This maintains a consistent coding style.

    :root {
        --red: hsl(0, 78%, 62%);
        --cyan: hsl(180, 62%, 55%);
        --orange: hsl(34, 97%, 64%);
        --blue: hsl(212, 86%, 64%);
        --very-dark-blue: hsl(234, 12%, 34%);
        --grayish-blue: hsl(229, 6%, 66%);
        --very-light-gray: hsl(0, 0%, 98%);
      
        --font-family1:  "Poppins", sans-serif;
      
        --font-weight-light: 200;
        --font-weight-regular: 400;
        --font-weight-semibold: 600;
    }
    

    These are very minor changes but can help enhance your code’s accessibility and maintainability. Happy coding!

    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