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

Signup Form using NextJS, TailwindCSS and React Hook Form

accessibility, next, tailwind-css
Robert Williams•40
@RobertWilliamsCymro
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 did you find difficult while building the project? I found creating the mobile and desktop layouts quite difficult. I asked the community for help on this got a nudge in the right direction (use flex) so I got there in the end! I spent a lot of time tweaking the mobile and desktop layouts to get it as close as possible, this was something I was not expecting. But ultimately, I'm learning and I enjoyed the process!

Which areas of your code are you unsure of? I think my tailwindCSS code has not been written suitably for tablet layout (e.g. an iPad). I didn't have a design to go on. Does anyone have any suggestions on what to do so that it looks better?

Do you have any questions about best practices? I have put my react hook form code within my SignUpForm component. As a result, there's quite a lot of code in one file. Is there a better way of doing this? I feel like the validation code should be in it's own component but I didn't want to overcomplicate things!

Opinions on Accessibility I have changed the text colour for the sign up link ("By clicking the button, you are agreeing to our) so that it would pass WCAG 2.0. As Frontend Mentor uses axe-core for running tests on accessibility violations, perhaps future designs should consider things like appropriate colour contrast? It would mean then I wouldn't have to deviate from the design then!

This is not meant to be harsh criticism, please don't take it that way. Frontend Mentor does great work, and I'm thankful they have given me this chance to improve my skills :)

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 Robert Williams'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 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.