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

Streamlining Design with a 3-Column Preview Card Component Solution

accessibility, bem, sass/scss
Momin Riyadh•370
@momin-riyadh
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


Hey everyone, I recently completed a project called Streamlining Design with a 3-Column Preview Card Component Solution which focuses on accurately translating UI concepts into code using HTML5, CSS3, and Javascript. I'm curious to know your thoughts on the project and if you have any feedback for me.

What do you think of the overall design of the 3-column preview card component solution? Is there anything you would change or improve?"

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Developer Matusala A.•170
    @matusalab-dev
    Posted about 2 years ago

    congrats for achieving this far... I've got a couple of suggestions, let's start with the animation when the cards return to their original position the overlapping of the card's transition isn't smooth. you can make the animation using a CSS property z-index. because the z-index property is animatable. the other one is responsiveness, your app is not responsive. you can make it responsive with a CSS grid or simply just use the flex-box flex-direction property from row to column at an appropriate breakpoint.

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