mirror of
https://github.com/pacnpal/thrillwiki_django_no_react.git
synced 2025-12-21 18:11:08 -05:00
Enhance static files management guidelines: clarify directory structure, file management rules, and benefits of separation for better adherence to Django best practices
This commit is contained in:
@@ -21,6 +21,23 @@
|
||||
- Implement component-based structure
|
||||
- Follow progressive enhancement
|
||||
|
||||
### Static Files Organization
|
||||
1. Directory Structure
|
||||
- `static/` - Source static files (CSS, JS, images, etc.)
|
||||
- `staticfiles/` - Collected files (generated by collectstatic)
|
||||
|
||||
2. File Management Rules
|
||||
- Place all source static files in `static/` directory
|
||||
- Never directly modify `staticfiles/` directory
|
||||
- Use Django's `static` template tag for references
|
||||
- Run collectstatic before deployment
|
||||
|
||||
3. Benefits of Separation
|
||||
- Clear distinction between source and compiled files
|
||||
- Prevents confusion in development vs production
|
||||
- Follows Django best practices
|
||||
- Simplifies deployment process
|
||||
|
||||
## Design Patterns
|
||||
|
||||
### Data Access
|
||||
|
||||
Reference in New Issue
Block a user