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

Milestone-Frontend Quiz with React and React Route!!!

react, react-router, vite
P
Alexwz89•480
@Alexwz89
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?

After 2 days of hard working, I finally published my first multi-page React project on Netlify, and it's a great way to conclude the third phase of Learning Path. Looking forward to more challenges in subsequent projects, I'll gradually increase my proficiency in React, while gradually introducing Typescript and Tailwind CSS!

What challenges did you encounter, and how did you overcome them?
  • How to design the Route - review the lesson in scrimba, highly recommend Bob Zirol's Advanced React course!
  • The dark and light theme switch - even I have learned some knowledge from scrimba, but still asked GPT and xAI for the best practise to realize it.
  • The most challenge part comes from Test Page, I have introduced a lot of state variables to follow the status while keep the page update. At the same time, I have practised a lot about dynamic styling.
  • reviewed the process to publish the React website in Netlify. At the first time deployment, the image link was broken due to I have not used the import way.
What specific areas of your project would you like help with?

Welcome to my site, and feel free to leave any suggestions and ideas you may have~!

Quiz website

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • JoyObaidu•350
    @JoyObaidu
    Posted 24 days ago

    The solution is accesible with the color change for every correct answers.

    The layout looks good on my screen

  • Duncan Chege•340
    @duncan-chege
    Posted 4 months ago
    • Add an error state when someone clicks the "Submit Answer" button yet they haven't chosen an option in the question
    • Space your icons from the text in the option question boxes
    • Reduce the opacity in your options box-shadows
    • Change the button text in the final question from "Next Question" to "View Score"
    • Let your element styles in dark mode be similar to the Figma design

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub