How quinnkwolter/modulearn works
Main Components
A. External Systems Layer:
• Canvas LMS (with LTI 1.3 integration)
• External Content Authoring Tools
• PostgreSQL Database
B. Application Core (Django Apps):
• LTI Module (Authentication & Integration)
• Accounts Module (User Management)
• Courses Module (Content Management)
• Dashboard Module (User Interfaces)
• Main Module (Core Application)
[Client Tier]
• ↕
[Application Tier]
• ↕
[Data Tier]
Component Details
a) Client Tier:
• Canvas LMS Interface
• Standalone Web Interface
b) Application Tier (Core Components):
• Within this container, create separate modules for:
• LTI Handler (OAuth2, Grade Services)
• Course Management
• User Management
• Content Delivery
• Progress Tracking
• Internal communication paths between modules
c) Data Tier:
• PostgreSQL Database
• Cache Storage (for LTI data)
Interaction Flows
• LTI authentication flow
• Content delivery path
• Grade submission flow
• User session management
• Database interactions
Technical Details
• Django WSGI/ASGI Server
• Static File Handling
• Template Layer
• URL Routing System
• Model Relationships
Notes Section
Annotations for:
• Authentication flows
• Grade submission process
• Content delivery pipeline
• Progress tracking mechanism
Data flow for progress tracking and grading
Keep the abstraction level high enough to show the overall architecture while including sufficient detail to understand the key components and their interactions. Focus on showing how the different Django apps (accounts, courses, dashboard, lti, main) interact with each other and external systems.
Remember to highlight the scalability aspects and how the system handles different types of smart content through the modular architecture.