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

Audiophile challenge with React, TypeScript, React router, Zustand...

react, tailwind-css, typescript, zustand
Daniel Michael Villanueva•290
@DanVillanueva30
A solution to the Audiophile e-commerce website 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 really proud of my solution this is a huge challenge! With the figma files it's easier and you have much more information available. I did my best to create a solution as close as possible to the design. Next time I'll try to submit a FullStack solution using Node.js and TypeScript. I hope you like my solution :)

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

Creating a mobile menu was difficult for me especially because I don't have much experience using tailwindcss. My solution is functional but i'm sure I can do better, I just need to practice a little more.

Instead of creating a component or view for each category (headphones, speakers, earphones) and taking advantage of the URL params, I decided to create a single view and, using the useEffect Hook, once the component was ready, I could display the products of that category. I made this decision because I thought it wasn't necessary to repeat the same code for three different views, only changing the function that fetches the products. But again, I'm not sure if this solution is right.

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

Do you have any comments or suggestions? What can I do better next time? Is my solution to route management correct?

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 Daniel Michael Villanueva'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.