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

Responsive Product Review Using Flexbox

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

Solution retrospective


What are you most proud of, and what would you do differently next time?

Getting it done.

What challenges did you encounter, and how did you overcome them?

Still having some responsive issues with images.

What specific areas of your project would you like help with?

Image responsiveness and a bit of resizing of certain things

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ohazulike Stanley•220
    @Gentlestan
    Posted 7 months ago

    Kudos to you!

    The use of meaningful tags like <main> and <footer> for structuring your content is truly commendable. These semantic elements not only improve readability but also enhance accessibility, making the project more user-friendly and professional.

    I also appreciate your approach to defining reusable color variables (e.g., --Darkcyan, --Cream). This is a great practice that ensures consistency throughout the design and makes the code more maintainable, especially for larger projects.

    The inclusion of a media query is another strong point—it makes the site adaptable and responsive, catering to different screen sizes seamlessly. Additionally, the choice of Google Fonts, Fraunces and Montserrat, aligns well with the design aesthetic and contributes to the overall visual appeal.

    Suggestion for Improvement: For larger screens, you might want to consider increasing the width of the button. Currently, it appears a bit smaller than expected compared to the design. Adjusting the button's dimensions would enhance its prominence and maintain visual balance on wider screens.

    Overall, excellent work! With a few tweaks, this project will stand out even more. Keep up the great effort!

    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
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