How jllorencetti/pets works
Main Components
a. Frontend Layer:
• Static content (CSS, JS, images) in /static
• Template system with layouts and partials in /templates
• Separate template directories for each app component
b. Backend Layer (Django Apps):
• Main apps:
• meupet (core pet functionality)
• users (user management)
• cities (location management)
• common (shared functionality)
• api (REST API interface)
c. External Services:
• Social Authentication (Facebook, Twitter)
• SendGrid (Email service)
• Database (PostgreSQL)
• Media Storage (for pet images)
Architecture Pattern Representation
System following Django's MVT (Model-View-Template) pattern:
[Client Browser] ←→ [Django URLs/Views] ←→ [Models] ←→ [Database]
• ↑
• → [Templates] ←→ [Static Files]
Component Relationships
• User authentication flow through social providers
• Image processing pipeline (upload → easy-thumbnails processing)
• Database interactions
• API endpoints communication
• Email notification system
Specific Elements
a. Core Features:
• Pet registration system
• User management
• Location services
• Image handling
• Search functionality
• Social media integration
b. Supporting Services:
• Email notifications
• Social authentication
• Image processing
• API endpoints
Detailed Component Breakdown
Subcomponents for each main app:
meupet/
• Models (Pet, Photo)
• Views (registration, search, status updates)
• Forms
• Services (Facebook sharing, image processing)
users/
• Models (OwnerProfile)
• Authentication
• Social Integration
cities/
• Models (City, State)
• Location Services
Data Flow Indicators
• User request flow
• Authentication processes
• Database operations
• External service communications
• Media handling