Forms

Forms are Chinaski’s builder for contact, signup, and lead forms, with submissions management, confirmation and admin emails, per-form webhooks, spam defenses, and privacy controls. Forms live in their own admin section, publish either at their own URL or embedded in built pages, and are documented across these pages:

• Fields and the form builder: field types, validation rules, conditional display, file uploads.
• Submissions: where answers go, rate limits, retention, and duplicate protection.
• Emails & webhooks: confirmation and notification emails, per-form signing webhooks.
• Spam & privacy: Turnstile, country blocking, honeypot, and data minimization switches.

Quick orientation

A form consists of three things:

1. The form: its name, URL slug (used both for its own address and its embed shortcode), publish status, and presentation settings (success message, redirect-to-thank-you page, submit button text/colors).
2. Its fields: an ordered list of typed, validated, optionally conditional fields.
3. Its handling: what happens on submit: store the submission (with retention), email people, fire a webhook.

Creating and publishing a form

• Standalone: with a slug set, the form is served at /forms/<slug> on the CMS. An inactive form returns 404 instead.
• Embedded in a page: put a [form:<slug>] shortcode in a page/post body. The builder renders the form inline at build time: the public output needs no CMS connectivity to show the form. If a referenced form isn’t available to the builder, the shortcode falls back to embedding the CMS-hosted form in an iframe (requires the CMS base URL to be configured).

Because the site is static, submissions POST straight back to the CMS server: the thing to check when moving hosting is that the CMS URL is reachable wherever the form is embedded.

Defaults that matter

Every new form starts with a sensible baseline: submissions are stored (no retention limit), the IP address is stored with each submission, webhook/email settings are blank, and Cloudflare Turnstile is enabled per-form (it only actually runs when Turnstile keys are configured site-wide). Each of these is adjustable on the form, including “don’t store IPs” and “delete submissions after N days”; see the linked subpages.

Where to manage submissions

Submitted entries are viewable and searchable in the admin Forms section, with per-form views and the ability to delete (which also cleans up any uploaded files belonging to those submissions). Rate limiting keeps a single visitor from flooding: 5 submissions to one form per hour, and 30 per hour total across all forms.

In this section

• Form Fields
• Form Submissions
• Form Emails & Webhooks
• Form Spam & Privacy