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

Responsive Multi-Step-Form

react, vite, tailwind-css
Luca•350
@lgorvin
A solution to the Multi-step form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Took me a while to complete, I did all the design first and then worked on the calculations for the total afterwards in hindsight I should have done it the other way round.

I used tailwind as it makes writing CSS much quicker but as a result my code looks pretty messy.

I still need to work on the total calculations because currently if the user changes add ons the total doesn't go back down.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Jo89 😈•510
    @AhmadYousif89
    Posted over 2 years ago

    Hi there, just to add to @Ruben's comment, I noticed that if you reached to step 3 (addons) then went back to step 1 then went back again to step 3 you will see that both step 2 and 3 gets selected and rendered to the screen (I guess the nav buttons for the steps have the same id or so). similar thing happens with step 4 but in this case to doesn't trigger the step on first click but rather on the second attempt! and you might need to take a look at the generated report for the accessibility and html validation errors

    Marked as helpful
  • Ruben•550
    @RubenSmn
    Posted over 2 years ago

    Hi Luca, great work on this multi step form! I was impressed by the animation on the check icon! I did find some things that could be improved.

    UI/UX improvements:

    • changing the plan to yearly does not auto adjust the height of the cards
    • switch button does not have a pointer as a cursor
    • the Go Back and Next Step buttons do not have a hover effect

    State/JS improvements:

    • there is no plan pre-selected
    • when selecting a yearly plan the add-on prices don't update
    • when you select a plan and deselect it on the Finish screen there is no plan only the (Monthly) text. But the total price still has the previously selected plan price.

    I hope you find this helpful, happy hacking!

    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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub