I'd love to help you with documentation and such; hit me up at [email protected] if you'd like a partner(:
[1] https://github.com/tvst/htbuilder
EDIT: Actually, scrolling further in this thread, it looks like https://htpy.dev fits the bill? It has explicit integration with Django, which is what I was looking for.
It’s modeled after Django templates circa 2005, and that was designed with an idea that designers will write those templates, that they are not code.
I’m doing all this for 18 years, it was always programmers who wrote template code.
Why then we have such things as filters, in addition to functions? Untyped macros. Formatting template code is a struggle. Include tags are the worst.
The only thing I fear with regard to all these component libraries is performance. I actually wrote a PoC myself for such a library, but didn’t bring it to production quality.
Components are overrated.
Their best feature is that they help build a fantastic ecosystem, which is the biggest react strength.
But for your own website?
Their cons and pros balance each other out, and all that is left is the terrible API that react exposes.
Eventually, you gain locally some reusability (provided you actually need it in your project, because there are not that many components that need reusability, and even less that couldn't be a template tag in django), but every single dev writes react code differently.
So you get a heterogeneous mess anyway.
My last SPA project (in vue), we had one component that was worth making reusable.
One. For a month and a half of work.
Turns out vanilla functions are quite reusable themselves already.
On the frontend, things are a little less consistent.
How does the performance side of this thing look like?
But it's fully django compact.
How is this next-gen? It looks exactly like all current frameworks in various languages, but with more default functionality thrown in.
Something like Postgrest would, to me, be "next-gen".
I have a private/proprietary backend-based framework that I used for a few clients that has both less "magic" while simultaneously allowing more functionality with even less code than any of the examples in any current framework, including this one.
I find it hard to get impressed these days.
I created a truly reusable Python component framework which is just a a string generation library and can be used for ANY existing Python web framework and even more: HTML, XML, RSS, SVG generation, even robots.txt generation as a silly example. I use it with Django and HTMX but it doesn't have an opinion about anything how should you use it. If you pass a Component to Django HttpResponse instead of a string or template, it just works.
I guess I should just write some documentation and release it before the 6th one of these appears :) so we ALL can collaborate with the same API on a bunch of Component sets like Twitter Bootstrap or Material components!
https://github.com/kissgyorgy/compone