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

HTML, CSS

Maciekexe•60
@maciekexe
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Improve something?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Tiago José•300
    @tiago-jv0
    Posted about 3 years ago

    There are a few things i would recommend you to learn, for exaple :

    1. BEM methodology - is used to improve your css selectors and make your html structure more descriptive

    2. Usage of new layout techniques like Grid or Flexbox as mentioned above

    3. Css variables - so you can put all your repeatable css values inside a central place

    Marked as helpful
  • Account deletedPosted about 3 years ago

    Hello 😊

    Your current solution is a good start, however there are a couple things that could be improved:

    1. I would recommend always making it obvious when something can be interacted with - In this case, the button. Changing the cursor to a pointer and adding a hover effect would be a great addition.

    2. It looks like you used a table for the layout - I would recommend looking into Flexbox and CSS Grid for responsive designs - Tables should be used for data that is presented as a table, not as a layout tool. Kevin Powell has amazing courses for both of these (Flexbox Simplified, and Responsive Design Bootcamp specifically - The Bootcamp one has a section for Grid).

    3. Your alt tag on the image should be a little bit more descriptive, generally speaking - These are meant to give an idea of what the image is, in this case it doesn't really explain what the image is.

    4. You are missing the <main> tag after <body> - This should always be included for accessibility.

    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

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub