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

Product-list-with-cart using Vite and tailwindcss

fetch, next, react, tailwind-css, react-router
Godsgift Etuk•40
@Sparklegift
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?

I’m proud of designing a Product-list-with-cart using Tailwind CSS, and I was able to complete the project within a short time compared to my previous work. The outcome was exactly as I envisioned, and I was able to practice data-fetching techniques from a JSON file, which worked smoothly. Additionally, I’m happy with how I applied clear naming conventions for functions and variables, making the code more understandable for other developers.

If I were to do anything differently next time, I would focus on optimizing the code structure earlier in the process, especially when dealing with more complex data manipulation. This could help avoid potential issues down the line and ensure scalability as the project grows.

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

The main challenges I faced were more related to JavaScript than just the design structure. As a junior developer, I encountered a few issues while executing the website's functionality, particularly with handling dynamic data and ensuring smooth interactions between the product list and the cart.

To overcome these challenges, I broke down the functionality into smaller, manageable tasks and focused on understanding the flow of data between components. I also referred to online resources and documentation to fill gaps in my knowledge. By the end, I was able to successfully implement the required functionality, but I realized the importance of improving my JavaScript skills to handle more complex logic in future projects.

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

I would like help with optimizing the JavaScript functionality, particularly around improving the efficiency of the data handling between the product list and the cart. I want to ensure that the code is not only functional but also follows best practices for performance and scalability. Additionally, any guidance on implementing more advanced state management or using external libraries to streamline the process would be greatly appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Godsgift Etuk'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 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.