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

frontEnd-quiz-app

Tuna Erten•430
@tunaerten
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 turned out to be quite challenging. Unfortunately, limited time made it a lengthy process to complete. Each time I took a break, resuming with a fresh understanding of the code proved difficult. JavaScript presented its own set of hurdles, and the responsive design across different devices was especially complex. I’ve decided that in future projects, I’ll start with a detailed sketch. While I began with mobile and moved up to tablet and desktop, I faced unique challenges at each breakpoint, often requiring code adjustments. I also learned that separating media queries into a dedicated file made reading and updating the code much easier. On multiple occasions, I accidentally altered my original code, causing issues. Overall, it was a long marathon for me, but I’m pleased with the result.

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

Initially, I created separate HTML pages for each option and navigated between them via JavaScript. Using different pages might seem a bit excessive for a small project like this, but I wanted to try it out. However, I encountered various issues, the biggest being that dark and light mode settings had problems despite saving them in localStorage. Later, I restructured almost everything into a single HTML document, which made things easier. I’d be very grateful for any suggestions or help from anyone who has experience with multiple HTML pages.

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

I am gladly open to any suggestions!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Weverson Godinho•490
    @Godinhoweverson
    Posted 8 months ago

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