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

Quiz Game with state management and templating

P
Radu Petre Tarean•560
@2XG-DEV
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?

This was a cool project altough a bit large to build out without a framework. I am proud of the state management I implemented and the templating.

Altough itsnot complete: -decided to stop before adding the night / day mode, -desktop layout for question and result page and -progress bar for question page

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

State management and templating are definetly hard without a framework or library but it was fun to see how even simple implementations can work.

The best advice is to follow clean code and not have too many things in the same function. Keep state management in one file, templating in another and use pure functions and immutable state

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

Nothing major to get help with. I decided to stop adding the features listed above because I decided I had spent enough time on this challenge and implementing these features will not help me learn anything new

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Jair•760
    @JairRaid
    Posted 4 months ago

    Here is a link to help you uderstanding flex and grid: -https://www.joshwcomeau.com/css/interactive-guide-to-flexbox/ -https://www.joshwcomeau.com/css/interactive-guide-to-grid/

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.

Oops! 😬

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

Log in with GitHub