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

React/vite/React router /react form / MUI ** multi step with dark mode

material-ui, react, react-router, vite, accessibility
Yousef•90
@ousey-ousey
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?

this project nearly take 7 hours in one day

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

some advices * upload the images in internet so you get url address so it work with you

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • aberllin•80
    @aberllin
    Posted 12 months ago

    Hi Yousef! It's amazing you've decided to use additional libraries and you've also added light/dark theme! Love it!

    There are some of my feedback:

    • The state is not persistent in the first step. When navigating back, the information entered is lost. Ensuring the state remains consistent would improve user experience.
    • The step box (the square with the step number) appears too dark in the light theme, making it difficult to distinguish from the background. Adjusting the color for better contrast would help.
    • On the adds-on page, the boxes become jumpy when checking/unchecking an option. This might be due to the absence of a transparent border initially, which then appears when an option is selected. Adding a consistent border could resolve this.
    • Validation on the first page is preventing users from proceeding to the next step, yet they can still click the next step from the left sidebar. Ensuring that navigation through the sidebar also adheres to the validation rules would ensure a smoother process.

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