TL;DR: Polyform now has comprehensive documentation at polyform.to/docs. It covers everything from creating your first form to setting up conditional logic, integrations, scoring, and team collaboration.
#What's covered
The docs are organized into six sections:
#Getting Started
- Introduction — what Polyform is and who it's for
- Quickstart — create your first form in under a minute
- Creating Forms — start with AI, a template, or from scratch
#Building Forms
- Builder — the visual editor and how to use it
- Question Types — all available question types with examples
- Theming — colors, fonts, logos, and animated backgrounds
#Logic & Scoring
- Flow — conditional branching and skip logic
- Recall — reference previous answers in later questions
- Scoring — point values, score-based routing, quiz setup
- Final Pages — customize end screens and create multiple endings
#Responses
- Summary — dashboard overview of form performance
- Responses — viewing, searching, and exporting submissions
- Settings — form behavior, access control, and scheduling
#Integrations
- Webhooks — send data to custom endpoints
- Slack — real-time submission notifications
- Zapier — connect to 8,000+ apps
- Email Notifications — inbox alerts for new submissions
#Team & Billing
- Team Members — invite and manage collaborators
- Billing — plans, trials, and subscription management
#Why we wrote docs
We noticed support questions clustering around the same topics — conditional logic setup, scoring configuration, and integration wiring. Docs solve that by giving users a self-serve reference that's searchable, linkable, and always up to date.
Every doc page includes SEO metadata and structured data, so they're discoverable via search too.
#Keeping docs current
The docs live alongside the product code in the same repository. When we ship a feature, updating the docs is part of the same workflow. This keeps documentation from drifting out of sync with the product.
#Read the docs
Start at polyform.to/docs or jump to any section from the navigation.