How patrykwitek/garden-design-app-.net-angular works
Main Components
Frontend Layer:
• Angular Application (TypeScript/JavaScript)
• Components Module
• Services Module
• Shared Components
• Models/Interfaces
• Assets (3D models, textures, translations)
• WebGL/ThreeJS Integration
Backend Layer:
• ASP.NET Core API
• Controllers
• Data Layer (Entity Framework Core)
• Services
• DTOs
• Middleware
• Authentication/Authorization
Database:
• SQLite Database (indicated by the presence of SQLite dependencies)
Key Architectural Elements
a) Client-Side (Frontend):
• Core Modules:
• * App Module
• * Shared Module
• * Components (Admin, Garden Tools, Navigation)
• Services:
• * Engine Service (3D rendering)
• * Garden Service
• * Project Service
• * User Service
• State Management:
• * User Authentication
• * Project Data
• * Garden Elements
b) Server-Side (Backend):
• API Controllers:
• * Projects
• * Login
• * Language
• * Solution
• Data Access:
• * Entity Framework Core
• * Repositories
• * Unit of Work Pattern
• Domain Entities:
• * User
• * Project
• * Garden Elements
• * Environment
Integration Points
Key interactions:
• JWT Authentication Flow
• API Endpoints Communication
• File Generation (PDF)
• 3D Model Loading
• Database Operations
Specific Implementation Details
Specialized components:
• 3D Visualization Engine:
• * ThreeJS Integration
• * Camera Controls
• * Element Manipulation
• Garden Design Tools:
• * Element Placement
• * Ground Management
• * Environment Settings
Top Layer: User Interface & Client Logic
Middle Layer: API & Business Logic
Bottom Layer: Data Storage & Persistence
Flow Indicators
Key flows:
• User authentication process
• Project creation/modification
• 3D model rendering pipeline
• PDF generation process
• Data persistence operations
The modular structure of both frontend and backend
This system design should reflect the application's focus on 3D garden design while showing how all components work together to provide the complete functionality described in the README.