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

Responsive Dessert Product App

react, vite, chakra-ui
José Mama•240
@codesByJose
A solution to the Product list with cart 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?

Um... im looking forward to maybe refactoring my lines of code..above all one thing that stood out for me is that this is my most perfect projects because i have had to think in react.. hehe Like logic begins to appeal to me.

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

one of the challenges i encountered was with the styling since i used chakra... it was kinda difficult to know what Box(div) i should apply certain stylings... but somehow i found my way around it by making enuff mistakes to see the errors and correct it. Secondly, after pushing and publishing this project, the images from the data.json would display because of the file structure and file path.. i kinda had understood where the problem was from but i just didnt know how to rectify it... im already learning more about it by now.. but i am glad to have gotten that rectified. i also came across the problem of working on the items individually.. i mean since its being mapped out at once how would you then affect it individually.. that led me to learn the reduce method.. quite an interesting project yeah. Thanks

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

ummm.. overall i think this project is good.. but i am open to corrections. Thanks

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • José Mama•240
    @codesByJose
    Posted 5 months ago

    thanks a bunch... a sis by the way

  • Marzia Jalili•8,230
    @MarziaJalili
    Posted 5 months ago

    Well done bro!

    Some adjestments you can make:

    When the user hovers over the product, it resizes the element.

    I assume it is because of the border added on hover. To solve this set the border initial and set the color of it to transparent.

    Then, on the hove mood only change the color. Take the code below as an example:

    .product {
      border: 2px solid transparent;
    }
    
    .product:hover {
      border-color: red; /* or the code of that color */
    }
    

    The website is looking great though!

    Keep up the excellent work 😎

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