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

3 Column Preview Card Component

bem
Jason Greenwald•200
@jaycgreenwald
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


Did I implement my BEM modifiers correctly (based on BEM standards)? Did I use flex-basis correctly and was there a different/better way to solve the problem of making all three sections a uniform width? Regarding best practices, please confirm that using a link instead of a button was the correct choice for this situation. Other thoughts?

As always, thank you for the feedback and support!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alan Ibarra•440
    @Ibarra11
    Posted about 3 years ago

    Overall, I think the app was good. One thing that you might want to use in the future with flex-box is giving the flex children a flex:1 instead of doing flex-basis: 33.3%. When you use flex: 1 what flex-box does is divides up the space and distributes according the ratio of the children. For example, in the application you have a card with of 920px, so if you apply flex:1 to each child and you have 3 children then flex-box divides up 920/3 and gives each child that width. When you start having a-lot of children you don't have to think of percents. Also, the link was a good choice because inferring from the challenge it seems that those buttons navigate to a different page. You want to use links when navigating to different pages.

    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