What if you don't want your page kept into the browser history local storage?

This is a somewhat open thought process looking at the question I see online: what is htmx good for?

Mentioned in the episode: the htmx movies example from Andrew Rhyand:
https://htmx.andrewrhyand.com/
A great looking page with smooth animations and educational htmx content on it.

Your browser has built in types and validation on inputs in a form. But what happens when you use inputs without a form??

Note: I accidentally posted an incomplete episode at first, if you dont hear the end, try to re-download!

Every request has secret hidden headers. But what if you wanted to make your own?

https://htmx.org/attributes/hx-headers/

When you make your life easier, that's a win.

Having any weird async ajax request issues? 

htmx got yer back 🤜 🤛

Push your ajax route to the url bar! Now you've got access to the back button again.

.. but what happens when you refresh?

Work with the browser history on any htmx request with hx-push-url and hx-replace-url.

PUSH it to the Browser history stack:
hx-get="/account/details" hx-push-url="true"

REPLACE the current browser history stack:
hx-get="/account/details" hx-replace-url="true"

Per listener request: Same episode as last, but without the soundtrack!

Keeping the other up for posterity's sake.

Every developer should have their own custom to-do app. Join me for my journey building this simple app in my head using htmx