PLANNED · WPALLOY BUILD
Forms that feel native to the site they belong to.
WPAlloy Forms is planned as an accessible, performance-conscious application layer for form schemas, validation, submissions, notifications and integrations—designed to work naturally with MachAxis, Ready Sites and future automation.
The form belongs to the application layer—not the theme.
Schema & validation
Define fields, required state, validation rules and submission state through a structured forms model rather than theme-owned markup alone.
Submissions & notifications
Submission data and notification workflows remain owned by WPAlloy Forms or the selected forms provider so they survive design and theme changes.
Integrations
Conditional logic, multi-step flows, uploads, spam controls, CRM connections and webhooks belong in the forms application layer, not in MachAxis presentation code.
ACCESSIBLE BY DESIGN
A form should explain what it needs, what went wrong and what happened next.
- Real labels rather than placeholder-only fields
- Associated help and error text
- Clear required-state semantics
- Error summaries for complex forms
- Visible keyboard focus and predictable field order
- Accessible success and failure states
- Autocomplete and password-manager-safe behavior
- Form-state preview before publication
- Reduced-motion-aware interaction
- Design-token-aware contrast and spacing
One forms contract. Multiple design and workflow surfaces.
MachAxis is intended to provide the presentation layer—field styling, layout Recipes and interaction shells—while WPAlloy Forms owns the form application logic. A provider contract allows compatible forms to be placed into Starter Sites and Solution Packs without hard-coded provider shortcodes or unsafe markup rewriting.
Ready Sites
Starter patterns can provide a Form Slot that accepts a compatible form during onboarding.
Solution Packs
Vertical packages can combine industry-specific form structures with presentation, workflows and integrations.
Automation
Future AI and Agent workflows can draft or configure forms through provider APIs while preserving permissions and approval boundaries.
Privacy and conversion integrity stay explicit.
WPAlloy Forms should not turn a successful button click into a fake lead, silently expose submissions to AI, or bundle marketing surveillance into basic form rendering. Submission access, analytics and downstream automation require the appropriate authority and provider-owned completion signals.
- Form success comes from the authoritative forms provider
- AI access to raw submissions is separately permissioned
- Analytics and campaign behavior are separate capabilities
- Deactivation or cloud outage must not destroy form configuration or customer submissions
Planned, not yet available.
The final field catalogue, submission storage model, anti-spam stack, notification channels, provider integrations, Free/Pro packaging and release gates still require engineering and validation.