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

Continue Form Practice

react, tailwind-css
tOnski86•330
@tOnski86
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?

This was more trial and error than anything (although there are a lot more errors than I'd hope!) to keep practicing forms in React.

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

Yesterday when I did the form, I was happy to get it to work. Now - I have mixed feelings because now that I kinda understand the inner workings, I realize that there is more to it than simply styling the form.

Design Challenges

  • In general, I still need to build confidence when to use borders, outline and ring.
  • Styling and animating the success message - struggled with this because this is my first time.
  • Overall animations. I want to get to the point where the design and the user interactions are fluid.

Logic Challenges

  • I was able to abstract the input type='text' into its own component but for the other field types, such as checkboxes and radio, I am still struggling to control them. They react differently to styling so I will have to keep working on them to get confident, same as I did with the text inputs. I will keep working on getting familiar with forms as is, before checking out React form libraries.
  • I attempted and failed (again) to use and understand useReducer, but realized I will need two objects to interact - the user input object and the error object, so I went back to using useState instead.
  • I also attempted to use useEffect to make errors appear depending on the user input before submit. Opted to have the errors show up on submit instead.
Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on tOnski86'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
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.