Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 4 years ago

3-column card component

Natnael Fanta Teffera•110
@nashee
A solution to the 3-column preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello All this is my first post on html css project would you please watch the codes and send me feedback? thanks

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted about 4 years ago

    👋Hi Natnael Fanta Teffera! My name is Vanza!

    I have some feedback on this solution:

    • Don't use id for styling purposes, in this case it will increase the specificity with no reason. I recommend to use classes.
    • Try to write a your html in a consistent way, since right now is the ending div tag is not align correctly.
    • Also try to write a better scss, since right now, the indentation is just useless:
    #s-left  a:hover {
        text-align: center;
        width: 146px;
        height: 48px;
        border-radius: 20px;
       
        
            display: inline-block;
            padding: 10px;
            color:  white;
            border: 3px solid white;
            border-radius: 20px;
            background-color: #E28625;
            
    }
    
    • On :hover state you don't need to copy paste the existing style on the a, just add the style for the :hover state.
    • Try to use rem unit, because it will allow the user to control the size of your page based on their browser setting.
    • Try to add padding-right and padding-left on your body when the card is just one column to prevent the card touching the right and the left of the screen.
    • As you can see from the design comparison, the body background color should be grayish color.

    That's it! Hopefully this is helpful!

    Happy Coding!

  • Natnael Fanta Teffera•110
    @nashee
    Posted about 4 years ago

    Thank you for the feed back, i have updated them now, but this comment is not clear "Try to add padding-right and padding-left on your body when the card is just one column to prevent the card touching the right and the left of the screen."

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

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

Oops! 😬

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

Log in with GitHub