How wardxela/rwx works
Main Components
a) Frontend Layer (SolidJS Application):
• Client-side application structure
• Feature-based architecture (/features directory)
• Routing system with nested routes
• Integration with shared UI components
b) Backend Layer (NestJS Application):
• Modular architecture (auth, users, config modules)
• Authentication flow with Yandex strategy
• Session management
• Controller-service pattern
c) Database Layer:
• PostgreSQL database (evident from Prisma schema)
• Main entities and their relationships
• Migration management
d) Shared Packages:
• UI Component Library
• API client package
• Database access layer (Prisma)
• Tooling utilities
┌─────────────────────────────────────────────────────────────┐
• Client Layer │
• ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
• Routes │ │ Features │ │ Components │ │
• ┘ └─────────────┘ └─────────────┘ │
• ┬─────────────────────────────────┘
┌───────────────────────────┼─────────────────────────────────┐
• Shared Packages │
• ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
• UI │ │ API │ │ Tooling │ │
• ┘ └─────────────┘ └─────────────┘ │
• ┼─────────────────────────────────┘
┌───────────────────────────┼─────────────────────────────────┐
• Backend Layer │
• ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
• Auth │ │ Users │ │ Config │ │
• ┘ └─────────────┘ └─────────────┘ │
• ┼─────────────────────────────────┘
┌───────────────────────────┼─────────────────────────────────┐
• Database Layer │
• ┌─────────────┐ ┌─────────────┐ │
• Prisma │ │ Postgres │ │
• ┘ └─────────────┘ │
• ┘
Important Details
a) Frontend Details:
• Route structure: courses, blog, profile
• Feature modules: blog, categories, courses
• Shared components and utilities
b) Backend Details:
• Auth flow with Yandex integration
• User management system
• Configuration management
• Session handling
c) Database Details:
• Main entities from Prisma schema
• Migration management
• Relationship between services and database
Additional Elements
• Version information for major components
• External service integrations
• Development tools integration (CI/CD, testing)
Notes for Implementation
• Clear boundaries between packages
• Extensibility points for future features
• Environment configuration flow
Remember to maintain a balance between detail and clarity, focusing on the educational platform's core functionality while showing the technical architecture that supports it.