Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Quiz App (React + SCSS + Framer.Motion + Express.js)

framer-motion, react, sass/scss, express
Sasha Herman•270
@SashaH62
A solution to the Frontend Quiz app 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?

Hi everyone 👋,

Thanks for having a look at my project. I had a lot of fun with this one. 😁

As I'm currently learning and practicing React, my goal with this specific project was to practice using the 'useReducer' hook in React as opposed to using multiple useState hooks to manage the project. I was quite blown away with how much simpler the useReducer hook actually made creating a project of this type.

What I'm most proud of is seeing my progress with React in general, and how much more comfortable with the library, at least with a project of this scale. I also made the decision to try and create a 'mock api' with the json data provided, for which I used Express.js to serve the data. It wasn't necessary at all, but I decided to challenge myself to see if I could actually get it to work.

Overall, I'm proud that I could try to start working out of my comfort zone and expose myself to unfamiliar territory and try to actually make it work.

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

I didn't really have much of an issue getting the reducer to function. For the most part, it was purely troubleshooting natural errors that would occur during the dev process.

The biggest challenge I encountered was setting up the 'mock-api'. Initially I made use of 'json-server' to serve the data as a mock-api on my local, but realised this would not work the moment I pushed my project to Vercel.

I then attempted to setup an Express.js server in the same project directory (separated into frontend and backend) which again, worked on my local, but the moment I pushed the project to Vercel, the server would not run.

After a lot of backand forth, I eventually resorted to separating the frontend and the backend and hosted the backend on Vercel as it's own project, from which I could then use the Vercel project as an API to retrieve my data.

This was a huge headache, and I didn't really know how to troubleshoot issues I was experiencing but I learned a lot, even if the Express.js implementation was minor. 🫠

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

I'm completely open to any and all feedback. Let me know if anything is broken or if there's something you would have done to simplify a specific process. 😊

Thanks again for having a look at my project. 😁

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 Sasha Herman'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.