django-components VS django-ninja

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/

Django Ninja [1], it forever changed how I write Django project, in a way so elegant and productive.

[1]: https://django-ninja.dev/

Django Ninja is a RESTful wrapper for Django, while UtilMeta Python Framework uses a more concise declarative ORM Schema for Django and other future-supporting ORMs like sqlachemy and Peewee to build RESTful APIs more efficiently, and supports not only Django but all Python mainstream frameworks like Django, Flask, Starlette, FastAPI, Sanic, Tornado, etc.

I can't recommend [django-ninja](https://github.com/vitalik/django-ninja) enough. It's an easy to use, extremely fast, typed API for django. I've found it to be better in almost all aspects when compared to djangorestframework.

It's gaining popularity but is still widely unknown.

> The only place I really see Django at large companies is as an api using DRF or something.

This is not a bad thing. Using Django as an API backend is amazingly fast in terms of development time, especially with modern frameworks such as django-ninja [1].

Just use the built-in ORM to create models, write your endpoints, and use the built-in admin interface to play with the database if you don't have endpoints for everything.

There is also a less known feature of Django called admindocs [2], which automatically generates a human readable, hyperlinked documentation for your models and relations between them.

[1] https://django-ninja.rest-framework.com/

[2] https://docs.djangoproject.com/en/4.2/ref/contrib/admin/admi...

Personally, I also prefer django-ninja to DRF.

Actually that's not fully true. If you mix async and sync codes in django-ninja there will be some errors. Where's the proof ? django-ninja doesn't support async auth

Subscribe to this issue :D

Also recommend Django-Ninja. It basically reimplements fastapi's type and decorator-based API construction, but embedded directly in django so you have access to django's ORM and middleware library.