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

Frontend Quiz App using Less for Css and Vanilla Javascript

accessibility, less, bem
P
Yulia•720
@YuliaLantzberg
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?

Somehow it was pretty tough for me to write it in vanilla js. I had to rewrite the js code thrice. The desire to leave it like this was strong but I kept it up. So not bad. Also this time work on Less and CSS and HTML went really smooth. And there is clear stable workflow for me now

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

I got so weird bugs in the process that couldn't find even theoretical explanation for them. For example when code reads the same data from an array, read 4 entries, but then for some reason cut them to 2. Inspite that while looping they still were 4. But I think I took many outcomes from this challenge. First of all, how frameworks ease us lives :-D. Second, if you don't have tools like redux and context, build code in the way that you needn't to pass data through many functions. Otherwise you'll get a lot of unexpected bugs. Clean eventListeners, otherwise it is a real pain, multiple calling events when you don't need it, memory leaks and so on. Keep functions independent as much as possible and don't forget about closures. Otherwise, you get unexpected results again. I know all that are known mistakes and reasons for existing best practices but somehow flew through fingers when writing in vanilla js.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    roswell•520
    @welpmoz
    Posted 7 months ago

    Your project looks great on both mobile and desktop devices, but it could use some improvement on tablets. The flow of the questionnaire is good; however, I noticed that when an option is incorrect, only the incorrect option is shown. It would be helpful to also display the correct answer in such cases as in the design. Additionally, be mindful of the border property. For example, if an element has a height of 10px and you increase the border to 2px (while hovering), it might cause unexpected behavior in the interface. Instead, you could set the height to 8px with a 2px border matching the background color, and on hover, simply change the border color.

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