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

Building a Multi-Step Form with React, Styled Components, react router

react, styled-components, vite, react-router
abdulsalam11-alao•150
@abdulsalam11-alao
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?

Solution Retrospective What are you most proud of?

Dynamic Step Navigation: I’m particularly proud of how the steps in the multi-step form were linked dynamically using React Router. This allows users to navigate between steps smoothly and provides a clear, structured flow. Styling: The design of the form, especially the sidebar, came out great using Styled Components. It feels modern and clean, and the flexibility of this styling method made it easy to implement responsive designs. Error Handling and Form Validation: Implementing basic validation checks to ensure users can’t skip important fields helped make the form more robust and user-friendly. What would you do differently next time?

Use a More Robust State Management Solution: While React’s built-in state management worked fine for this project, I would consider using a more robust solution like Redux or React Context API for larger, more complex multi-step forms. This would make managing the state across multiple steps and components easier and more efficient. Add Animations and Transitions: Next time, I would add smooth transitions between form steps to enhance user experience. This would provide a more engaging feel as users move through the form. Improve Error Boundaries: Handling errors with more detailed error boundaries and alerts would give users clearer feedback if something went wrong. Implement Backend Integration: While this form collects user data effectively, integrating it with a backend API or service for persistent storage or sending the form data would complete the form’s functionality. Would love to hear feedback on the potential enhancements and suggestions for improving the state management!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mahmoud Elagamy•1,100
    @m-elagamy
    Posted 10 months ago

    Thank you for your hard work on this project. I've been using the application and have encountered a few issues:

    • 404 Page Errors: When reloading the app during any step, I consistently encounter 404 page errors. This can disrupt the user experience and lead to confusion.
    • Data Persistence: When I navigate to a different step and then return to a previous one, any changes I've made are not saved. This can be frustrating, as it requires me to re-enter information. It would be beneficial if the application could automatically save user input as they progress through the steps.
    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