How shalvirajpura2/sahyogi works
Project Type and Purpose
• This is a full-stack Django web application (“Sahyogi”) that connects volunteers, recruiters, and administrators in a social-impact platform.
• Backend: Django 4.2 (MTV pattern), SQLite3 database, Django’s authentication system.
File Structure
• Top level:
• manage.py (Django CLI entry point)
• volunteer_system/ (project settings, URLs, WSGI)
• accounts/ (Django app containing models, views, forms, migrations, admin)
• templates/ (HTML templates partitioned by role: admin, recruiter, volunteer, registration, plus base.html and shared layouts)
• Database schema evolves via accounts/migrations.
• URL routing: volunteer_system/urls.py delegates to accounts.views and built-in auth.
Extract Insights from README
• Three distinct user roles with role-specific dashboards and UIs.
• Core features: event creation & management, volunteer application workflows, impact tracking, community governance.
• Emphasis on MVC-like separation (models, templates, views/forms).
a. Main Components
1. Client Browser (Volunteer, Recruiter, Admin interfaces)
2. Web Server / WSGI Layer (Gunicorn or built-in dev server)
3. Django Application
• Presentation Layer: Templates + Bootstrap UI
• Logic Layer: accounts.views, forms, admin site
• Data Layer: accounts.models + Django ORM
4. SQLite Database
5. External Services (None in core; optionally SMTP for email, third-party analytics)
b. Relationships & Data Flow
• Browser ↔ HTTP requests/responses → Web Server ↔ WSGI → Django URL Router → View Functions
• Views ↔ ORM → SQLite
• Views → Render Templates → Browser
• Authentication subsystem intercepts login/signup routes
c. Architectural Patterns & Principles
• MTV (Model–Template–View) architecture
• Role-based access control (Volunteer/Recruiter/Admin) enforced via Django’s auth and view decorators
• Separation of concerns: accounts app handles all business logic, templates handle presentation
d. Key Technologies & Frameworks
• Django 4.2 (MTV, ORM, Authentication, Admin)
• Bootstrap 5 + HTML5/CSS3 (Responsive UI)
• SQLite3 (lightweight relational DB)
• Break the system into client, server, and data tiers.
• Drill into the server tier: show URL routing → views/forms → models → migrations → admin.
• Role-based modules and templates.
• Frameworks (Django, Bootstrap, ORM).