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

I used the html and Css but I couldn't find a free Icon.

next
Maher•110
@Maher0551071612
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I couldn't find free icons.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • kxnzx•870
    @kxnzx
    Posted about 3 years ago

    Hello @Maher0551071612,

    Well done finishing your second challenge! I have some suggestions...

    • You need to wrap the title "Gabrielle Essence Eau De Parfum" in a <h1></h1> tag, because this is the most important heading on the page. This helps the search engines understand what the page is about. Besides that it helps (screen)readers understand the hierarchy of the page. Always first start with an H1 and then you can follow it up with an H2 etc. (in case you have subheadings.) You could wrap "perfume" in an <h2></h2> tag. Even though this starts earlier on the page, this does not matter: the screenreaders will understand the hierarchy.

    • You are also missing the <main></main> tag. (Wrap or make your div in(to) a main tag). The main tag acts like a landmark. Screen readers and other assistive technologies read them. By using landmark elements such as <main>, you improve the navigation experience for users of assistive technology such as people with bad eyesight. The footer is also a landmark, and you included that. Well done!

    • Also..Look into CSS Flex-box and CSS-Grid to learn how to center containers on the page.

    Marked as helpful
  • Luis Herrera•795
    @Luis15Herr
    Posted about 3 years ago

    The cart icon is in the ./images folder.

    Marked as helpful
  • Kallakuri Sahitya•100
    @Sahitya2006
    Posted about 3 years ago

    Hey, Your project is nice. You can use free icons from Fontawesome.com https://fontawesome.com/

    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

Oops! 😬

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

Log in with GitHub