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

Overly Complicated Quiz App in JavaScript and CSS

P
Austin•430
@astnio
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 project was a huge challenge for me, and not for quite the right reasons. I learned a lot about proper planning for a project, and considering the architecture more thoughtfully ahead of time. This project really shouldn't have been very complicated, and yet my lack of planning and forethought made it quite the challenge.

In my defense, I tried to create a more robust system that is dynamically expandable. You should be able to add more quizzes and questions to each quiz, and the code should take care of the rest in generating the questions and everything for you.

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

I feel as though both my CSS and JavaScript are overly complicated for this project. I ended up throwing in all kinds of things into my CSS to account for edge cases, while I probably could have simplified the logic for a lot of this had I been more thoughtful.

Same thing with my JavaScript. In fact, the final product is much simpler than what I had midway through the project. I did quite a bit of refactoring that slimmed down the logic a bit here.

Overall, in the future, I will take more careful consideration of my projects, and probably write out an outline or draft in pseudo code to attempt to make things easier.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ikitamalarose•420
    @ikitamalarose
    Posted 10 months ago

    First of all, congratulations for thw work done and here is my contribution.

    1-Add the hover effect on the question with a colour on the boxes, check the figma model

    2-The warning message changes its coulour in light mode to make it red

    3-As you say, the code is loaded and you could have made sure that the js loads the content of each step automatically ( your first idea of coursse).

    For my part, i separated a file loadData.js that takes care of recovering the data data.json which we need. A file utils.js that takes care of creation of each component. And finally the file quiz.js that targets and adds the element in the html files as we progress.

    I hope i was helpful :)

    And otherwise it's great job

    Marked as helpful

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