Skip to content
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

Evaluate contact form submission strategy #83

Open
mradamcox opened this issue Nov 13, 2023 · 1 comment
Open

Evaluate contact form submission strategy #83

mradamcox opened this issue Nov 13, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@mradamcox
Copy link
Collaborator

Currently this is handled with a Google script, would it be better to turn this into a Netlify form? We are starting to use Netlify for forms on other sites.

One thing to look for is where these form submissions are currently going and stored, and whether there are people getting alerts for these submissions who wouldn't be able to get alerts if we switched to Netlify.

@Makosak
Copy link
Collaborator

Makosak commented Dec 20, 2023

There are a few forms-- I thought the main chives/contact form goes to the HEROP Slack? Then there is a Resource Guide submission form, and a data submission form, which go to GoogleForms.

Pros for Google Script/Google: Shared google form repo where multiple groups can view/manage.

Cons: It's easy to miss, and not enough individuals are collectively co-viewing or co-managing. Missed a resource guide submission in the past because of that. For the general contact form, would agree that routing to the Slack of managing group is most efficient.

@Makosak Makosak added this to the Spring Tasks 2024 milestone Dec 20, 2023
@Makosak Makosak added the enhancement New feature or request label Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants