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

3 Column Card

Semih Rodoplu•50
@SemihRodoplu
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


It seems alike but I am not convinced . I struggled to make button text color different for each column therefore I assigned id attribute for each element . I know something wrong but I could not figure out . Please feel free to make any comment . Thanks

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Michael Johnson•950
    @mikej321
    Posted over 2 years ago

    To get your buttons to show the effects on hover, you can apply this to your CSS.

    .btn:hover, #first:hover, #second:hover, #third:hover { background-color: transparent; border: 1px solid white; color: white; }

    There are a few things going on here...the button and all of your spans are being applied this CSS at this same time.

    https://developer.mozilla.org/en-US/docs/Web/CSS/:hover

    This is a great article on applying hover styles. Let me know if you need anything more!

    Michael Johnson

  • Melvin Aguilar 🧑🏻‍💻•61,020
    @MelvinAguilar
    Posted over 2 years ago

    Hi @SemihRodoplu 👋, good job completing this challenge! 🎉

    I have some suggestions you might consider to improve your code:

    • Use the <main> tag to wrap all the main content of the page instead of the <div> tag. With this semantic element you can improve the accessibility of your page.
    • Setting element width with percentages or VW will cause your component to behave weirdly on mobile devices and high-resolution desktops. You can set the max-width at 920px and remove width: 55vw;
    • The <h1> element is the main heading on a web page. There should only be one <h1> tag per page. The HTML Section Heading elements (Reference). This case requires that SUVS, SEDANS, and LUXURY be <h2> elements.
    • The Learn More elements should be anchor tags and not buttons because they redirect to another website. Use buttons to perform actions such as displaying a modal, performing calculations. Use anchor tags to redirect users to a part of the page or to an external site.
    • Not all images should have alt text. Car icons are for decoration purposes only, so they can be hidden from screen-readers by adding aria-hidden="true" and leaving its alt attribute empty:
    <img src="./images/icon-sedans.svg" alt aria-hidden="true">
    <img src="./images/icon-suvs.svg" alt aria-hidden="true" >
    <img src="./images/icon-luxury.svg" alt aria-hidden="true" >
    

    Above all, the project is done well👏. I hope those tips will help you! 👍

    Good job, and happy coding! 😁

  • Fhero•110
    @fhero2030
    Posted over 2 years ago

    It looks good to me. If you want any improvement I think having more padding inside the card should make the difference but the mobile responsiveness is not there. This can be solved if you apply layout using a flex or grid.

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

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