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

NextJS, Shadcn UI, React-hook-form, Zustand, and Zod Multi-step form

next, react, tailwind-css, typescript
Ebenezer•560
@ekankam
A solution to the Multi-step form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This challenge was bit difficult for me because I have never built a multi-step form before. I struggled to figure out how to manage the state and form validations. And since I haven't used most of these tools in my personal projects before I had to learn them while trying to build this component. But I am glad I decided to use different tools such as React-hook-form, Zod, Zustand, and Shadcn UI. I usually don't use any of these in my projects because I recreate everything from scratch. But once I figured how to use these tools the build became a little easier. And now I can say I love these tools. Especially Shadcn UI.

Any feedback is welcome. Especially with Zustand. I followed the documentation but I can't help but wonder if there might have been an easier way to use it.

Thank you.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    RicardoAymay•40
    @RicardoAymay
    Posted over 1 year ago

    Nice work. I had a difficult time with the styling with the checkbox. I just could not figure how to add the phone number to go ahead. But to be frank, I liked your first form more than the 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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub