django-tailwind-cli
Tailwind CSS for Django without Node.js. The library downloads the standalone Tailwind CSS CLI and wires it into Django management commands, so there is no npm, no webpack, and no separate build tool to configure. It follows the approach of the Tailwind integration for Phoenix.
What it does
- Downloads and manages the Tailwind CLI binary for your platform
- Rebuilds CSS on change, running under Django's own auto-reloader
- Produces minified production builds containing only the classes you use
- Includes the CSS via a
{% tailwind_css %}template tag - Supports DaisyUI through tailwindcss-cli-extra
- Targets Tailwind CSS 4.x
Quickstart
In an existing Django project, install the package:
python -m pip install django-tailwind-cli
Add the app and a static files directory to settings.py:
INSTALLED_APPS = [
# ... your other apps
"django_tailwind_cli",
]
STATICFILES_DIRS = [BASE_DIR / "assets"]
Create that directory before starting Django:
mkdir -p assets
Load the template tag in your base template and place it inside <head>:
{% load tailwind_cli %}
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>My Django App</title>
{% tailwind_css %}
</head>
<body>
{% block content %}{% endblock %}
</body>
</html>
Start Django and the Tailwind watcher together:
python manage.py tailwind runserver
The first run downloads the CLI and creates the default source CSS. Add Tailwind classes to your templates; the watcher rebuilds the stylesheet when you save them.
For a production build, run Tailwind before collecting static files:
python manage.py tailwind build
python manage.py collectstatic --noinput
See the installation guide for setup checks and optional integrations, and the workflow guide for custom CSS, editor setup and troubleshooting.
Requirements
- Python: 3.10+
- Django: 4.2 LTS, 5.2, 6.0, or 6.1
- Platform: Windows, macOS, Linux (automatic platform detection)
Configuration and commands
The defaults work with the setup above. Optional settings let you pin the Tailwind version, use a system binary, add custom CSS, enable DaisyUI, or include editable-installed external apps. See the settings reference.
The command reference covers all commands and options. To inspect your setup or investigate a build problem, start with:
python manage.py tailwind config
python manage.py tailwind build --verbose
python manage.py tailwind troubleshoot
Documentation and related projects
- Full documentation
- Tailwind CSS documentation
- DaisyUI components
- tailwindcss-cli-extra — the DaisyUI-enabled CLI build
- Django Extensions — provides
runserver_plus - Tailwind CSS IntelliSense — VS Code extension
- Django Commons
Contributing
Contributions are welcome.
CONTRIBUTING.md
covers the development setup (mise provisions Python, uv, and
pre-commit), how to run the tests, and what a pull request should look like. Please read the short
section at the top of it before opening an issue or a pull request — it explains what makes one easy
to act on.
License
This software is licensed under MIT license.
Metadata
Release files for django-tailwind-cli 4.8.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django_tailwind_cli-4.8.2.tar.gz | 165.5 kB | With provenance | Details for django_tailwind_cli-4.8.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_tailwind_cli-4.8.2-py3-none-any.whl | Python 3 | none | any | Details for django_tailwind_cli-4.8.2-py3-none-any.whl |
Total release size: 216.2 kB
Release files / django_tailwind_cli-4.8.2.tar.gz
| Download URL | django_tailwind_cli-4.8.2.tar.gz |
|---|---|
| Size | 165.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ef2455e491ab9f2686af26f2cd2491ae24ed4c2957e82ac0d75265bb469a2d1
|
|
BLAKE2b-256 checksum How to use checksums |
774e014cad8b6b66f021025383d93998f86e722b8735770cd7c06c8284b9669d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / django_tailwind_cli-4.8.2-py3-none-any.whl
| Download URL | django_tailwind_cli-4.8.2-py3-none-any.whl |
|---|---|
| Size | 50.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
42d4ead7efb1b1fec92c82ef49c1426a72ef369f87f2d76a25eead42cb6634ea
|
|
BLAKE2b-256 checksum How to use checksums |
db7e1c79351b909a5f39c0b03b783d5d56e54e1e7482ea81f90f6b80746a8d4e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logSecurity for django-tailwind-cli 4.8.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for django_tailwind_cli-4.8.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.