Moodle Dev
Moodle is modernising its frontend stack while hardening the base institutions audit.
A side-by-side editorial comparison of Kajabi and Blockly — release velocity, themes, recent moves, and the top alternatives to consider.
Kajabi is building retention machinery around the community and the checkout.
Recent work clusters in three places. Payments: Instant Payouts, ACH Direct Debit for invoicing at lower processing fees, redesigned upsells and checkout label overrides. Community: a moderation set with a review feed, per-member post approval, hide and lock actions, bulk handling and a full audit log, plus translations covering interface, in-app notifications, email and push across six languages. Retention: cancellation reason tracking, and win-back targeting that filters contacts by previously owned or cancelling offers across campaigns, triggers and branches.
Blockly makes keyboard and screenreader access the default, not a plugin
This Blockly line shipped a major version in June that made the editor keyboard-navigable and screenreader-accessible by default, folding what had been the separate keyboard-navigation plugin into core and requiring custom blocks and fields to update their ARIA roles and labels. Everything since builds on that: a FOCUSABLE capability for components, paste placement near the focused block, added navigation shortcuts, an ARIA type-name method for fields, and translated field labels. The most recent releases are corrective, covering memory leaks, right-to-left rendering, and flyout behavior.
Recent work clusters in three places. Payments: Instant Payouts, ACH Direct Debit for invoicing at lower processing fees, redesigned upsells and checkout label overrides. Community: a moderation set with a review feed, per-member post approval, hide and lock actions, bulk handling and a full audit log, plus translations covering interface, in-app notifications, email and push across six languages. Retention: cancellation reason tracking, and win-back targeting that filters contacts by previously owned or cancelling offers across campaigns, triggers and branches.
The pattern is a platform moving from helping creators sell once to helping them keep members. Cancellation reasons and win-back campaigns are two halves of one loop — record why someone left, then address them as a segment — and the community investment treats the membership rather than the course as the unit being retained. The payments work points at higher-ticket invoiced sales rather than impulse checkout.
With cancellation reasons now collected, the natural next step is acting on them automatically — triggering a retention offer from the reason itself rather than leaving it in a report for someone to read.
This Blockly line shipped a major version in June that made the editor keyboard-navigable and screenreader-accessible by default, folding what had been the separate keyboard-navigation plugin into core and requiring custom blocks and fields to update their ARIA roles and labels. Everything since builds on that: a FOCUSABLE capability for components, paste placement near the focused block, added navigation shortcuts, an ARIA type-name method for fields, and translated field labels. The most recent releases are corrective, covering memory leaks, right-to-left rendering, and flyout behavior.
Accessibility has moved from an add-on to an architectural property of the editor, and the follow-on releases show what that costs: focus management, insertion markers, and field labeling all had to be reworked around it. The insertion marker rewrite is a good marker of the pattern, framed as a performance change but motivated by memory leaks in the focus-aware rendering path. Translation of field labels extends the same reasoning from assistive technology to language.
Expect continued hardening of the focus and navigation paths rather than new editor capability, since that is where every release since 13.0.0 has concentrated. The RTL and memory-leak fixes suggest the accessible rendering path is still settling.
Other EdTech 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 Kajabi or Blockly.
Moodle is modernising its frontend stack while hardening the base institutions audit.
This feed is Kahoot's press room, so it tracks partnerships, not product.
Thinkific's teaching assistant grows into a storefront recommender.
Processing is shipping again — and quietly moved its renderer onto wgpu.
Gemini in Classroom drops its age gate and starts reading the assignment you are on.
LifterLMS wired its REST surface into WordPress's new Abilities API.
See all Kajabi alternatives → · See all Blockly alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Blockly is currently shipping more aggressively (velocity 5.0 vs 0.0), 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. Blockly is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other EdTech products to evaluate alongside.
Top Kajabi alternatives in EdTech are ranked by recent ship velocity. Browse the "Kajabi alternatives" section above for the current picks, or visit /alternatives/kajabi for the full list with editorial commentary on each.
Top Blockly alternatives in EdTech are ranked by recent ship velocity. Browse the "Blockly alternatives" section above for the current picks, or visit /alternatives/blockly for the full list with editorial commentary on each.