Local-safe email capture
Email Capture Setup
This site is currently running on GitHub Pages, so the checklist form is intentionally in setup mode. It does not pretend to save subscribers until a real backend or form provider is connected.
Email capture is currently in setup mode
GitHub Pages cannot write new form submissions into data/subscribers.csv on its own. The current form uses a mailto fallback and the local CSV is prepared for future imports or provider exports.
Option A: Formspree
Use Formspree for a simple hosted endpoint, then export subscribers into your local workflow. Do not hard-code private keys in the static site.
Option B: Google Forms
Embed or link to a Google Form if you want the lowest-maintenance setup. This is not as branded, but it is simple and reliable.
Option C: Netlify Forms
If the site later moves to Netlify, Netlify Forms can capture submissions without building a custom backend.
Recommended next step
Keep the current local-safe mode until you choose a provider. Then update config/email_capture.json with the provider name and replace the mailto action with the provider endpoint.
FAQ
Can GitHub Pages save emails directly?
No. GitHub Pages serves static files, so it cannot write directly to data/subscribers.csv without a backend or form provider.
What does the current form do?
The form is in setup mode. It uses a mailto fallback so readers can contact you while a real provider is not connected yet.
What should be integrated later?
Simple options include Formspree, Google Forms, ConvertKit, Mailchimp, or Netlify Forms if the site later moves to Netlify.
CTA
Use this page as the setup note before enabling real subscriber storage.
Contact the site owner