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

Next JS, React and Tailwind CSS

next, react, tailwind-css
filecc•470
@filecc
A solution to the Audiophile e-commerce website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey, hi y'all! 😄🥳

I had so much fun with NextJS and this really huge project. I used a new feature for me, the useContext hook from React.

Feel free to submit anything about new features or adjustments.

Things missing: validate in input at checkout and localstorage for persisting state.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mukwende•1,370
    @mukwende2000
    Posted about 2 years ago

    Hello, you did well, here are a few things i noticed, first when you remove all from the cart, it takes you to the homepage, not sure why you did that but don't thing that is an appropriate behaviours, secondly, the number to display besides the is the number of items in the cart, as in if you have a headphone and a speaker, you have two in the, even if the the amount of the headphone is more than. So if you have one mark ii headphone with an amount of 3, that is still one item in the cart not 3. The other thing is on the modal that appears when you continue and pay. The but that says "and 1 other item" should be clickable and reveal the rest of the items. Those are a few notes i made. Hope you find helpful and improve on.

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

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