Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

ReactJS TailwindCSS Vite Newsletter Sign-up

react, vite, tailwind-css
lavollmer•480
@lavollmer
A solution to the Newsletter sign-up form with success message 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?

Reflecting on this project, I take pride in its outcome. I learned new concepts and reinforced my knowledge on various topics. What I found rewarding was the process of writing my README and reviewing my code. During this review, I discovered opportunities to refine and enhance my code which was great.

Next time, I would give myself more time to work through the form submission logic and code. It was more challenging than anticipated.

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

Throughout the development of this application, I gained valuable insights and learned several key concepts:

React Router Dom: This npm package uses dynamic routing in web applications, ideal for creating single-page applications (SPAs) where content is dynamically loaded based on the URL. Its benefits include enhanced speed and performance. The Router component acts as a container for all other components, while Routes define the navigation paths within an SPA. The Route component checks the current URL and renders the corresponding component, and Link is used for creating navigable links to different paths.

Email Validation: I implemented a validateEmail function that accepts an email address as its argument. This function uses validate.test(email), where validate is a regular expression that matches the basic structure of an email address, to determine if the provided email matches the expected pattern. It returns true if the match is successful, and false otherwise.

handleSubmit Function: This function is designed to process user input. It prevents the default page reload, validates the email address, and provides an appropriate response based on the input. If the validation checks are passed, it navigates the user to a thank you page.

Refactoring Code for Success Variable: During a review of my code, I noticed that I had included a success variable for conditional rendering, which ultimately was unnecessary. Initially, setting this variable to true would conditionally render a "Thank you for subscribing!" message. However, after integrating a dedicated thank you component page that appears upon submitting a valid email, I found the success variable and its associated code redundant. Removing this extraneous code streamlined the program's functionality.

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

For my buttons, I would love to create a gradient with the tomato color based on the design. Help would be 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 lavollmer'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.