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

Interactive Frontend Quiz App using React with Sass

react, sass/scss, vite, bem
P
Schindler Dumagat•370
@schindlerdumagat
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?

I learned how to use React to build applications using components. I used some React features such as state and props to create the logic of the application. I will build better React applications in the future by learning more about React and its features together with the best practices when building applications with it.

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

I struggled to display the images in React applications. I kept changing the URL paths of the images and it did not work. To solve that, I researched on how to fix it and it turned out that I was referencing the images incorrectly since it is a react application and it has a build feature. I need to place the assets in the public folder and reference it using its absolute path then it worked.

I also struggled on the start because I kept overthinking on how I should start the project and how I should build my components. But then I decided to just build it based on my current knowledge and just learn along the way.

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

Here are the things I am concerned about:

  • It was my first time to build a Frontend Mentor project with React. How well did I utilize react for this project? What do you think about my folder structure and my components?

  • In react, the app component is rendered in the div which has a class of root but div is not a landmark role. Tags that has a landmark role are header, main, footer, etc. Is it ok to leave it this way in a react application?

<body>
  <div id="root"></div>
  <script type="module" src="/src/main.jsx"></script>
</body>
  • I used the same sass folder structure the way I do it with projects where I use plain HTML, CSS and JavaScript. Is there a better way to use Sass in React applications?

As usual, any feedback is welcome!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    emawid•240
    @emawid
    Posted about 1 month ago

    Hi Schindler! Congratulations on completing the Frontend Quiz challenge. The app aligns well with the design files and the user interface works as intended. I'm not (yet) a React developer but I think you have your code neatly structured.

    If you are looking for ways to improve the app I would consider replacing the button elements with <a> tags for links on the Home page and with <input> elements (type="radio") on the Quiz page. Also, consider wrapping the options on the Quiz page with a <form> element. These changes would improve the semantics, accessibility and enable you to leverage the browser for validation. This could reduce the need for JavaScript.

    One last thing, when tabbing through the pages, its difficult to navigate to the theme toggle in the header. A quick-fix could be to target :active and add a border to the toggle button.

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