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

3 column preview card challenge

othman•120
@othmanbenhamdoune
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


if you have any notice don't hesitate to let me your feedback

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

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

    Hey, awesome work on this one. Layout in desktop looks great, though it is not responsive. Right now before going into mobile breakpoint, the layout has shrunk which is not great, your mobile breakpoint is too late. I suggest starting from mobile-first workflow to avoid this kind of scenarios.

    Ken already gave great feedback on this, just going to add some suggestions as well:

    • Always have a main element to wrap the main content of your page. On this one, the .container should be using the main instead of div.
    • Each car icon is just a decoration. Decorative image must be hidden at all times for screen-reader users by using alt="" and extra aria-hidden="true" attribute on the img tag.
    • Also when using alt attribute, avoid using words that relates to "graphic" such as "icon" and others. An img is already an image/graphic so no need to describe it as one.
    • Avoid using multiple h1 on a page, use only at least 1 per page so change those into other heading tags.
    • A page must have a single h1 on a page. Since there are no text-content that are visible that could be h1, you will make the h1 screen-reader only text. Meaning this will be hidden for sighted users and only be visible for screen-reader users, search about sr-only stylings and see how it is used. The h1 text should describe what is the main content is all about, this h1 would be placed as the first text-content inside the main element. Have a look at Grace's solution on this one inspect that layout and see the usage of the h1 as well the stylings applied to it.
    • Those learn more are better using a tag since on a real site, it would be a link to "learn more" about the car.

    Aside from those, great job again on this one.

    Marked as helpful
  • Ken•935
    @kenreibman
    Posted almost 4 years ago

    Good work! It seems like you had trouble centering your card within your body. For future projects like this there is a quick and easy way to center your container. In your body tag for CSS if you put:

    body {
      display: flex;
      justify-content: center;
      align-items: center;
      min-height: 100vh;
    }
    

    The child content (in your case it would be .container) will automatically be centered in the middle your page.

    I recommend you to start a media query to change into the "mobile version" of the card under 1000px. The contents seems to start spilling out around 380px and you finally change the layout at 375 pixels. I know the challenge just tells you to do 1440px and 375px but I challenge you to make it a habit to make it responsive for all other screen sizes in between!

    Marked as helpful

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