Resources and Notes

Version state, reading list, and how this connects to theok.

Version state (verified October 2026)

LineStatusNotes
1.xmaintainedserved at v1.htmx.org for IE11 support; migration guide at htmx.org/migration-guide-htmx-1
2.xstable, current2.0.11 (package.json on master; docs CDN pin). <hx-partial> server-sent swap commands are already documented and implemented here (src/htmx.js:2004)
4.0beta onlynewest tag v4.0.0-beta6; no stable release. Plans in the-fetchening.md: promoted <htmx-partial> tag, streaming support, OOB simplifying toward plain id replacement

Write against 2.x today; the 4.0 ideas to watch are streaming and the partial-tag promotion, both extensions of what 2.x already does.

Essays worth reading

All in the repo mirror:

The essays index lives at essays/ (or htmx.org/essays). The docs intro also links a quirks page - a short list of browser and htmx edge cases worth one read before shipping.

theok relevance

htmx is the interactivity layer candidate for the Go-native rendering path:

  • templ integration: templ has first-class fragment support for exactly this style - @templ.Fragment("name") marks a subsection, and a handler with templ.WithFragments("name") renders just that fragment while a handler without it renders the whole page, which is the HX-Request branch in template form. See _repos/a-h-templ/docs/docs/03-syntax-and-usage/19-fragments.md.
  • What htmx would replace: the client-side React islands (share actions, load-more, player controls) become server-rendered fragments swapped by attributes - the patterns in Common Patterns map directly.
  • Pre-reading before a spike: the Next.js port essay above plus the 10-tips essay. Together they cover the migration mechanics and the server-structure conventions that make an HDA maintainable.

Related topics: templ, Go