WS Form Pro over Fluent Forms Pro

Context

Original locked stack specified Fluent Forms Pro for forms. Fluent Forms is a popular budget choice — solid product at agency-friendly pricing. But form plugin choice has secondary implications for the data-model-first workflow we want.

Decision

Replace Fluent Forms Pro with WS Form Pro as the locked forms plugin for all NP clients.

Rationale

Best-in-class ACF integration. WS Form maps form submissions directly to ACF field groups. The pipeline becomes: form submission → ACF-typed field → custom post → structured content. This fits the productization workflow — every input becomes structured data without glue code.
ACSS-aware output. WS Form’s markup is framework-conscious in a way Fluent Forms’ isn’t. Cleaner integration with the ACSS class system.
Modern WordPress standards. REST API first, breakpoints baked in, semantic markup that reads more like hand-coded form HTML than the typical form-builder soup.
Etch / ACSS community alignment. WS Form is the form plugin the broader Etch+ACSS+ACF community has converged on for these reasons.

Trade-offs accepted

WS Form’s unlimited-sites tier is somewhat more expensive than Fluent Forms’ equivalent. Offset by better integration value and reduced glue code.
Smaller install base than Fluent Forms — fewer community resources, but the documentation is strong and the integration story compensates.

Consequences

Form-to-ACF binding becomes a core Phase 4 pattern. When designing CPT data models, forms are first-class inputs that round-trip to the same ACF field groups.
The locked stack documentation updates to reflect WS Form across all client onboarding artifacts.
License procurement: WS Form Pro Agency tier under Blackbyrd account.

stack/overview.mdx
decisions/2026-04-27-stack-foundation.mdx