How ahmedy19/projects_library works
Project type and purpose
• This is a monolithic, server-rendered full-stack web application built with Django. Its purpose is to manage student projects: user accounts, project creation, tagging, dashboard statistics, etc.
File structure
• Top-level:
• core/: Django settings, URL dispatcher, ASGI/WSGI entry points
• accounts/, dashboard/, projects/: three Django “apps” handling authentication/profile, admin dashboard views, and project CRUD respectively
• templates/: global templates (base layouts, error pages, includes)
• static/ + staticfiles/: CSS, JS assets, fonts, images, uploads
• manage.py, requirements.txt, .env config, migrations
• Patterns:
• Django’s MVT (Models/Views/Templates) for each app
• Static asset pipeline collecting into staticfiles/
• Database migrations under each app
README
• Confirms Django + Pillow stack, local run steps, .env variables for secret key and DEBUG.
• No mention of external services (no caching, message queues, search engine).
Main components & their relationships
a. Frontend (Client browser)
• Requests HTML pages, CSS, JS, images from the Django server (or separate static‐file server/CDN).
b. Web Server / WSGI / ASGI
• Gunicorn or uWSGI sits in front of Django, handles HTTP, forwards to Django’s core/asgi.py or wsgi.py.
c. Django Application
• core (global settings, URL router)
• accounts app (auth, profiles, skills)
• projects app (project models, forms, views)
• dashboard app (aggregated views, admin‐style interface, statistics)
• Template engine renders HTML using templates under each app + global templates
• Staticfiles machinery (collectstatic) serves CSS/JS/images (optionally via WhiteNoise or CDN)
d. Database
• Relational DB (e.g., PostgreSQL, SQLite) storing Users, Profiles, Projects, Tags, Skills
e. Media storage
• File system or cloud storage for user uploads (project attachments, profile photos)
f. External Libraries
• Pillow for image processing
• Third-party JS/CSS libraries served as static assets
Architectural patterns & design principles
• MVT: each app defines Models for data, Views for request handling, Templates for presentation
• Single code-base with clear app boundaries; adhere to Django’s “loose coupling”
• Static asset separation: versioned JS/CSS under static/ and collected into staticfiles/ for production
• Environment-based settings (.env for secret key and DEBUG)