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

three-column

Themoonwillbestaywithme•450
@ZENSE-THAI
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


#Day 15 of frontend training For this piece, it took me 2 days to create. On the first day, I practiced doing it myself using the knowledge I gained from the past 10 days. After encountering a problem that I didn't understand, I went to study on YouTube. and solve problems until getting the finished product

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ahlam•300
    @AhlamAb22
    Posted almost 2 years ago

    Great job on your work! I have a few notes to share. I'm also in the process of learning and addressing past challenges to reach best practices. Here's some feedback I received that might be helpful to you:

    -It's recommended to have only one h1 per page. For this task, consider using h2 headings for 'Sedans,' 'SUVs,' and 'Luxury.'

    -Instead of using buttons, consider using anchors as these will navigate to other pages.

    -Incorporating landmarks such as 'Main' and 'Footer' would improve the page's accessibility and structure.

  • Jewels•150
    @ShalomiAhavah
    Posted almost 2 years ago

    Wow nice Job! Just keep practicing like that and you'll make it far!

  • P
    Øystein Håberg•13,280
    @Islandstone89
    Posted almost 2 years ago

    HTML:

    • Container class should be a <main>.

    • The images are decorative, so alt text should be empty: alt = ""

    CSS:

    • It's best practice to link the fonts in the <head> of the HTML.

    • Font-size should not be in px, but in rem.

    • Max-width on container should also be in rem.

    • You can remove margin: 0 auto - the card is already centered using Flexbox.

    • Set margin-top: auto on the .btn to make the buttons align.

    • Ideally you should do mobile styling as default, and use media queries (in rem) for larger screens.

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