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

20th Challenge - Multi-step form

tailwind-css
drunken_neoguri•290
@DrunkenNeoguri
A solution to the Multi-step form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


(This was written using a translator. The grammar can be very awkward!) Long time no see. And Happy New Year!

It's already the 20th challenge, and this challenge is much later than usual. With the end of the year approaching and the new year approaching, my mind has become lazy.

Still, in the new year, I made up my mind again and coded hard to study steadily.

This time, I worked with pure JavaScript, not React, which I have been using for a while. In addition, I loaded and used Tailwind CSS through CDN.

While working, it was fun, but on the other hand, 'Are my coding skills really good?' I often think about it. I guess I lost a lot of confidence.

I want to be good at coding. I want to do well somehow and get a job as a new web front-end developer!

If you don't mind, please leave code reviews as Github Issues or comments! The code reviews and feedback you left are the driving force for me to study further!

thank you!

(! The Github README is in Korean. Please refer to it.)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

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

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.