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

3-column preview card component solution

Víctor Mato•50
@MatoRV
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, it's my first challenge in frontend mentor, if someone see something that can be changed in the code, please tell me :).

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted almost 4 years ago

    👋Hi Víctor Mato!

    👍 Good job on completing your first challenge!

    I have some feedback to improve this solution:

    • You need to make the h2 all uppercase by using CSS text-transform property.
    • The body should have grayish background too.
    • You should wrap all your content except the attribution one inside a main tag.
    • For the attribution, I recommend to use footer instead of a div.
    • I recommend to use woff2 or woff (Web Open Font Format) instead of the .ttf (TrueType). It's recommended because, the woff has smaller size which mean it can improve the loading speed of your page. I recommend to convert all your *.ttf to *.woff (to support Internet Explorer 9 and above) and *.woff2 (for all modern browsers) using this Free Font Converter.
    • I recommend to always make all elements have box-sizing: border-box; as your common reset. It will prevent all elements to add initial width when you add padding to them.
    *, *::after, *::before {
      box-sizing: border-box;
    }
    
    • Use rem or sometimes em for everything that you usually uses px. Using px will prevent the user to control the size of your page.
    • Try to use CSS Custom Property, to prevent you from keep repeating the same thing. It's also make it easier to organize things.

    That's it! Hopefully this is 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

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