How 747er/codyscapes works
Main Components
a) Frontend Layer:
• Static Content Delivery (HTML, CSS, JS)
• Three main application modules:
• Gallery Module
• Live Map Module
• Personal/About Module
• Template System (Django Templates)
b) Backend Layer:
• Django Web Framework
• URL Routing System
• Core Django Apps:
• Photos App (main photography functionality)
• Personal App (about/profile information)
• Blog App
• Gallery App
c) Data Layer:
• Database (SQLite in development, presumably PostgreSQL in production on Heroku)
• Static Files Storage (for images and assets)
[Client Layer]
• ↕
[Application Layer]
• ↕
[Data Layer]
Component Relationships
• HTTP/HTTPS requests between client and server
• Database queries between apps and database
• Static file serving paths
• Template rendering flow
Specific Implementation Details
Key architectural elements:
[Frontend Static Files]
• CSS (Bootstrap + Custom styles)
• JavaScript
• Images
[Django Apps]
• Photos (Main photography features)
• Personal (About/Profile pages)
• Blog
• Gallery
[Static File Handling]
• Development: Django staticfiles
• Production: Heroku static files
Specific Elements to Label
• URL routing paths
• Template inheritance relationships
• Static file serving paths
• Database relationships between models
• Admin interface access points
Implementation Notes
• Use standard UML notation where applicable
• Annotations for key configuration points
• Development vs production differences
• Security boundaries
The database schema relationships
Remember to maintain a balance between showing enough detail to understand the system while keeping it clear and readable. Focus on the photography-specific features while still showing the underlying Django architecture.