Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

Sign up Form - Vanilla JS - Personal Additions and Animations

bem
P
Luciano Lima•1,270
@LucianoDLima
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


Thank you for checking out my challenge!

I learned quite a few things the past 2 months where I finally started learning JavaScript, so this is my very first JS project, be kind!

I actually remade this challenge three times! The first time I was struggling a lot, and there were quite a few bugs, then I gave up and started studying more, tried again, still struggled.. Then I started again yesterday and everything just clicked! Third time is a charm

CUSTOM DESGIN - My personal additions:

  • I added a few new error messages for when a special character is used inside Name and Last Name.
  • I learned and used regex in order to make the validation form for the Name, Last Name and Email.
  • I added an eye icon when you type in the password so that you can see what you typed if you click on it.
  • I added a small animation to the placeholder when you click in the input field, and because of that I removed the "email@example/com" that the design asked for.

Any and all feedback is welcome, thanks!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aruj Joshi•290
    @gtalin
    Posted about 2 years ago

    Congratulations on completing the challenge. Your solution looks perfect. The personal additions that you have added to the solution are impressive.

    Absolutely love the placeholder animation. Initially when I saw it I thought maybe you used material design (They have a similar transition for placeholder). But it is even more impressive that you have used vanilla CSS for the transitions.

    Just looking at your solution no one could've guessed your personal struggles with the challenge. Thank you for sharing it and the solution.

    The attention to detail is really commendable. Really appreciate it.

    All the best for your future challenges.

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