Buttondown
Buttondown ships small fixes daily, most of them the quiet-failure kind that lose subscribers.
A side-by-side editorial comparison of AWeber and Joomla — release velocity, themes, recent moves, and the top alternatives to consider.
AWeber is moving the console out of the browser and into the chat window
AWeber ships small, user-visible features on a steady two-to-four-week rhythm, and the recent run is unusually coherent: automatic UTM tagging on every link, opens-and-clicks charts over the last 100 broadcasts, AI image editing inside the signup form builder, and visual inline form placement. The newest release puts AWeber in Claude's connector directory, so drafting a broadcast, adding subscribers, or pulling open and click rates happens in a conversation against live account data. The rest of the feed is search-oriented marketing education that carries no product change.
Three Joomla branches ship in lockstep, and the release notes are mostly checksums
Joomla is running three branches in parallel: 5.4.x as the LTS-style maintenance line, 6.1.x as the current series, and 6.2.0 in alpha. Releases arrive as paired release candidates — a 5.4.x RC and a 6.1.x RC hours apart — rather than as independent branch events. The GitHub release bodies are dominated by download tables and SHA-256 checksums, with the actual merged-PR list buried at the very end, so the user-visible change in any given tag is hard to read off the notes.
AWeber ships small, user-visible features on a steady two-to-four-week rhythm, and the recent run is unusually coherent: automatic UTM tagging on every link, opens-and-clicks charts over the last 100 broadcasts, AI image editing inside the signup form builder, and visual inline form placement. The newest release puts AWeber in Claude's connector directory, so drafting a broadcast, adding subscribers, or pulling open and click rates happens in a conversation against live account data. The rest of the feed is search-oriented marketing education that carries no product change.
Two threads run through this window and they are converging. One is measurement — UTM tagging, engagement charts, outlier comparison — building a record of what each send actually did. The other is generation, where the AI builders moved from producing forms to editing the images inside them. The Claude connector is what makes the pair useful without the app open: the analysis surface and the authoring surface both become things you ask for rather than navigate to.
The connector's surface should widen from broadcasts and subscriber lookups toward the automation and landing-page objects the AI builders already create. Whether AWeber treats chat as a companion to the console or as the primary interface is not something these entries settle.
Joomla is running three branches in parallel: 5.4.x as the LTS-style maintenance line, 6.1.x as the current series, and 6.2.0 in alpha. Releases arrive as paired release candidates — a 5.4.x RC and a 6.1.x RC hours apart — rather than as independent branch events. The GitHub release bodies are dominated by download tables and SHA-256 checksums, with the actual merged-PR list buried at the very end, so the user-visible change in any given tag is hard to read off the notes.
The paired-RC cadence is now the shape of this feed: 6.1.3-rc1/5.4.8-rc1 on 11 August, then 6.1.3-rc2/5.4.8-rc2 on 15 August, each pair covering the same backported fixes across both branches. The PR tails show maintenance work rather than feature work — path-traversal checks in com_templates, a division-by-zero fix in subforms, date and time input validation, Smart Search memory limits — which is what a double-branch patch train looks like. 6.2.0 has not advanced past Alpha 3 since 21 July, so the near-term energy is entirely in patch stabilization.
Expect 5.4.8 and 6.1.3 to reach final within days of each other, following the same paired pattern the 5.4.7/6.1.2 finals took on 8 July. Whether 6.2.0 moves to beta before that is not visible in these entries.
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 AWeber or Joomla.
Buttondown ships small fixes daily, most of them the quiet-failure kind that lose subscribers.
Customer.io spent the summer pushing messaging off the screen and into location, time, and the lock screen
Gumloop is building the enterprise floor under an agent it now ships pre-assembled
Customer.io is turning messaging context — location, knowledge, carriers — into platform primitives
Four release trains running at once, and the top of the feed is all patch traffic.
OneSignal's release notes are buried under a competitor-comparison content engine.
See all AWeber alternatives → · See all Joomla alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. AWeber is currently shipping more aggressively (velocity 6.3 vs 5.0), 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. AWeber is currently shipping more aggressively (velocity 6.3 vs 5.0), 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 AWeber alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "AWeber alternatives" section above for the current picks, or visit /alternatives/aweber for the full list with editorial commentary on each.
Top Joomla alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Joomla alternatives" section above for the current picks, or visit /alternatives/joomla for the full list with editorial commentary on each.