Sulu
Sulu ships 2.6 and 3.0 in lockstep, and the 3.0 line still reads like a maintenance branch.
A side-by-side editorial comparison of WPForms and Hugo — release velocity, themes, recent moves, and the top alternatives to consider.
WPForms fills its feed with tutorials while signposting a v2.0 it has not shipped here.
WPForms publishes on a near-daily tutorial cadence, and the entire visible window is instructional: connecting forms to Make.com and Slack, assembling an applicant tracker out of forms and entries, and separating confirmations from notifications. A retrospective post frames the recent stretch of releases as the road to WPForms v2.0, but the feed carries no release notes for it. What is visible is documentation of existing capability, not new capability.
Steady feature-then-patch cadence, with security reports rising because AI tools are finding them
Hugo is running its usual rhythm: a feature minor followed by a short run of patches. v0.164.0 added dark/light pairs for Chroma highlighter styles with matching flags on `hugo gen chromastyles`, new encoding.HexEncode, encoding.HexDecode and crypto.Hash template functions, an rst syntax-highlight option, Pandoc citation support, and sub-path support in layouts passed to Page.Render. Before it, v0.163.0 was largely a correction pass on the AVIF handling introduced in 0.162.0 — default quality dropped to 60 on the finding that JPEG and WebP at 75 are comparable, with per-format and per-image quality now configurable.
WPForms publishes on a near-daily tutorial cadence, and the entire visible window is instructional: connecting forms to Make.com and Slack, assembling an applicant tracker out of forms and entries, and separating confirmations from notifications. A retrospective post frames the recent stretch of releases as the road to WPForms v2.0, but the feed carries no release notes for it. What is visible is documentation of existing capability, not new capability.
The through-line across the tutorials is integration and routing — getting submissions out of WordPress and into the tools where work actually happens. Stacked with the v2.0 retrospective's claim that AI features have been accumulating quietly, the product is being positioned as a data-capture front end for other systems rather than a forms builder alone. The conversion-benchmarks post points the same way, toward measurement of what forms produce.
Given the v2.0 framing and the run of integration tutorials, the next substantive post is likely a v2.0 feature tour or another native integration walkthrough. The feed does not carry release notes, so any actual shipping detail will have to come from elsewhere.
Hugo is running its usual rhythm: a feature minor followed by a short run of patches. v0.164.0 added dark/light pairs for Chroma highlighter styles with matching flags on `hugo gen chromastyles`, new encoding.HexEncode, encoding.HexDecode and crypto.Hash template functions, an rst syntax-highlight option, Pandoc citation support, and sub-path support in layouts passed to Page.Render. Before it, v0.163.0 was largely a correction pass on the AVIF handling introduced in 0.162.0 — default quality dropped to 60 on the finding that JPEG and WebP at 75 are comparable, with per-format and per-image quality now configurable.
The work in this window is refinement rather than expansion: image encoding defaults tuned after real-world use, template function surface extended one primitive at a time, external converter behaviour standardized. The most notable observation comes from the maintainer in v0.163.1, who attributes a rise in security reports to new AI tooling being pointed at the codebase rather than to any decline in the code — and that release, plus the code-block language escaping fix in 0.163.3, is where those reports land.
The pattern across this window points to another patch run consolidating 0.164.0 before the next minor. If the reported uptick in AI-assisted security findings continues, more of those patches will be security-driven, as 0.163.1 already was.
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 WPForms or Hugo.
Sulu ships 2.6 and 3.0 in lockstep, and the 3.0 line still reads like a maintenance branch.
Nearly every release in this window carries security hardening — Pimcore is working through an injection sweep.
The v4 canary line is being renamed Build Awesome while 3.x is kept on pure maintenance.
Measurement gets granular while the API quietly opens ClickFunnels up to outside agents
n8n's daily patch train hides the real work: hardening its MCP server into a proper auth resource.
OneSignal is arguing a new category into existence before showing the product behind it.
See all WPForms 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. WPForms is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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. WPForms is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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 WPForms alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "WPForms alternatives" section above for the current picks, or visit /alternatives/wpforms 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.