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

HTML, CSS

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

Solution retrospective


Hi everyone, Working on a newbie project after a while is refreshing to me. If anyone finds some mistake please let me know.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Pradeep Saini•990
    @pradeeps4ini
    Posted almost 3 years ago

    Hi, @DekiDex. How are you, buddy?

    • You don't have to write
           box-sizing: border-box;
       }
    

    and then

    * , *::after, *::before{
       box-sizing: inherit;
    }
    

    When you use *, it means it applies to all the elements of the page. You could have only used *, *::after, *::before {box-sizing: border-box;}.

    • You're using "background-image" and media queries to interchange the desktop and mobile images. You could do that with <picture> element in HTML only. Learn more here....

      Using background-image for the image which convey information to user is bad for accessibility. You can provide an alt text using <img> element, which is useful for screen reader users.

    • One page should contain only one <h1> element. <h1> is used for the main heading of the page. You should change the <h1> in the "price" container, to <p>.

    • When i resize the screen below 280px. The image of the perfume bottle is gone. This is happening because you've used @media (min-width: 280px). You should remove it.

    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