48 lines
		
	
	
		
			1.2 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			48 lines
		
	
	
		
			1.2 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
| =================
 | |
| Django Compressor
 | |
| =================
 | |
| 
 | |
| Compresses linked and inline JavaScript or CSS into a single cached file.
 | |
| 
 | |
| Why another static file combiner for Django?
 | |
| ============================================
 | |
| 
 | |
| Short version: None of them did exactly what I needed.
 | |
| 
 | |
| Long version:
 | |
| 
 | |
| **JS/CSS belong in the templates**
 | |
|   Every static combiner for Django I've seen makes you configure
 | |
|   your static files in your ``settings.py``. While that works, it doesn't make
 | |
|   sense. Static files are for display. And it's not even an option if your
 | |
|   settings are in completely different repositories and use different deploy
 | |
|   processes from the templates that depend on them.
 | |
| 
 | |
| **Flexibility**
 | |
|   Django Compressor doesn't care if different pages use different combinations
 | |
|   of statics. It doesn't care if you use inline scripts or styles. It doesn't
 | |
|   get in the way.
 | |
| 
 | |
| **Automatic regeneration and cache-foreverable generated output**
 | |
|   Statics are never stale and browsers can be told to cache the output forever.
 | |
| 
 | |
| **Full test suite**
 | |
|   I has one.
 | |
| 
 | |
| Contents
 | |
| ========
 | |
| 
 | |
| .. toctree::
 | |
|  :maxdepth: 2
 | |
| 
 | |
|  quickstart
 | |
|  usage
 | |
|  scenarios
 | |
|  settings
 | |
|  remote-storages
 | |
|  behind-the-scenes
 | |
|  jinja2
 | |
|  django-sekizai
 | |
|  contributing
 | |
|  changelog
 | 
