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

React Newsletter Signup Form With Google Sheet API

fetch, react
Oscar Vaquera•270
@vaqueraoscar0
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


Technologies

  • React
  • HTML5/CSS3
  • Google Sheets
  • Google Script

Comments:

The Newsletter Signup Form challenge turned out to be more challenging than expected, especially when I accidentally deleted the entire project before deploying it. However, it was still a fun and rewarding experience. As an additional feature, I went beyond the basic requirements and created a way to store the submitted emails using Google Sheets and Google Scripts.

Instead of building a traditional backend, I used Google Sheets as a simple database to store the email addresses. I wrote a small piece of code using Google Scripts that allows the form submissions to be saved directly into a Google Sheet. You can check out the Google Sheet LINK HERE to see the collected email data.

If you're interested in how I made it work, I have included the script's code in my repository. You can take a look and try it out for yourself. This approach offers an alternative way to handle backend functionality without setting up a dedicated server.

I welcome any questions, comments, or feedback you may have about this project.

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 Oscar Vaquera'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.