whitenoise VS django-components

You can use whitenoise. https://github.com/evansd/whitenoise

We’ll use this library to serve our static admin files. I’m not going to go over all the configuration details here, but you can feel free follow them on your own. Make sure the static files are part of the Lambda package.

I'm trying to serve static files through WhiteNoise as per Heroku's recommendation. When I run collectstatic in my development environment, this happens:

Waitress - for serving your application easily (pairs very well with Whitenoise).

3) Caching static assets - both of static assets. So maybe try deploying a Django app in a production environment and cache the static assets. You could put them behind a service like Cloudflare which will take care of that for you, or have a look at something like [Whitenoise](https://github.com/evansd/whitenoise) which will add the correct HTTP headers for you. You can spend some time reading about HTTP Caching headers and even try writing a simple middleware which caches certain requests to your Django app (just for learning purposes).

FWIW, I always use Whitenoise to serve Static files when I use Heroku, and only keep Media files on AWS. It works well.

In the beginning of the project, I chose Google Cloud Platform as the "Cloud Provider". But for simplicity and easy to use I switched to WhiteNoise to serve staticfiles.

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/