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

Multi-Step-Form (React, Sass, Vite)

react, sass/scss, vite
Sankalpa Sarkar•520
@IllusiveCoder1101
A solution to the Multi-step form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello everyone , I completed yet another project , It did Take me a while. Things I used to built this Project:- 1.React (Reason:- To handle state Management and also to organise my code.) 2.Sass (Reason:- To seperate out my css into different files.) 3.Vite (Reason:- Much faster than NPM) Things I will fix Later :-

  1. Accessibility :- There is an accessibility issue that you guys might encounter which is related to the Headings, I will fix that as soon as possible.
  2. First page issue:- There is currently an issue on the first page of the website where once u add the details , and move to the next page and comeback , the details will be gone, I probably have to add a "value" to my input fields, which I will do as soon as possible.

If you guys find any other bugs/problems/code issues please feel free to inform me , your feedbacks are always welcome .

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Olalekan Bello•180
    @OlaOluwalekan
    Posted over 2 years ago

    Hi!

    Viewing your first step, your app design was cool, but I can't view it further. I can't also move to subsequent steps. Also, I noticed the border of your steps is oval instead of a circle. Though I haven't used vite before, I would like to know how to use it. Overall nice try

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