Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

Multi Step Form (HTML, CSS, JS)

Matthew•55
@MatthewBosveld
A solution to the Multi-step form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any feedback welcome. The code itself is quite messy, tried to organize it by declaring the variables per step at the top, then declaring the functions below those. Quickly found that scrolling up and down was more of a drag, and especially as the file got bigger I noticed that having (almost) all variables at the top did not really offer any benefit anymore. At that point I gave up trying to organize it, but it is noted for the next project. We live and we learn.

I was often wondering if my way of doing things was the most efficient (unlikely) or even considered bad practice. For example, the way I hide and show elements in this code seems a bit 'basic'. I knew creating elements and appending them was an option, but with the way I started the project (a bit naively just went straight in) I felt it would be too much of an effort to make that a thing.

So if there is any feedback on that, it would be very welcome. Things that are bad practice, things that can be more efficient. But also maybe things that are actually good practice and efficiently done.

Most differences between my project and the design images (I did not have the design files - used the free version) are intentional as I prefer it (e.g. displaying the yearly offer and resetting the add ons after going back to step 2) or small details which would be easily correct with the design files (font sizes, colors, etc.).

Also definitely did not forget ( ;) ) to make it resizeable to mobile. Will do that in the near future, as well as adding some transition effects to make it all look and feel nicer.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Matthew's solution.

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.