Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

CSS Grid, React, components Responsive, react-routing

react, react-router, sass/scss, animation
Azizbek Yunusaliev•400
@azick99
A solution to the E-commerce product page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Please, don't hesitate to give some feedbacks so that I could improve the project and work with that

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • S MD suleman•3,510
    @sulemaan7070
    Posted over 2 years ago

    hey Azizbek Yunusaliev😄, you did a great job. here are a few tips to improve...

    1.when the items are added to the cart the users have no idea that items are added successfully... you can place a span positioned absolutely to the cart svg.. which indicates items added successfully to the cart.

    2.When I open the mobile-menu and start scrolling down the close svg is going to top .. you can stop that scrolling behavior by adding this JS code

    this stops the user from scrolling: 
    
    (document.body.style.overflow = "hidden")
    
      This will help in scrolling again(default) :
    
     (document.body.style.overflow = "auto");
    

    3.I also recommend to you increase the height and width of .cart-dropdown-container a little bit more...

    Everything else looks great !! happy coding💯👍🏻✅

    Marked as helpful
  • P
    Jo89 😈•460
    @AhmadYousif89
    Posted over 2 years ago

    Hey Azizbek 👋

    Your solution looks Awesome 👍I just have a couple of notes that I hope it would be good for your project :

    • the animation is a bit too much may be readjusting the duration and the starting point would help (nit-picking I know 😅)

    • the animation on the header navigation tho is totally unnecessary (IMO) and doesn't make a lot of sense either 😐

    • the cart modal need to be a bit wider and taller to accommodate the items in it (I guess that you have added a fixed width and height on it 🤔)

    • the logic for adding the product to the cart doesn't make a lot of sense, instead of adding the same product twice or more you should just increase the quantity of that particular product, so if it doesn't exist initially in the cart you just push it to the cart with qty of 1, but if it's already in the cart you increase the qty by 1 or 2 or whatever the counter is at this point.

    • the lightbox animation looks good, but what I don't like is that the backdrop is being animated with it I think you placing them in the same component, try separating the lightbox/carousel from the backdrop and just animate the lightbox and maybe add a bit of delay so that the backdrop come first then the lightbox after like 200ms

    • I really loved the Authentication form section ❤

    I haven't really looked at the code so I can't give you my 2cents on it tho, but anyway I hope you find my notes helpful for you.

    Keep Coding 👊

    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

Oops! 😬

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

Log in with GitHub