18F / 18f.gsa.gov

The 18F website
https://18f.gsa.gov
Other
293 stars 311 forks source link

Create an intake form #2100

Closed coreycaitlin closed 7 years ago

coreycaitlin commented 7 years ago

Per #2067, we want to create a form for collecting some basic information from leads, and to make the process of contacting us a little more predictable.

gemfarmer commented 7 years ago

@coreycaitlin pure html approach!

<!DOCTYPE html>
<html>
<body>

<h2>Send e-mail to someone@example.com:</h2>

<form action="mailto:someone@example.com" method="post" enctype="text/plain">
Name:<br>
  <input type="text" name="name"><br>
  E-mail:<br>
  <input type="text" name="mail"><br>
  Comment:<br>
  <input type="text" name="comment" size="50"><br><br>
  <input type="submit" value="Send">
  <input type="reset" value="Reset">
</form>

</body>
</html>

http://www.w3schools.com/html/tryit.asp?filename=tryhtml_form_mail

gemfarmer commented 7 years ago

@coreycaitlin update! More research and this shouldn't be a security concern. The current method that I suggested doesn't make sense though :( It opens the default mail application on a given device with populated content.

I think we want to do something like one of the following:

My vote would be formspree for ease of use, but I'm also not entirely sure how secure that service is. When I say security, I am more concerned about keeping the info confidential than our site being attacked.

gemfarmer commented 7 years ago

@gboone do you know if formspree has come up before?

gboone commented 7 years ago

I do not know anything about formspree. I suspect the Google Script option will be tricky because we'll have to auth it to an account. Is Mandrill worth exploring or is that more for sending a lot of email at once?

coreycaitlin commented 7 years ago

After some intrepid investigation by @gemfarmer, it sounds like...

Other, similar forms out in the wild include:

In the long run, the right answer might be to build a form that's fully integrated with Salesforce or whatever CRM-type tools we're using. If it comes up again, here's the language I drafted for this form:

screen shot 2016-12-07 at 11 39 33 am

HOWEVER, for now, this doesn't seem like a very minimum viable way to solve the core user need of knowing what will happen when they contact us, and making action a little easier to track.

Closing out this issue for now, and pursuing simpler ways of solving #2067.