OttoKit
OttoKit keeps widening its WordPress trigger surface one plugin at a time
A side-by-side editorial comparison of Buttondown and Hugo — release velocity, themes, recent moves, and the top alternatives to consider.
Buttondown ships almost daily, and most of it is someone else's bug report closed.
The changelog is a near-daily log of two to four items, overwhelmingly fixes, many crediting the customer who reported them by name. The editor accounts for a disproportionate share — pasted Word documents locking it, cursors that would not sit between stacked tables, blank lines above tables that could not be deleted. Feature work is smaller and steadier: multi-select subscribe form fields, a searchable font specimen panel, Bluesky link cards that re-sync themselves.
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.
The changelog is a near-daily log of two to four items, overwhelmingly fixes, many crediting the customer who reported them by name. The editor accounts for a disproportionate share — pasted Word documents locking it, cursors that would not sit between stacked tables, blank lines above tables that could not be deleted. Feature work is smaller and steadier: multi-select subscribe form fields, a searchable font specimen panel, Bluesky link cards that re-sync themselves.
The pattern is a small team working a public queue in the open, and the fixes cluster where newsletter software actually breaks: rich-text editing, subscriber state transitions, and cross-posting to social platforms. Several recent items concern silent failures specifically — automations skipping sends without saying so, cross-posts marked failed after publishing, resubscribes quietly changing subscriber state. Correcting quiet-wrong behaviour into loud-correct behaviour is the through-line, and it matters more in a product where a mistake reaches someone's whole list.
Expect the cadence to hold and the editor to keep generating items, since that is where the reported bugs concentrate. The entries are day-stamped batches, so individual releases carry no version or theme to read direction from.
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 Buttondown or Hugo.
OttoKit keeps widening its WordPress trigger surface one plugin at a time
Craft 6's alphas keep converting the plugin API, one removal at a time
Two security releases ship the same day, and 6.2 finally clears alpha
Flodesk just moved its analytics out of the dashboard and into Claude and ChatGPT.
Formidable widens MCP compatibility and locks down signature files
Mailtrap is assembling a full email operations platform, one category step at a time
See all Buttondown 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. Buttondown 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. Buttondown 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 Buttondown alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Buttondown alternatives" section above for the current picks, or visit /alternatives/buttondown 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.