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

Bootstrap

Yana Antonna•20
@yanaantonna
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


This is my first project on Frontend Mentor. Could you please provide me some feedback on the work I have done. Tkank you.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted about 4 years ago

    Hey, great work on your first challenge here in FEM. The layout in desktop is fine, though it is somehow pushed onto the top, the mobile state is good.

    Some suggestions would be that:

    1. In our markup, html, we usually does not use multiple h1. We tend to only use 1 h1 per page. On your case, you used multiple h1, you could just use other heading tags like h2 or h3, and just use h1 like a screen-reader only heading.

    2. Adding an alt text to the images. The images are the 3 cars right, if the image is meaningful, add meaningful alt, if not, then just use alt="" leaving it blank.

    Well those only, good job on this and it is really nice^

  • Mohamed•325
    @MohamedBehhar
    Posted about 4 years ago

    hey Yana, for your first challenge I think that you did a good job, otherwise, I see that you forget to give a border-radius for the card's parent, and also the background color didn't match the one on the design. For the mobile version, I think it's better to reduce the margin between elements ( h1, p , and img) to make the design more beautiful. At the end, I'll be happy if you took a look at one of my projects and give me some advice to make it even better.

  • Aayush Sood•1,175
    @soodaayush
    Posted about 4 years ago

    Maybe fix the accessibility and HTML issues. Your font on the buttons does not look right compared to the design photo.

    That's all I have to say.

    Happy Coding!

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