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

Dessert Store with React, React Router, and Headless UI

react-router, react
Julianna Messineo•290
@mathematiCode
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 using React Router for the first time with the help of this video. I really worked to make this accessible and user-friendly, even straying from the design where needed. For example, I used Headless UI for the modal to make sure it had all the accessiblity pieces. And in the design, there wasn't a button to close the modal, only to "Start a New Order" and that seemed like a poor UX to me, so I added a close modal button. But that opened a whole new challenge because it didn't make sense for the user to close the modal and then still be able to edit their order after it has been confirmed. That's why I used React Router to redirect them to a Order Confirmed page when they closed the modal. This seemed easier and like a better UX than disabling every button on the original page.

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

I learned useContext halfway through working on this project and that was somewhat confusing, especially trying to manage state in separate parts of the application without using it at first and then migrating to it later. This is one of my first React projects ever so I spent a lot of time thinking about how to separate it into components. The Add to Cart button that transforms into a toggle was especially tricky, but I ended up creating two sub components within my Add to Cart component. One called and one called .

When I've looked into Tailwind in the past, I hated the idea. But with this project - specifically having very similar but slightly different components in 3 different places, I can see why it would be helpful. I was making new classes just to apply slight changes and keeping 90% the same as the other similar components. I know I can also do this by passing a few styles in through props.

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

The overall organization of the website. The basic concepts of React because I am just starting to make projects with it.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

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