Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Product Preview Card using HTML and CSS (Kevin Powell's walkthrough)

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

Solution retrospective


Product Preview Card using HTML and CSS (Kevin Powell's walkthrough)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Petrit Nuredini•2,860
    @petritnuredini
    Posted over 1 year ago

    Congratulations on completing your Product Preview Card Component project! 🎉 It's fantastic to see your hard work come to fruition with a beautifully designed and well-coded project. Here are some best practices and suggestions to enhance your work even further:

    • Accessibility Enhancements:

      • Use alt attributes effectively in your images to provide descriptive text for screen readers.
      • Make sure that the button is accessible. For example, if the button contains an icon, ensure that it has appropriate aria-label attributes for screen reader users.
    • CSS Organization:

      • Consider organizing your CSS properties consistently (e.g., positioning, box model, typography, visual). This makes your stylesheet easier to read and maintain.
      • Use comments to separate sections of your CSS for better readability.
    • Responsive Design:

      • Great use of media queries for responsive design! Ensure that the layout looks good and functions well on all device sizes, including tablets and smaller mobile devices.
      • Test your page in different browsers to ensure compatibility and a consistent user experience.
    • Performance Optimization:

      • Optimize your images to reduce file size without losing quality. Tools like TinyPNG can help reduce image file sizes.
    • Semantic HTML:

      • Good job using semantic elements like <main> and <article>. Continue this practice as it improves SEO and accessibility.
    • Font Loading:

      • Ensure that web fonts are loaded efficiently to minimize render-blocking. You can use font-display: swap in your font-face rule to enhance text visibility while fonts are loading.
    • Code Reusability and Maintenance:

      • Consider using CSS variables for frequently used values, such as margins and paddings. This makes it easier to maintain and change the values consistently across your stylesheet.
    • Hover and Focus States:

      • Make sure that all interactive elements like buttons have distinct hover and focus states. This improves usability, especially for keyboard users.

    References for Further Learning:

    • For accessibility: Web Accessibility Initiative (WAI)
    • For CSS organization: CSS Guidelines
    • For responsive design: Responsive Web Design Basics
    • For image optimization: Image Optimization

    Keep up the great work and continue exploring new challenges and technologies. Your journey as a developer is off to a strong start, and I can't wait to see what you create next! 💻🌟

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub