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

MultiStepForm using React and vite, styled with Tailwind

react, vite, tailwind-css
Jonathan Betancur•90
@Jonathanbees
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?

This is my first challenge using a library that is almost new for me, and that´s react, and also using something completely new for me called tailwind, to the next time i will develop best practices using react and tailwind, investigate new hooks and tools that would help me to develop faster and better my app!

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

Mixing this react and tailwind and knowing step by step some different hooks and ways to develop the multistepform became too challenging but funny at the same time because each day i discovered something new about react or about tailwind, or even both, and that´s the important thing of all of this, i´m really happy what capabilities i have and what i don´t have yet to become better each day

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

about the react logic using each hook and consts, i don´t know if that´s the best practices (i don´t think so) so i would really happy if any of you comment me all the best practices to develop components like this project, or told me ways to improve it or whatever makes the things better, even in tailwind classes or styles, but the most important is about react logic, form and state management, thank you :3

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Jonathan Betancur'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
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.