How danielthatu47/connectingngo works
Project Type Analysis
This is a Django web application focused on user authentication and management, with social login integration. It's a monolithic application following Django's MVT (Model-View-Template) architecture.
Main Components
A. Client Layer:
• Web Browser
• Static Files (CSS, JavaScript, Media)
B. Application Layer:
• Django Web Server
• Authentication System
• User Management Module
• Social Authentication (GitHub, Google)
• Media Handler
C. Data Layer:
• Database (Django ORM)
• File Storage (Media files, PDFs, Images)
Top Layer (Client):
┌─────────────────────────────────────────┐
• Web Browser / Frontend │
• (Bootstrap-based Templates) │
• ┘
• ↕ HTTP/HTTPS
Middle Layer (Application):
┌─────────────────────────────────────────┐
• Django Application Server │
• ┬──────────────┬───────────┤
• User Auth │ Profile │ Media │
• Module │ Management │ Handler │
• ┴──────────────┴───────────┤
• Social Authentication Services │
• (GitHub, Google) │
• ┘
• ↕
Bottom Layer (Data):
┌─────────────────────┐ ┌──────────────┐
• Database │ │ File Storage │
• User Data │ │ - Avatars │
• Profile Info │ │ - PDFs │
• NGO Data │ │ - Images │
• ┘ └──────────────┘
Key Components Detail
A. Templates Layer (users/templates/):
• Major template groups (auth, profile, NGO)
• Static file serving
B. Views Layer (users/views.py):
• Authentication views
• Profile management
• NGO management
• Payment handling
C. Models Layer (users/models.py):
• Profile model
• NGO model
• Related data structures
D. Media Handling:
• Separate paths for different media types
• PDF and image storage
Important Architectural Elements
• Django's built-in authentication system
• Custom user profile extension
• Social authentication integration
• Media file handling system
• Payment integration (as indicated by payment.html)
• Password reset flow
• Admin interface