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

Frontend Quiz with React

react
Andrew•420
@timshandrew
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?

So far this is the largest project I have tackled using React and as such my first time where I had to put some thought into design in terms of components. I was learning as I was going on this project and so next time I'd like to think I could come up with a cleaner implementation.

I am also proud of how I used CSS custom properties to allow for a somewhat clean implementation of theming.

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

My biggest struggle was with the styling of components. I was using CSS modules for the first time and was thinking too rigidly by trying to make everything a module. I later realised that it is of course okay to include some global styles.

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

One thing I was wondering though was for things such as the purple button. Is it worth making this a component simply to hold some related styling? The component has no state or special functionality and simply returns a HTML button. It is repeated with the same styling throughout the application however. How would you go about styling this (especially with CSS modules in mind). Would it be best to make a global (non module) button class for styling? My thought was to create a component and have an attached CSS module for the styling.

Thanks

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 Andrew'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

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.