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

Responsive Multi Step Form (React/Typescript)

react, recoil, typescript, styled-components
aberllin•80
@aberllin
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:

  • Responsive Design: I'm really proud of how the design adapts seamlessly between desktop and mobile. It looks professional and user-friendly on all devices.

  • Component Structure: The use of atomic design principles to break down the UI into reusable components made the code more maintainable and scalable.

  • Theming with Styled-Components: Implementing a global theme made it easier to manage colors and sizes consistently across the application.

What I will do differently next time:

  • Initial Setup: Instead of setting up Webpack from scratch, I might start with Create React App or another boilerplate to save time on initial configuration. (As I eventually did.)
  • Testing: I would integrate more comprehensive testing (unit tests with Jest and integration tests with React Testing Library) from the beginning to ensure the application is more reliable.
  • Accessibility: I would focus more on accessibility features to ensure the application is usable by everyone, including keyboard navigation and screen reader support.
  • TypeScript Integration: Adding TypeScript improved the code quality by catching errors early and providing better documentation through types.
What challenges did you encounter, and how did you overcome them?

Challenges Encountered:

  • Webpack Configuration: Setting up Webpack and configuring it correctly for a custom React setup was challenging and time-consuming. (Eventually used create-react-app).
  • Static Assets Management: Ensuring that images and fonts were correctly referenced and loaded, especially when dealing with different environments and build processes.
  • Responsive Design: Making sure the design looked good on all screen sizes required careful consideration and testing.
  • State Management in Forms: Managing state across multiple steps of the form and ensuring data was passed correctly between steps was a bit tricky.

How I Overcame Them:

  • Learning and Documentation: I spent a good amount of time reading documentation and various tutorials to understand the configuration better.
  • Using Create React App: For the final version, I switched to using Create React App which simplified the setup process and handled a lot of the configuration automatically.
  • Media Queries and Flexbox: For responsive design, I relied heavily on CSS Flexbox and media queries within styled-components to ensure the layout adjusted properly.
  • Breaking Down the Problem: For managing state, I broke down the problem into smaller pieces, creating reusable form components and using local state in each step before consolidating the data at the end.
  • Debugging and Testing: I used browser developer tools extensively for debugging issues with assets and layout. I also tested the application on different devices to ensure it was responsive.
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 aberllin'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.