How cthadeusantos/makemake works
Main System Components
a) Frontend Layer:
• HTML templates (located in each app's templates directory)
• Static assets (CSS, JavaScript, images)
• Client-side interactions (especially the JS files in various apps)
b) Backend Layer:
• Django Apps (multiple modular components):
• Core (base functionality)
• Projects
• Agreements
• Budgets
• Buildings
• Categories
• Companies
• Compositions
• Documents
• Prices
• Units
• Imports
c) Database Layer:
• Models from each app (as evidenced by models.py files)
• Relationships between different entities (reference the ER Model in documentation)
Architectural Patterns to Highlight
a) Django's MVT (Model-View-Template) architecture:
• Models: Data structure (models.py in each app)
• Views: Business logic (views.py in each app)
• Templates: Presentation layer (templates directories)
b) Modular Design:
• How each Django app is self-contained with its own MVC components
• Inter-app communications and dependencies
Specific Implementation Details
Key elements:
a) Authentication & Authorization:
• User management through Django's auth system
• Profile management (profiles app)
b) Data Flow:
• How projects flow through different components:
• Project creation → Agreements → Budgets → Payments
• Price and composition management flow
• Document management system
Technical Specifications
a) Technology Stack:
• Python 3.10+
• Django 5.1
• JavaScript (ECMAScript 2018+)
• HTML5
• Database (as configured in settings.py)
Key Relationships to Highlight
Relationships between:
• Projects and Agreements
• Agreements and Budgets
• Compositions and Prices
• Documents and their versions
• Companies and their associated entities