How ispc-soluciones/bienestar-plus works
Bienestar Plus is an integral-wellness web app. Users register or log in, then manage habits, exercise routines, hydration, sleep progress, nutrition plans and personal profiles; they can also browse health resources and receive notifications. The Angular UI routes requests through feature services to a Django REST backend, which handles domain logic and persistence. The README documents meditation and breathing exercises, personalized reminders, progress statistics and authentication. Some backend routes and storage details are unsampled, so those connections are omitted or marked unverified.
Main entry points: views.py API views · app.routes.ts App routes · services Wellness services · plan-nutricional.ts Nutrition plan
Components 22
User experience
- App routes
frontend/src/app/app.routes.ts - Registration
frontend/src/app/pages/registro/registro.ts - Login
frontend/src/app/pages/login/login.ts
Wellness features
- Habits
frontend/src/app/pages/habitos/habitos.ts - Profile
frontend/src/app/pages/perfil/perfil.ts - Nutrition plan
frontend/src/app/pages/plan-nutricional/plan-nutricional.ts - Wellness services
frontend/src/app/services - Domain models
frontend/src/app/models
Backend API
- API routing
backend/bienestar_plus_api/urls.py - API views
backend/bienestar/views.py - Hydration API
backend/bienestar/hydration_views.py - Nutrition API
backend/bienestar/nutrition_views.py - Serializers
backend/bienestar/serializers.py - Domain records
backend/bienestar/models.py - Mongo storage
backend/bienestar/mongo.py
Content and notifications
- News service
backend/bienestar/services/news.py - Resource service
frontend/src/app/services/recursos.service.ts - Notifications
frontend/src/app/services/notificaciones.ts - Notification socket
backend/bienestar/consumers.py - Email service
backend/bienestar/services/email.py
Other components
- User
- External news
Connections 26
- User → App routes: opens app
frontend/src/app/app.routes.ts - App routes → Registration: routes to
frontend/src/app/app.routes.ts - App routes → Login: routes to
frontend/src/app/app.routes.ts - App routes → Habits: routes to
frontend/src/app/app.routes.ts - App routes → Profile: routes to
frontend/src/app/app.routes.ts - Habits → Wellness services: uses
frontend/src/app/pages/habitos/habitos.ts - Profile → Wellness services: uses
frontend/src/app/pages/perfil/perfil.ts - Habits → Nutrition plan: renders
frontend/src/app/pages/habitos/habitos.ts - Profile → Nutrition plan: renders
frontend/src/app/pages/perfil/perfil.ts - Nutrition plan → Wellness services: uses
frontend/src/app/pages/plan-nutricional/plan-nutricional.ts - Nutrition plan → Domain models: uses
frontend/src/app/pages/plan-nutricional/plan-nutricional.ts - Registration → Login: uses auth
frontend/src/app/pages/registro/registro.ts - Login → Wellness services: uses
frontend/src/app/pages/login/login.ts - Resource service → External news: requests resources
- API routing → API views: routes requests
backend/bienestar_plus_api/urls.py - API views → Serializers: serializes
backend/bienestar/views.py - Serializers → Domain records: serializes records
backend/bienestar/serializers.py - API views → Domain records: reads and writes
backend/bienestar/views.py - API views → Mongo storage: stores files
backend/bienestar/views.py - API views → News service: gets news
backend/bienestar/views.py - API views → Email service: sends email
backend/bienestar/views.py - News service → External news: fetches articles
- Notifications → Notification socket: connects
- Hydration API → Domain records: persists hydration
- Nutrition API → Domain records: persists plans
- Wellness services → API routing: calls backend