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

Response Product Shopping card made using pure css and html

Priyavrat Chaudhary•110
@priyavrat8065
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?

In this project i learnt how to perfectly vertically align before pseudo element with respect to element it is applied on. This is why i managed to center the shopping cart icon inside the button and side by Add to cart text. Below is the code snipped of how i achieved that -

.perfume__shopping-btn:any-link {
  display: flex;
  justify-content: center;
  align-items: center;
}
.perfume__shopping-btn::before {
  display: flex;
  align-items: center;
}
What challenges did you encounter, and how did you overcome them?

Making sure the image flex item stays 50% the width of its parent conatiner when flex direction of the parent is row was challenging. I thought i would easily achieve that by setting flex:1 by it did not do the job for me.

Then i had to do this -

.container figure {
  min-width: 50%;
}
What specific areas of your project would you like help with?

If you want to learn how to perfectly vertically align shopping cart as a before pseudo element with respect to the element it is applied on, then please do check my code on github.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bhuvnesh Upadhayay•2,120
    @bhuvi819381
    Posted 6 months ago

    Code Feedback

    Hello Friend 👋,

    Your project is looking great overall! However, here are a few suggestions for improvement:


    Suggestions 💡

    1. Use Semantic Tags 🏷️

    To improve code structure and accessibility, use semantic tags like <main>, <section>, and <footer>. It makes your code cleaner and easier to understand.

    2. Avoid Inline CSS 🚫

    Inline CSS can make your code harder to maintain. Keep all your styles in a separate CSS file for better organization.

    3. Avoid Fixed Heights 📏

    Whenever possible, let the content define the height instead of setting fixed values. This approach ensures a more flexible and responsive design.


    Final Thoughts ✨

    Everything else in your project looks amazing 😎. Keep up the great work! Let me know if you need assistance with anything.

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