Ask HN: 2023 way to do contact form
I'm a little late to the public cloud party, you might say, but better late than never. I'm hosting the new site in an S3 bucket fronted by CloudFront.
My natural instinct would be to wire a contact form to a mailer running on the web server hosting the site, which, as we know, is so Jurassic an impulse as to be wholly ruled out in this brave new serverless world. Putting such functionality in Lambda gives me the sense of taking a labourious detour to reinvent some kind of wheel, since people with far less technical acumen are throwing up contact forms every day.
I have experience with some third-party overlay products for contact and engagement, e.g. www.livechat.com. Maybe I'll come back to that idea, but today I want a contact form that generates an e-mail, or perhaps calls a webhook/POST-back.
I'm embarrassed to say, I don't really know how to get a high-quality contact form going in a truly turn-key, serverless, 2023 way. Recommendations appreciated!
13 comments
[ 2.7 ms ] story [ 51.8 ms ] threadI am clearly capable of solving this problem in a large variety of ways. What I really want to know is how everyone else is solving it, especially those who ain't got time for all that.
A key requirement of doing things "in the cloud" nowadays seems to be to divest oneself of any and all perceived non-core competencies, no matter how relatively trivial, sourcing anything that strays by so much as a detectable micron from the "core mission" from either from third party services or NPM dependencies.
Okay, I want to drink the Kool-Aid. How do I do it with a contact form? ;-)
I've also found that people are generally pretty happy to schedule short meetings. I've personally had a very good experience with calendly! I've posted my schedule as an example below. Feel free to say hello :)
[1] https://dreamdaddy.io
[2] https://calendly.com/taylor-town/30min
Specifically with workers, you can send unlimited emails for free, which is great for plugging into your existing workflows.
Another nice thing about Workers is that they can sit in your codebase as JS files alongside your front-end code and auto-deploy when you push changes to Github/Gitlab/etc.
[1] https://blog.cloudflare.com/sending-email-from-workers-with-...
[2] https://developers.cloudflare.com/workers/wrangler/ci-cd
[1] https://tally.so
https://gist.github.com/thoughtpalette/d2cc6b88d32cb4613b037...