Formspree Setup for Email Capture
Review notes, pricing checks, alternatives, and buyer-fit signals.
Open guideLocal-safe email capture
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.
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.
Use Formspree for a simple hosted endpoint, then export subscribers into your local workflow. Do not hard-code private keys in the static site.
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.
If the site later moves to Netlify, Netlify Forms can capture submissions without building a custom backend.
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.
Metrics are based on public content activity and are updated monthly. They are not website visitor claims.
No. GitHub Pages serves static files, so it cannot write directly to data/subscribers.csv without a backend or form provider.
The form is in setup mode. It uses a mailto fallback so readers can contact you while a real provider is not connected yet.
Simple options include Formspree, Google Forms, ConvertKit, Mailchimp, or Netlify Forms if the site later moves to Netlify.
Use this page as the setup note before enabling real subscriber storage.
Contact the site owner