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

3-Column Preview Card Component

Durga Jaiswal•230
@Durga-Jaiswal
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 2nd attempt in the Challenges. Every suggestion on how to improve will be valuable to me.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Laharl•1,000
    @UrbanskiDev
    Posted almost 3 years ago

    Hello Durga Jaiswal

    Congratulation on finishing this challenge while trying to improve it

    1. I would recommend you to fix all the HTML issues available in the rapport section above !

    2. In your HTML file, you did use a "button" to make the button "Learn more". While it is a good option, you can make your own button by defining it as a "a" tag, and then use css to make it like you want

    For example; a very basic way to make it looks like a button :

    a {
      text-decoration:none;
      background-color:black;
      color:white;
      padding:10px;
      border-radius:10px;
    }
    

    It will make looks like a black button, and then, you can easily add a link in the "href" of your "a" html tag to redirect.

    1. You tried to make it responsive, which is a good thing ! However, there's some tips I can give you :
    • When you're in desktop mode, there is a moment where you text start to resize with the design (you can use the browser dev tools to see how responsive your page is) at width 800px, maybe you could add an other media query to make it more natural between 600px and 800px.

    • You could add a min-width, to avoid your content to be resized too much if the size become too small

    .section{
       padding:35px;
       max-width: 250px;
       height: 350px;
       min-height:300px;
    }
    
    • And for the margin, I would avoid to use % as an unit, it is better to use px or rem for that purpose, I add a link where you can have the best practices for units, it is a bit old, but it should help you : https://gist.github.com/basham/2175a16ab7c60ce8e001

    I hope my comment will be helpful to you !

    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