So, DRF already has support for receiving and rendering html templates by passing a

template_name

kwarg to the drf

Response

constructor. Then, under the hood, drf has a content negotiation process which this library could hook into for determining what actually gets rendered based on the content_type and presence/absence of htmx headers