Stand upright...
","Stand upright...
",https://youtube.com/...,https://img.youtube.com/...,slug-fr,slug-en,TYPE,STRENGTH 157,"Fentes arrières à la barre","Barbell Reverse Lunges","Stand upright...
","Stand upright...
",https://youtube.com/...,https://img.youtube.com/...,slug-fr,slug-en,PRIMARY_MUSCLE,QUADRICEPS ``` ### Available Attribute Types - **TYPE**: `STRENGTH`, `CARDIO`, `PLYOMETRICS`, `STRETCHING`, etc. - **PRIMARY_MUSCLE**: `QUADRICEPS`, `CHEST`, `BACK`, `SHOULDERS`, etc. - **SECONDARY_MUSCLE**: Secondary muscle groups targeted - **EQUIPMENT**: `BARBELL`, `DUMBBELL`, `BODYWEIGHT`, `MACHINE`, etc. - **MECHANICS_TYPE**: `COMPOUND`, `ISOLATION` ## Project Architecture This project follows **Feature-Sliced Design (FSD)** principles with Next.js App Router: src/ βββ app/ # Next.js pages, routes and layouts βββ processes/ # Business flows (multi-feature) βββ widgets/ # Composable UI with logic (Sidebar, Header) βββ features/ # Business units (auth, exercise-management) βββ entities/ # Domain entities (user, exercise, workout) βββ shared/ # Shared code (UI, lib, config, types) βββ styles/ # Global CSS, themes ### Architecture Principles - **Feature-driven**: Each feature is independent and reusable - **Clear domain isolation**: `shared` β `entities` β `features` β `widgets` β `app` - **Consistency**: Between business logic, UI, and data layers ### Example Feature Structure features/ βββ exercise-management/ βββ ui/ # UI components (ExerciseForm, ExerciseCard) βββ model/ # Hooks, state management (useExercises) βββ lib/ # Utilities (exercise-helpers) βββ api/ # Server actions or API calls ## Contributing We welcome contributions! Please see our [Contributing Guide](CONTRIBUTING.md) for details. ### Development Workflow 1. Fork the repository 2. Create a feature branch (`git checkout -b feature/amazing-feature`) 3. Make your changes 4. Commit your changes (`git commit -m 'feat: add amazing feature'`) 5. Push to the branch (`git push origin feature/amazing-feature`) 6. Open a Pull Request ### Code Style - Follow TypeScript best practices - Use Feature-Sliced Design architecture - Write meaningful commit messages - Add tests for new features ## Deployment ### Using Docker ```bash # Build the Docker image docker build -t workout-cool . # Run the container docker run -p 3000:3000 workout-cool ``` ### Manual Deployment ```bash # Build the application pnpm build # Run database migrations export DATABASE_URL="your-production-db-url" npx prisma migrate deploy # Start the production server pnpm start ``` ## Resources - [Feature-Sliced Design](https://feature-sliced.design/) - [Next.js Documentation](https://nextjs.org/docs) - [Prisma Documentation](https://www.prisma.io/docs/) - [Better Auth](https://github.com/better-auth/better-auth) ## License This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details. [](https://choosealicense.com/licenses/mit/) ## Support If you found this project helpful, consider: - β Starring the repository - π Reporting bugs - π‘ Suggesting new features - π€ Contributing to the codebase ---