How jfilby/nexus works
Main Components
a. Core Framework Components:
• Command Line Interface (nexus)
• Model Generation System
• Web Framework
• Database Layer
• Authentication System
b. Module Structure:
• Core Module
• Core Extras Module
• CRM Module
• Social Module
┌─ Application Layer ─────────────────────────────────────┐
• Web Apps / Console Apps │
• (Generated from conf/*/web_apps/) │
• ┘
• ↑ ↑ ↑
┌─ Framework Modules ──────────────────────────────────────┐
• ┌─────────┐ ┌──────────┐ ┌─────┐ ┌──────────┐ │
• Core │ │ Core │ │ CRM │ │ Social │ │
• Module │ │ Extras │ │ │ │ Module │ │
• ┘ └──────────┘ └─────┘ └──────────┘ │
• ┘
• ↑ ↑ ↑
┌─ Services Layer ───────────────────────────────────────┐
• Authentication | Email | Scheduled Tasks | Data Access │
• ┘
• ↑ ↑ ↑
┌─ Data Layer ──────────────────────────────────────────┐
• ORM | Model Generation | Database Access │
• ┘
Component Relationships
• Data flow between components
• Dependencies between modules
• Generation paths for code artifacts
Special Elements
a. Code Generation Pipeline:
• YAML Model Definitions → Generated Nim Types
• Route Definitions → Generated Controllers
• Database Schema Generation
b. Authentication Flow:
• User Sessions
• JWT Handling
• Role-based Access Control
Implementation Details
Implementation features:
• Cached vs. Uncached Data Access
• Model Type Generation
• View Generation
• Route Generation
• Multiple layers and grouping
• Clear text labels
• Export to common formats
Remember to include the database schema generation and ORM functionality as these are central to the framework's operation, but keep them at an appropriate level of abstraction.