Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

multi-step-form-main

less
@philgabby•600
@CHEGEBB
A solution to the Multi-step form 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?

I am most proud of the progress I've made in my JavaScript journey 🎉. Consistently taking on challenges has significantly improved my understanding of JavaScript concepts 💡. Next time, I will actively seek out more JavaScript challenges 🧩 and tackle them as I continue to grow each day 📈. This approach will help me deepen my understanding and mastery of JavaScript concepts I also used less for styling which was fun.

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

I encountered challenges in updating HTML content dynamically using JavaScript and implementing a monthly/yearly toggle button. To overcome them, I broke down tasks into manageable steps and utilized JavaScript functions for dynamic updates, while implementing the toggle button with event listeners and conditional statements.

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

How to dynamically update content using js

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dror Katzir•200
    @DorKatzir
    Posted over 1 year ago

    Hi, dynamically updating content using pure/vanilla js is a good choise for small things, but for a challenge like this one it can get unnecesery over complicated. So... even though I enjoy and preffer vanilla js, 6 months ago I've learned ReactJs and i must say that it magically takes care of all the dynamiclly updating the DOM content. I completed this challenge as my first project in React. I recommend Reactjs if you have a good js knowledge.

    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