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

Simple 3 Column card Component using BEM CSS Format

accessibility, bem
Roland Jethro Suyom•375
@Jeth0214
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


Kindly check if my solution on how I solved the changes of border-radius from small device to medium devices was correct. Thanks

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • nikos andriopoulos•0
    @nikosAndr13
    Posted over 3 years ago

    Some things I would like to point out:

    1. A good practice for your HTML is to make everything classes or id just so you can focus and increase the specificity
    2. Now you had only a few images so it wasn't a problem, but when you put let's say 25 imgs in a folder you need to make a half/full step: The syntax: <img src="./images/icons/one-image.png">
    3. For the mobile responsiveness I would recommend finding the most common screen sizes and stick to that: for PC 1200px, iPad 768px iPhone 320px etc I hope I helped! Keep grinding!
  • Rio Cantre•9,650
    @RioCantre
    Posted over 3 years ago

    Hello! Great job on this one! Your solution is pretty much the same to the original design. The border-radius looks fine during the transition to smaller devices. Nothing much to say but I could suggest the following for you:

    • Adjust the height on the .container to make it appear longer.
    • Add a padding or margin around the paragraph inside the .attribution in order to give it enough space on smaller screen view.

    These are just very minor enhancement. Overall the project you made is on point. Keep it up!

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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