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

Using React/styled-components/react-hook-form/yup

react, styled-components
Jansana Dylan•60
@SwiichyCode
A solution to the Multi-step form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


"Hello! Today, I present my solution for this challenge:

-Path Architecture: It may seem a bit heavy and complex for this challenge, I admit. I tried to approach it as closely as possible to a real medium-sized application, and I really like Atomic Design. As you may have noticed, each component contains its own logic and style. I prefer this approach as it seems more readable and accessible to me.

-Components: There are some examples of reusable components in the project. For me, creating reusable components is essential when working with this type of component-oriented framework. I plan to create my own component library for my personal and professional projects in the future.

-Styles: As for the style, there isn't much to specify. The use of styled-components in this case simply serves to open a portal for me to write my CSS and pass props. I don't use all the features of the library.

-Features: Managing state in localstorage, which will allow the user to return to the specific index where they left off on the form while keeping their data, refactoring the CSS to remove duplicates, etc."

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!

    I liked your implementation!

    I liked a transition effect you've implemented when a user changes plan from monthly to yearly - quite neat 👏.

    I liked that you already implemented email and phone verification - and noticed that phone verification perceives a number that starts with a "+" as an incorrect one. The "+" symbol indicates that the number is an international phone number and is followed by the country code. This helps to ensure that the phone number is formatted correctly and can be properly recognized by phone systems and carriers.

    There are some differences with initial design, but I personally am good with them :)

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