django-crispy-forms VS django-tables2

We start with an empty Django project which we call babelbox_project and an empty app called babelbox. We use the django-crispy-forms package to style our forms with Bootstrap.

django-crispy-forms - have to put this up again, amazing for rendering forms simply.

django-crispy-forms

Unless I'm misunderstanding the image/description, you only mentioned one field, phone_number, so I'm not exactly sure what you're wanting separated. In any case, are you using django-cirpsy-forms? You may want to give that a try, then following the advice from the article above you can customize your forms as you see fit with some easy bootstrap styling to boot:

Doc: https://django-crispy-forms.readthedocs.io/en/latest/ Source: https://github.com/django-crispy-forms/django-crispy-forms

Does this link help at all?

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.