django-components VS django-tables2

The same can be said of a React frontend that talks to a JSON API. There is some structure, organization, and convention to the API endpoints, one-way data flow, and so on. Otherwise it’s chaos.

On our most recent project we do the same with Django and HTMX. Organized endpoints by component. Composable, reusable server-side components with django-components [1]. And we’ve been orders of magnitude more productive, shipping more in 1-2 months than we did the previous 12-18 months working with React.

[1] https://github.com/EmilStenstrom/django-components

Yes. Or django-components

I use django-components to break templates into very small pieces, and never had any of the issues you describe.

I've been reading about django-components and #slippers components, but don't know about combining Pre or PostCSS, Tailwind or XXX for styling and how to keep the whole thing as simple to maintain as possible. Not willing to go the Bootstrap route, but need to structure a compromise.

I had used this project for creating components https://github.com/EmilStenstrom/django-components/

Also, for simpler cases I include partial templates.

In React it is as simple Django with https://github.com/EmilStenstrom/django-components installed {% component_block "button" intent="primary" %} Now everyone using Django would have to create their own components, they also have to do this in React which is a waste.

I felt the ux around registering new components to be much stronger with https://github.com/EmilStenstrom/django-components although I do like how slippers uses attributes

That said, you might find this package interesting: https://github.com/EmilStenstrom/django-components/

How does this compare to https://github.com/jieter/django-tables2? That one makes it really easy to display database models with column sorting and pagination.

The degree of reusability (Thanks to things like GenericForeignKey and the ubiquity of Django Templates and Django ORM, there are tons of reusable components like django-filter or django-tables)

In Django there is django-tables2 for example, that creates html table from database query.

(eg. "Django apps" like django-filter and django-tables2, which rely on being a slice across the ORM, controller layer, and templating engine.)

From the readthedocs tutorial, A few examples:

I don't see how Axum would enable something like django-tables2 or django-filter which has is vertically integrated with Django's ORM, routing layer, and template system.

I've used actix-web for stuff... but I'm just sick of constantly reinventing the rote boilerplate that things like django-tables2 and django-filter generate for me once I've declared whatever customizations I want.

django-tables2 - like crispy forms but for tables, abstracts away the need to render tables in a template.