-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs(www): add Build a Contact Form reference guide (#14564) #14768
Changes from 3 commits
83fcc3c
43b0661
7ac93e0
3ef68f3
dd9ad59
5211b5a
0aff87d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -0,0 +1,140 @@ | ||||||
--- | ||||||
title: Building a Contact Form | ||||||
--- | ||||||
|
||||||
This guide covers how to create a contact form in a Gatsby site, along with an overview of some strategies for handling form data that has been submitted. | ||||||
|
||||||
## Adding a Contact Form | ||||||
|
||||||
Gatsby is built on top of React. So anything that is possible with a React form is possible in Gatsby. Additional details about how to add forms to gatsby can be found in the [Adding Forms](https://www.gatsbyjs.org/docs/adding-forms/) section. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
## Creating an Accessible Form | ||||||
|
||||||
Faulty forms are a common barrier to a website's accessibility, and can be especially problematic if you use a keyboard and screen reader to navigate the web. Forms should be clearly and intuitively organized into groups of related information, and each form field should be identified with a proper label. | ||||||
|
||||||
More information on creating accessible forms can be found in [WebAIM's article](https://webaim.org/techniques/forms/) on the subject. | ||||||
|
||||||
## Sending Form Data | ||||||
|
||||||
When you submit a form, the corresponding data is typically sent to a server to be handled in some manner. More in-depth information on sending form data can be found [on MDN](https://developer.mozilla.org/en-US/docs/Learn/HTML/Forms/Sending_and_retrieving_form_data). | ||||||
|
||||||
Each method detailed below will start with the following contact form: | ||||||
|
||||||
```jsx:title=src/pages/contact.js | ||||||
<form method="post" action="#"> | ||||||
<label> | ||||||
Name | ||||||
<input type="text" name="name" id="name" /> | ||||||
</label> | ||||||
<label> | ||||||
<input type="email" name="email" id="email" /> | ||||||
</label> | ||||||
<label> | ||||||
Subject | ||||||
<input type="text" name="subject" id="subject" /> | ||||||
</label> | ||||||
<label> | ||||||
Message | ||||||
<textarea name="message" id="message" rows="5" /> | ||||||
</label> | ||||||
<button type="submit">Send</button> | ||||||
<input type="reset" value="Clear" /> | ||||||
</form> | ||||||
``` | ||||||
|
||||||
marcysutton marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
### Netlify | ||||||
|
||||||
If you're hosting your site with Netlify, you gain access to their excellent form handling feature. Setting this up only invloves adding a few form attributes: | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
```jsx:title=src/pages/contact.js | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This could be a good place to use a I also had trouble trying to make this work, I put the default starter on Netlify with this code and I don't actually get submissions to go through: https://amazing-roentgen-d0c1a6.netlify.com/netlify/ I also looked at Netlify's example that worked okay, but it uses plenty of JavaScript even though their docs say you just need to add a few html attributes like this. Do you have an example where you got this working by chance? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I have it working on my site: https://github.com/marcysutton/gatsby-site/blob/master/src/pages/contact.js |
||||||
<form method="post" netlify-honeypot="bot-field" data-netlify="true"> | ||||||
<input type="hidden" name="bot-field" /> | ||||||
... | ||||||
</form> | ||||||
``` | ||||||
|
||||||
Now, all submissions to your form will appear in the Forms tab of your site dashboard. By adding the form attribute `netlify-honeypot="bot-field"` and a corresponding hidden input, Netlify will know to quietly reject any spam submissions you may receive. | ||||||
|
||||||
More information on Netlify Forms can be found [on their website](https://www.netlify.com/docs/form-handling/). | ||||||
|
||||||
### Formspree | ||||||
|
||||||
Formspree offers a generous free-tier service for handling form submissions on static sites. This makes it a great tool for having form submissions sent directly to an email address of your choosing, with very little setup required. | ||||||
|
||||||
In order to begin leveraging Formspree's features, you must add a form action directing the http POST method to the Formspree API (substituting your chosen email), as well as changing the `name` attribute of the email input to `name="_replyto"`. | ||||||
|
||||||
```jsx:title=src/pages/contact.js | ||||||
<form method="post" action="https://formspree.io/[email protected]"> | ||||||
... | ||||||
<label> | ||||||
<input type="email" name="_replyto" /> | ||||||
</label> | ||||||
... | ||||||
</form> | ||||||
``` | ||||||
|
||||||
Once you've made the changes you can submit your own form for the first time and register using the email Formspree will send you, and all subsequent form submissions will be sent to your email address. You can find more information on the registration process or setup [on their website](https://formspree.io/). | ||||||
|
||||||
### Run Your Own Server | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
This is just a style guide thing 🙂 https://www.gatsbyjs.org/contributing/gatsby-style-guide/#format-titles-and-headers |
||||||
|
||||||
If your form data requires a significant amount of business logic to handle, creating your own service might make the most sense. The most popular solution to this is writing an HTTP server - this can be done in many languages including PHP, Ruby, GoLang, or in our case Node.js with [Express](https://expressjs.com/). | ||||||
|
||||||
An initial implementation of a server using express, body-parser, and nodemailer may look like this: | ||||||
|
||||||
```javascript:title=handleForm.js | ||||||
const bodyParser = require("body-parser") | ||||||
const express = require("express") | ||||||
const nodemailer = require("nodemailer") | ||||||
|
||||||
const app = express() | ||||||
app.use(bodyParser.urlencoded()) | ||||||
|
||||||
const contactAddress = "[email protected]" | ||||||
|
||||||
const mailer = nodemailer.createTransport({ | ||||||
service: "Gmail", | ||||||
auth: { | ||||||
user: process.env.production.GMAIL_ADDRESS, | ||||||
pass: process.env.production.GMAIL_PASSWORD, | ||||||
}, | ||||||
}) | ||||||
|
||||||
app.post("/contact", function(req, res) { | ||||||
mailer.sendMail( | ||||||
{ | ||||||
from: req.body.from, | ||||||
to: [contactAddress], | ||||||
subject: req.body.subject || "[No subject]", | ||||||
html: req.body.message || "[No message]", | ||||||
}, | ||||||
function(err, info) { | ||||||
if (err) return res.status(500).send(err) | ||||||
res.json({ success: true }) | ||||||
} | ||||||
) | ||||||
}) | ||||||
|
||||||
app.listen(3000) | ||||||
``` | ||||||
|
||||||
This initial implementation listens for POST requests to `/contact`, and sends you an email with the submitted form data. You can deploy this server with services such as [Now](https://zeit.co/now). | ||||||
|
||||||
Once deployed, note the url of the deployment (something like `my-project-abcd123.now.sh`), and use it as your form action: | ||||||
|
||||||
```jsx:title=src/pages/contact.js | ||||||
<form method="post" action="my-project-abcd123.now.sh/contact"> | ||||||
... | ||||||
</form> | ||||||
``` | ||||||
|
||||||
Now, all subsequent form submissions will be sent to your email address! | ||||||
|
||||||
For an in-depth guide on running your own mail server, you can refer to [this awesome guide by DataFire](https://medium.com/datafire-io/simple-backends-four-ways-to-implement-a-contact-us-form-on-a-static-website-10fc430984a4). | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Are there any security/spam implications we should mention here? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I found an article that goes into some of the detail of complexity and spam implications, though it isn't messaged from the perspective of a static site: https://www.digitalocean.com/community/tutorials/why-you-may-not-want-to-run-your-own-mail-server |
||||||
|
||||||
## Other resources | ||||||
|
||||||
If you have any issues or if you want to learn more about implementing your own contact form in Gatsby, check out this tutorial from Scott Tolinski: | ||||||
|
||||||
`youtube: hF7xJhzrr9s` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this would be fine to be removed since the paragraph below it is mostly just more overview information and the title says pretty close to the same thing.