this is why the amount of work for a htmx + rest framework library is not really much. The only thing I'd hope to see is a content negotiator that is responsive to the

Hx-Request

header (i.e., it returns a partial page for htmx and something else for normal requests), and a revamp of the browsable renderer where the something else returned for normal requests is a UI component explorer thing (alongside a BrowsableAPI data view). Everything else in terms of content negotiation, rendering, and the API a library user would interact with is already there in DRF. So, my vision for the library is just to drop-in a content-negotiator class and a render class that is a UI component explorer; quite minimal