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

With mobile 1st triple div and using display: table-cell for desktop

Kimue•200
@dratinixgithub
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 time its the 1st using a lot of padding and margins to get accord to design. There's any other 'better' way ?. If there's i'm open to learn anything new.

-PS: i take 02:17:44 to accomplish this work with 2 breaks from the set up of project, approach with design using Excalidraw, doing the task, creating and managing github with pages and fixes.

Its a good time? bad? average?

Thanks to anyone who responds

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted over 3 years ago

    Hello, Kimue! 👋

    I would recommend focusing on the quality of your code instead of how fast I could finish this challenge. Speed will come in nature but you need to put some effort to make the code has good quality.

    I have a recommendation on making the cards perfectly centered on the page. So, my recommendation is to make the body element as the flex container and add min-height: 100vh to it so that it allows to grow if needed. Also, add some padding to prevent the card from touching the browser edges or simply having full width and height on small screen sizes.

    I highly recommend not setting any styling on the html element because I would like to think of the html element like a table and the body element as a piece of paper so I don't want to change the way the table of the paper, instead it's recommended to adjust the element inside the body element instead. So, the point is I recommend removing the max-width and overflow properties on the html element to prevent any issues.

    I suggest making the "Learn More" buttons as link elements instead of button elements. As a user, I would expect after I click one of those buttons, I would get navigated to another page. That's what I would expect. Now, what do you think is going to happen after the user clicks the "Learn More" button?

    That's it! Happy coding! 😁

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

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