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

A Responsive Multi step Form using Next.JS with Typescript and Shadcn

next, redux-toolkit, shadcn, typescript
Abdalla emad•200
@abdallemad
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 I implemented the multi-step form logic using Redux Toolkit for state management and how I integrated animations with Framer Motion to enhance the user experience. I also enjoyed working with ShadCN UI components, which made styling clean and consistent.

If I were to do it again, I would focus more on accessibility and form validation edge cases. I’d also consider adding unit and integration tests to make the solution more robust and production-ready.

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

One of the main challenges was managing the form state across multiple steps while keeping the codebase clean and scalable. I solved this by using Redux Toolkit to centralize the state, which made it easier to manage and debug.

Another challenge was implementing smooth step transitions without breaking the form logic. I used Framer Motion to handle animations, and I had to carefully coordinate the animation timing with form validations and state updates to avoid any glitches.

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

way to handle multi-step form state. I’m also open to suggestions on improving the user experience, especially regarding transitions and animations between steps using Framer Motion.

Additionally, any tips on improving form validation patterns and making the app more accessible (a11y) would be super helpful.

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 Abdalla emad'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.