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

HTML, CSS

Ankit Lamsal•30
@AnkitLamsal
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


Please review my code

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted about 4 years ago

    Hi

    This looks really nice. I recommend adjusting the max-width on desktop so you're closer to the design.

    The only other real suggestion for improvement is over importing multiple css files for different breakpoints. That's OK to do, but if you are going with that approach, mobile should be your base styles, and desktop overrides in the additional stylesheet targeted with a min width media query. The reasons are because you are forcing a mobile device with less data, power memory etc to download both the desktop styles and the styles it needs to display correctly. Much better to be the other way around, let the desktop download the extra.

    The other thing with that technique, just as with any media query, you only need to override the specific css properties that need to change. You have some repetition in there atm I think.

    Personally I wouldn't use grid for this challenge as it's only ever going in one direction, but no problem with using it. And I would use pseudo elements rather than place an empty div in html to show a background img. But again, your choice it doesn't really matter ☺

    Well Done again, you've done a good job overall

  • Walter Sono•660
    @waltersono
    Posted about 4 years ago

    Hi AnkitLamsal

    Nice work completing your first challenge.

    Here are some points to improve your next projects:

    • Add a transitions on when the user hover the button

      • This will make a smooth experience on button hover
      • Just add this to your button transition: all 0.2s
    • Target your elements by class not by element

      • This will make your projects easy to maintain because
      • If you had given the a tag a class you could have style it with fewer lines, like so:

    HTML <a href="#" class="button">Learn more</a>

    CSS .button { *styles go here* }

    • Learn BEM Naming convetion
      • Has a future professional, you want to write clean code, easy to understand and easy to maintain, writing your code following a naming convention is a good practice

    That is it my fellow mentor

    Hope this is helpful, and keep on coding!

    See you!

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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