hx-pod

"We've done them all now"All headers grouped===========> REQUEST HEADERS======> Flags*HX-Boosted - was it a boosted link*HX-Request - is it an htmx request*HX-History-Restore-Request - is it a back button restore request======> Auto-sent variables*HX-Current-URL - current url page is at*HX-Target - id of target if has id*HX-Trigger-Name - which element triggered it by name*HX-Trigger - which element triggered it======> User Variables*HX-Prompt - user is asked to provide prompt, this is what they typed============> RESPONSE HEADERS======> Browser & history commands*HX-Location - hx-boost reload to page*HX-Redirect - regular redirect*HX-Refresh - refresh page*HX-Push-Url - push url to top bar*HX-Replace-Url - replace url in top bar======> override attributes*HX-Reswap - sets hx-swap value*HX-Retarget - set hx-target value*HX-Reselect - set hx-select value======> Trigger events*HX-Trigger - trigger an event on client immediately*HX-Trigger-After-Swap - trigger an event after swapping in html*HX-Trigger-After-Settle - trigger an event next lifecycle

Carson Gross, an expert in gonzo open source marketing, shares insights on bringing humor and positivity to social media. Alex Petros dives into the rise and fall of HTMX, providing a thought-provoking perspective. Ben Damman introduces Hypermedia Middleware with a focus on innovation. Meanwhile, Ryan Florence delivers a sharp critique of HTMX, sparking intriguing discussions. Nathaniel Maile and Jon-Michael Hartway co-present on the creative misuse of hypermedia, showcasing the playful side of tech development.

Use this response header to send event trigers to ANY client side browser event (javascript, htmx, custom, etc)HX-Trigger - as soon as response receivedHX-Trigger-After-Swap - after new html is swapped inHX-Trigger-After-Settle - after new html is settled and processed by browsersingle eventHX-Trigger:eventmultiple eventsHX-Trigger:event1, event2 single event with valueHX-Trigger:{“event1”:”event 1 message”} single events with key/value dataHX-Trigger:{“event1:{“key1”:”value1,”key2:”value2”}}multiple events with key/value data HX-Trigger:{“event1:{“key1”:”value1,”key2:”value2”}, “event2”:{“key1”:”value1,”key2:”value2”}}

{ "HX-Reselect": "#one-div-inside-html" }

This episode explores what an optimistic ui might look like in htmx. Also: is it what we want to do? Is it even possible? Or is it incompatible with the idea of having the dom as the true application state?Original tweet:https://x.com/noahflk/status/1795758603577545035DHH responses: https://x.com/dhh/status/1796163806650868149Htmx guy responses:https://x.com/htmx_org/status/1796182554883539236

{ "HX-Retarget": "#my-special-target" }

Override your "hx-swap=" attribute. Correct your hx-swap mistake! Do it now!!!

{ "HX-Refresh": "true" }

Decide from your server side what url the user sees!https://htmx.org/headers/hx-push-url

Speaking with a prolific developer who recently switched from React to htmx