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

Intro-component-with-sign-up-form-SCSS-Formik Public

react, vite, sass/scss
Teodor Jenkler•4,040
@TedJenkler
A solution to the Intro component with sign-up 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?

What I'm Most Proud Of: I’m most proud of learning how to use Formik for form management and Yup for validation, which streamlined the process and improved the user experience.

What I’d Do Differently Next Time: I’d avoid deep SCSS nesting, as it can complicate the code and make it harder to manage. Simplifying the SCSS structure would lead to more maintainable and clearer styles.

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

Challenges Encountered: I faced significant issues with SCSS nesting, which became overly complex and difficult to manage.

How I Overcame Them: I had to rewrite parts of the SCSS code to simplify the nesting. This process taught me the importance of maintaining a flatter and more manageable SCSS structure for better maintainability and clarity.

What specific areas of your project would you like help with?

SCSS Code: I’d appreciate feedback on how to improve my SCSS code. Any tips on organizing SCSS for better maintainability and clarity would be very helpful. Best practices for writing clean and efficient SCSS would also be welcome.

Formik & Yup Tips: I’m looking for best practices or tips on using Formik and Yup more effectively. Insights on optimizing form validation and management, as well as common pitfalls to avoid, would be greatly appreciated.

Feel free to provide any additional suggestions that could enhance the overall quality of my project.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Solomon Obanijesu Philip•1,200
    @Hackerbot24
    Posted 11 months ago

    Nice Job Ted Keep it up it's impressive

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