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

Product Card Design Challenge

pure-css
Rhuqayah001•40
@Rhuqayah001
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?

I'm most proud of how closely I was able to match the original design using only HTML and CSS. It really helped me improve my layout skills, especially with Flexbox . I also kept my code organized and readable, which made the project feel more manageable as it grew.

Next time, I’d focus more on responsive design from the start, maybe using mobile-first styling. I also want to improve my use of semantic HTML and maybe start using a CSS preprocessor like SCSS to keep things even more organized.

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

One challenge I faced was matching the design without using Figma, since I had to rely mostly on the preview images and my own judgment for spacing, font sizes, and alignment. I took my time comparing the layout visually and adjusting things until they looked as close as possible.

Another challenge was structuring the layout properly with just HTML and CSS. I had to experiment a bit with Flexbox to get elements in the right position, especially when centering content or handling spacing between sections.

While I didn’t make the project mobile responsive this time, I now realize how important that is and I’d like to focus on learning responsive design in my next project.

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

I’d really appreciate help with making the layout responsive across different screen sizes — especially understanding how to use media queries effectively.

I’d also like feedback on my CSS structure and class naming to make sure I'm writing clean and maintainable code. Any tips on improving alignment and spacing without relying on guesswork would be great too!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Rhuqayah001's solution.

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.