HTMX is neutral to composability, since it's limited to connecting and orchestrating parts of a system that may or may not chose to provide components. Does yo

HTMX is neutral to composability, since it's limited to connecting and orchestrating parts of a system that may or may not chose to provide components. Does your backend has components? Does your scripting toolkit has components? HTMX doesn't care either way, and will use whatever you give it. You can pick reusable django forms, alpine js, some manually created boundaries, a jquery module... You can even drop react on a single page because there is a widget you like and it's not loaded often. People may be tempted to talk about HTMX using irrelevant points of references. It's not providing an SPA with a component architecture, that's the point. The readers that are very used to modern JS stacks and never had to deal with the web before 2010 may want to read: https://www.bitecode.dev/p/a-little-taste-of-htmx-part-1 https://www.bitecode.dev/p/a-little-taste-of-htmx-part-1 This will give a better idea of how to think in HTMX, which is just a new trick for an old dog. It's better to use this tool for what it is, with its limits and strengths rather than trying to make it into something it's not. The reason HTMX can't do many things react is good at is because it's by nature the opposite of react.