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

3-column-preview

Taishi Arai•20
@tailorthecreator
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


Hi guys, this is the second solution to the project that I have participated at Front End Mentor in. I gotta say, I am falling in love with the whole process of learning.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dimitar Pavlov•310
    @DimiPavlov
    Posted about 3 years ago

    Hello Taishi, congratulations on completing the challenge!!!

    I have noticed that you haven't implemented the active state. You can add a hover effect on each of the buttons(including cursor, border, and color). For more information please refer to the active-states.jpg file in the design folder.

    Hope I was able to help you.

    Happy coding!!!

    Marked as helpful
  • Lucas 👾•104,160
    @correlucas
    Posted about 3 years ago

    👾 Hello Taishi, congratulations for your solution!

    I've two tips for you to improve your solution:

    1.You've used a wrong property twice in your code, just delete it from the .container and from each card class (sedan, suv, luxury) to clean the code, delete this ---> display: relative;

    2.Althought you set a correct breakpoint with media query, the card itself isn't responsive due the fixed width you've set to the container, this means that the card didn't contract properly in smaller screens, replace width with max-width to fix this behavior.

    3.You don't need use id's to manage classes, just use a regular .class to manage the css elements and let the id for specific stuff like forms and complex things.

    The rest is all fine, congrats! Hope it helps you and happy coding!

    Marked as helpful
  • Account deletedPosted about 3 years ago

    Hey Taishi, congratulations on completing the challenge! You did a good job 😉

    Let me give you some little tips for optimizing your code:

    • the link and title tag go inside the head of document not inside the body, For this if you look at the browser window see you do not see the name 3-column-review you have assigned to the page
    • remove <div id="space"></div>
    • remove margin and height properties from container class
    • use flexbox to the body to center the card. Read here -> flexbox guide
    • after, add min-height: 100vh to body because Flexbox aligns child items to the size of the parent container
    • add transition on the element with hover effect
    • instead of using px use relative units of measurement like rem -> read here

    Hope this help! Happy coding 😁 by Travolgi

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

Oops! 😬

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

Log in with GitHub