Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 11 months ago

Responsive Product Card

Thibault•110
@Thibs13
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Carlos Al•200
    @crsaele
    Posted 11 months ago

    Hey there, fellow developer!

    When it comes to building websites, it's easy to get caught up in the excitement of creating something new and just use a bunch of <div> and <section> elements to get the job done. But, trust me, taking the extra step to write semantic HTML is totally worth it!

    So, what's the big deal about semantic HTML? Well, let me break it down for you:

    Search Engine Optimization (SEO)

    Search engines like Google love semantic HTML because it helps them understand the structure and content of your website. By using specific elements like <header>, <nav>, <main>, and <footer>, you're giving search engines a clear picture of your website's layout and content. This can improve your website's visibility and ranking in search results!

    Accessibility

    Semantic HTML is a game-changer for accessibility. Screen readers and other assistive technologies can better interpret your website's content when you use specific elements like <button>, <label>, and <table>. This means that users with disabilities can more easily navigate and understand your website.

    Code Readability and Maintenance

    Let's face it, code can get messy quickly! Semantic HTML helps keep your code organized and easy to read. When you use specific elements, you can quickly identify the purpose of each section of code. This makes it easier to maintain and update your website over time.

    Future-Proofing

    As web development continues to evolve, new technologies and features are being added all the time. By using semantic HTML, you're future-proofing your website for upcoming advancements. For example, when new accessibility features are introduced, your website will be better equipped to take advantage of them.

    In conclusion, writing semantic HTML is an important part of building a website that's not only functional but also accessible, search engine friendly, and easy to maintain. So, take the extra time to learn and use semantic HTML elements – your users (and search engines) will thank you!

    Happy coding!

    @crsaele

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
Frontend Mentor logo

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