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

Intro component with sign-up form using REACT JS & TAILWIND CSS

react, tailwind-css
meccoi•160
@meccoi
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


This is my first time using React again. Do you have any ideas, suggestions, or advice for a newcomer to React?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Fluffy Kas•7,655
    @FluffyKas
    Posted almost 2 years ago

    Heyo,

    Your solution looks nice! However, I'd suggest you look up a video or two about the basics of React. Here you're essentially using vanilla javascript in a React setup and then just put everything in a useEffect (it's not what useEffect is used for). Try looking up how event handling works in React and rework your logic accordingly.

    As a sidenote, the use of create-react-app is no longer encouraged, and has been removed from the official React documentation, for a number of reasons ( tl;dr, it's bulky and slow). There are a bunch of better options out there, check out the React docs. There's also Vite, as a very beginner-friendly option, perhaps I'd recommend this one for you. Tailwind has an easy setup guide for Vite as well.

    Regarding everything else:

    1. Instead of the button type input, it's preferable to just use a button element.
    2. All inputs need to have a label attached to them, even if they are not visible. Placeholders are not a replacement for this. Luckily, Tailwind has a really handy "sr-only" class you can put on the labels to keep them from showing up.
    3. Terms and Services should be a clickable link.
    4. The "Try it free for 7 days..." element shouldn't be a label. Labels are used to provide description for input. Here most probably you could just use a <p>.

    I hope this was somewhat helpful. Good luck (:

    Marked as helpful

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub