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

multi step form with Vuejs and dark mode! <3

vue, pinia
Lucas Matheus•400
@Lukiticas
A solution to the Multi-step form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Oh, how i missed you guys <3

So, i started to learn vue this week and nothing would help more than building a real app sooooo here i'm!!

It was a little difficult because i hadnt done something like this for a while, but vue and its systems made it easy!

  • i used pinia for storing user inputs and repopulating the components with them.
  • made a custom directive to handle the stepper logic
  • used vue <Component :is="component" > for mutating the steps component

What i'll be trying to implement:

  • I tried to use <Transition name=""> tag to animate the transitions between steps change, but it was very buggy, it bet its something about the element getting its position absoluted and then its width shrinking making a mess...
  • i would love to add more steps...

That was it! Hope you liked and please, please, please, i'm still learning so i would LOVE critics, opinions, tips and tricks envolving vue. See ya <3

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Katja Danilova•340
    @katjadanilova
    Posted over 2 years ago

    Hi, Lucas!

    Your animations are fantastic, they are elegant and perfectly match the design. I regret only not thinking of them myself :D.

    The only thing I noticed that is slightly off, is that the phone number field doesn't accept a "+" at the beginning of the number.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub