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

Multistep Form Built with Next.js and Mantine-UI

next, react, tailwind-css, typescript, vite
Fanuel Amare•200
@Fanu-Cd
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'm most proud of how intuitive and user-friendly the multistep experience turned out. The combination of Mantine Stepper and custom layout allowed me to create a clear, guided process that adapts well to different screen sizes. I was also able to manage complex form state across multiple steps without losing data or disrupting the flow—something that can easily go wrong in multistep interfaces.

If I were to do it differently next time, I would invest more time in abstracting the form logic and validation schemas into reusable hooks or utilities. That would make the solution more scalable and maintainable if the number of steps or fields were to grow. I’d also consider integrating persistent form state (e.g. via localStorage or session) to improve UX in case of accidental page refreshes.

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

I didn’t encounter any major challenges during this project, thanks to my familiarity with Next.js and Mantine UI. Having a solid understanding of both frameworks allowed me to implement the multistep logic, responsive design, and validation flow smoothly. Minor refinements—like managing step transitions and conditionally displaying validation messages—were handled through deliberate planning and clean state management.

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

I didn’t require help during this project. The implementation went smoothly, and I was able to handle all aspects confidently using my existing skills in Next.js and Mantine UI.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•8,750
    @MarziaJalili
    Posted about 2 months ago

    Flawlessly done, no cap! 💯

    🌟 A tiny adjustment?

    ✅ Update the input for phone number as follows:

    <input type="number" />
    

    ✅ It is best practice to set it like that because it will not let alphabet letter as it's value, man.

    ✅ Also, the repo's link is broken. ⛓️‍💥 You may as well fix that too.

    The web's running like clockwork work; keep up the grid!

    😎😎😎

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