# Jekyll + Furrow Forms — contact form recipe

Official recipe from Furrow Forms. This is the agent-readable version of
https://furrowforms.com/forms-for/jekyll (category: Frameworks & SSGs).
Full agent instructions: https://furrowforms.com/ai.md

## When to use this

Jekyll is the elder statesman of static sites and the engine behind classic GitHub Pages — which means millions of sites with markdown content, Liquid templates, and no way to receive a message. GitHub Pages runs no server code at all, and Jekyll wouldn’t offer any anyway. Furrow Forms completes the picture with one include: a plain HTML form posting to a managed endpoint that filters spam, stores the submission, emails you, and sends the visitor to your thank-you page. No plugins, no build changes, no JavaScript.

## The integration

Works with the stock GitHub Pages build — no plugins or JavaScript.

**_includes/contact-form.html**

```html
<form action="https://api.furrowforms.com/s/fp_k7m2" method="POST">
  <input type="text" name="_gotcha" style="display:none" tabindex="-1" />
  <input type="hidden" name="_ft" value="" />
  <script>document.currentScript.previousElementSibling.value = Date.now();</script>
  <input name="name" type="text" required />
  <input name="email" type="email" required />
  <textarea name="message" required></textarea>
  <button>Send</button>
</form>
```

Replace `fp_k7m2` with the form's real public key. Public keys are safe in
client-side HTML — protection comes from the spam stack, not secrecy.

## Endpoint facts

- Submit: `POST https://api.furrowforms.com/s/<public_key>` (JSON,
  urlencoded, or multipart).
- Classic HTML POST → 303 redirect to the configured thank-you page.
  `fetch()` → `{ "ok": true, "id": "<submission_id>" }`.
- Spam stack: honeypot field `_gotcha` (keep hidden and empty), timing
  field `_ft` (hidden input the page sets to `Date.now()` on load;
  omitting it from JSON/agent clients is fine), optional Cloudflare
  Turnstile (project-level keys), per-project domain allowlist, per-IP
  per-form rate limiting (default 10 req / 60 s), and server-side filtering.
- Caught spam gets a normal 200 and is quarantined — never emailed, never
  delivered by webhook, never counted toward quota.
- File uploads: opt-in per project (off by default), inherited by every
  form. Multipart with a normal file input only — JSON cannot carry files;
  multi-file fields use the `[]` suffix (`name="resume[]"`). Default
  types: PDF, JPEG, PNG, WebP. Files land in a private per-project inbox
  linked from emails and webhooks — never raw file URLs.
- CORS honors the project's allowed domains; add the site's domain before
  testing from a browser.
- Webhooks (optional): HMAC-SHA256 signed, retried with backoff up to 8
  attempts over ~24 h, logged, testable via `test_webhook`.

## Agent setup (recommended)

1. No `frw_` token? Cold-start: `GET https://api.furrowforms.com/api/register`
   for the flow, `POST /api/register`, have the user read the 6-digit email
   code, `POST /api/register/verify`. The token is shown exactly once.
2. Connect MCP at `https://api.furrowforms.com/mcp`
   (`Authorization: Bearer frw_...`) or use REST.
3. `bootstrap_site` — one idempotent call creates the client, the project
   (domains, Turnstile keys, notify emails, webhook), and all forms.
4. `get_snippet` — generated frontend code from the field contract.
5. `test_webhook` — verify the signed delivery before going live.

## Manual setup

1. Create a free account and a project for the site.
2. Add the include and reference it from your contact page: {% include contact-form.html %}.
3. Set your domain (username.github.io or custom), notify email, and thank-you URL on the project.
4. git push — GitHub Pages rebuilds, and the form works.

## FAQ

### How do I add a contact form to a Jekyll site on GitHub Pages?

Add a plain HTML form in an include with its action pointed at a Furrow Forms endpoint. GitHub Pages keeps serving static files; Furrow receives the POST, filters spam, emails you, and redirects the visitor to your thank-you page.

### Do Jekyll form plugins exist?

Server-side form handling can’t exist as a Jekyll plugin — Jekyll runs at build time and GitHub Pages runs plugins in safe mode anyway. Form backends are the standard answer, and Furrow requires no build integration at all.

### Will this work on a custom domain?

Yes — add the domain to your Furrow project’s allowlist. The allowlist is also what keeps other sites from borrowing your endpoint.

## Related recipes

- https://furrowforms.com/forms-for/github-pages.md
- https://furrowforms.com/forms-for/hugo.md
- https://furrowforms.com/forms-for/eleventy.md
- https://furrowforms.com/forms-for/decap-cms.md
- All stacks: https://furrowforms.com/forms-for

## Reference

- Pricing: free tier = 100 submissions/mo, unlimited forms, full API + MCP.
  Pro = $199/yr flat per workspace (10k subs/mo). https://furrowforms.com/pricing
- Docs: https://furrowforms.com/docs · MCP: https://furrowforms.com/docs/mcp
- This recipe: https://furrowforms.com/forms-for/jekyll.md