Multiple apps using django-tailwind in the same project. about django-tailwind

[timonweb]

Hello, usually you don't need more than one tailwind app in a project. Once installed, it works for all your templates, regardless number of other apps you use. What's your case? I'm curious.

[Alpha249]

Well it's not a very interesting use case, its just that in the tutorials I have seen, its good practice to separate stuff like authentication in one app and other functionality in some other app.

Anyways, thanks for your response.

[timonweb]

@Alpha249 ok, I get it, but the Tailwind app works globally. You can use Tailwind classes across all your Django apps, as long as they belong to the Django project that has Tailwind installed.

[karimone]

For more complex projects, you need to create an app only for tailwind and share the tailwind config and CSS between different apps. This could be an issue if you have very different websites running on your project.

E.g.

src/
  data/
  domain/
  interfaces/
     restapi/
     appsite/
     frontendsite/
     supportsite/
     shared_tailwind/ <<< this is the app registered with tailwind

appsite, frontsite and supportsite are 3 different interfaces website served by the same project. shared_tailwind contains the tailwind stuff.

This seems to be a border case situation, but if you think about this already happens in most of the Django projects. The Django admin is completely different from the frontend app