GetResponse
GetResponse keeps removing the setup step between connecting a store and sending to it.
A side-by-side editorial comparison of Formidable Forms and Hugo — release velocity, themes, recent moves, and the top alternatives to consider.
The forms plugin just opened its data to AI agents, and the next release goes back to search and calculations.
Formidable Forms ships the core plugin and its add-ons on separate version lines, and the last month covers both. The headline move is Forms API v2.0, which added an MCP adapter and WordPress Abilities API support alongside API key scoping and constant-time comparison. Core v6.34 follows with search over repeater and embedded form entry data, shortcode filtering for math calculations, and before/after input settings on scale fields. Security fixes run through the add-on line, including a Wordfence-credited signature deletion issue.
Hugo's releases are almost entirely asset pipeline work now: AVIF, Chroma, and import resolution.
Hugo's recent line is dominated by the asset pipeline and the markup layer rather than the site model. 0.165.0 adds css.ChromaStyles for generating highlighter stylesheets and an importContext option that makes in-memory resources resolvable from CSS @import statements across css.Build, js.Build, css.Sass, css.PostCSS and css.TailwindCSS. The releases before it tuned AVIF encoding defaults, added dark/light Chroma pairs, and closed a batch of security reports in the file and URL handling.
Formidable Forms ships the core plugin and its add-ons on separate version lines, and the last month covers both. The headline move is Forms API v2.0, which added an MCP adapter and WordPress Abilities API support alongside API key scoping and constant-time comparison. Core v6.34 follows with search over repeater and embedded form entry data, shortcode filtering for math calculations, and before/after input settings on scale fields. Security fixes run through the add-on line, including a Wordfence-credited signature deletion issue.
Two threads run in parallel. One is agent access: the Abilities API and MCP work makes form data readable and writable by AI clients through WordPress's own emerging standard rather than a bespoke bridge. The other is steady depth in the builder itself — entry search reaching nested data, calculation inputs getting guardrails — which is where most releases still land. Security hardening is continuous across add-ons rather than batched, suggesting an active disclosure pipeline.
Expect the agent surface to extend from the API add-on into the products that hold the data, with Views or entry management becoming reachable through the same Abilities API path. The builder line will likely keep shipping incremental field and calculation refinements on its usual cadence.
Hugo's recent line is dominated by the asset pipeline and the markup layer rather than the site model. 0.165.0 adds css.ChromaStyles for generating highlighter stylesheets and an importContext option that makes in-memory resources resolvable from CSS @import statements across css.Build, js.Build, css.Sass, css.PostCSS and css.TailwindCSS. The releases before it tuned AVIF encoding defaults, added dark/light Chroma pairs, and closed a batch of security reports in the file and URL handling.
The through-line is making Hugo's build pipeline self-sufficient — resources generated at build time can now feed the CSS and JS bundlers directly, and highlighter themes are generated rather than vendored. In parallel the project keeps tightening its security model: 0.163.1 normalized integer IPv4 host encodings and dropped symlinks from the os.* template functions, and 0.165.0 removes tailwindcss from the default security.exec.allow list, moving toward explicit opt-in for external binaries.
Expect the importContext mechanism to spread to the remaining resource transformers and further deprecations to land, given resources.PostProcess was already deprecated in favor of templates.Defer. Sites relying on the implicit tailwindcss exec permission will need to add it to their config explicitly.
Other Mkt Auto products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Formidable Forms or Hugo.
GetResponse keeps removing the setup step between connecting a store and sending to it.
Sender is filling out from a budget email tool into a fuller marketing platform, now reaching into transactional sends.
Four release branches shipping in parallel, and this window is all repair work.
A daily fix log where the editor and the archive absorb nearly every commit.
SegMetrics is cleaning up the inputs to attribution before selling more reports on top.
WPForms documents its own addons as tutorials; the feed is support content, not releases.
See all Formidable Forms alternatives → · See all Hugo alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Formidable Forms is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Formidable Forms is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Mkt Auto products to evaluate alongside.
Top Formidable Forms alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Formidable Forms alternatives" section above for the current picks, or visit /alternatives/formidable-forms for the full list with editorial commentary on each.
Top Hugo alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Hugo alternatives" section above for the current picks, or visit /alternatives/hugo for the full list with editorial commentary on each.