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

Responsive Multi-Step Form with React and Context API

react, tailwind-css, vite, material-ui
P
Damilola Emmanuel•230
@Damilordz
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?
  • Most Proud Of:

    • Successfully implementing Context API for the first time to manage global state effectively.
    • Overcoming the challenges of making form inputs mandatory before allowing navigation to the next step.
    • Gaining a deeper understanding of Context API and how to manage complex state interactions.
  • What I Would Do Differently:

    • Optimise the error-handling logic further for better scalability in larger forms.
    • Explore custom hooks for cleaner and more reusable state logic.
What challenges did you encounter, and how did you overcome them?
  • Challenges:

    • Ensuring that users could not proceed to the next step without filling out the required personal information fields.
    • Managing the global state using Context API for the first time, especially keeping track of form data across multiple steps.
  • How I Overcame Them:

    • For form validation, I implemented error-checking logic using useEffect and tracked errors in the component state. This ensured users were alerted when a field was left empty.
    • By reading documentation and experimenting, I gained a solid understanding of how to structure and use Context API for handling multi-step form state. This included separating state management for plans, add-ons, and form data into logical contexts.
What specific areas of your project would you like help with?
  • Suggestions on how to optimize the state management for large forms with multiple nested contexts.
Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

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