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

Responsive Contact Form with Animated Toast Notification

sass/scss
P
krru09•200
@krru09
A solution to the Contact 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?

I'm most proud of stepping out of my comfort zone for this challenge. Specifically, I utilized grids, keyframe animations, and switch cases (as opposed to ifs and nested if/else if/else statements). I don't really enjoy using grid, although I know it can offer more capabilities for layouts (especially complex ones), but I also just wanted to practice it without feeling overwhelmed. As I'm completing more projects, I wanted to step outside of the box and utilize an animation for the toast notification. I wanted to make this form reusable so the best way to do it for me was to have the notification slide out once the user reads it. Finally, I noticed that I was doing too many if and else ifs... so I decided to implement switch cases if I felt that a specific scenario could utilize them (e.g., running a block of code based on the type of form element).

What I would fix is my localStorage when saving current form data. The only way I thought I could fix it was to simply refresh the page after the user submits the form to ensure that no old form data was saved within the program. I did not really like this since I didn't want the page to refresh at all, but it's okay.

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

While utilizing grid, particularly for the first and last names, I did not check if my grid set up worked for all use cases (if both inputs were valid, if both were invalid, or if 1 was valid and the other was not). I tested it well after, and after hundreds of lines of code written, I noticed that my layout broke when it was one invalid input and one valid input.

The best fix at this point for me was to set up the grid with a third row that accounted for the error message, that way the layout will stay the same regardless of whether the error message was hidden or visible. This added unwanted spacing though, but it was the best fix at the moment for me.

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

Any feedback is appreciated!

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 krru09'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.