About 'Wareg': Bringing Convenient, Healthy Meals to Modern Society
In today's fast-paced world, finding time for nutritious home-cooked meals can be challenging. "Wareg" is our solution: providing varied, healthy, and easy-to-access meals delivered right to your doorstep. We collaborate with nutritionists, use fresh local ingredients, and offer diverse menus, ensuring your meals are not just food, but a convenient and healthy lifestyle solution. Experience our service and feel the difference.
| Name | Role |
|---|---|
| Okky Anggoro | Frontend Developer & UI UX |
| Mesel Ghea | Frontend Developer & Backend Developer |
| Nofrialdi | Frontend Developer & Infra Engineer |
Live:
| Name | Role |
|---|---|
| Okky Anggoro | Frontend Developer & UI UX |
| Mesel Ghea | Frontend Developer & Backend Developer |
| Nofrialdi | Frontend Developer & Infra Engineer |
Live:
- http://api.wareg.site
- https://w17-our-backend-group-e-production-57d7.up.railway.app/
- https://our-backend-warteg.nofri.xyz/
Docker:
- https://hub.docker.com/r/nofrialdi/our-backend-warteg/tags
- https://asia-southeast2-docker.pkg.dev/our-backend-warteg/docker/our-backend-warteg
Repo : https://github.com/revou-fsse-1/w17-our-backend-group-e
Status : https://our-backend-group-e.betteruptime.com/
The table below gives an overview of the technologies used in this project, as well as places to learn more about them.
| Name | Links |
|---|---|
| Next.js | Website - Docs - Learn Next.js - GitHub - Wikipedia |
| React | Website - Docs - GitHub - Wikipedia |
| TypeScript | Website - Docs - GitHub - Wikipedia |
| Tailwind CSS | Website - Docs - GitHub Docs - GitHub |
| React Icons | Website - GitHub |
| ESLint | Website - Configuration - Rules - GitHub |
| Prettier | Website - Docs - Options - GitHub |
| Husky | Website - Docs - GitHub |
| lint-staged | Website - GitHub |
| pnpm | Website - Docs - GitHub |
| GitHub Actions | Website - Docs - Workflow syntax |
| Vercel | Website - Docs - CLI Docs |
| Next.js | Website - Docs - Learn Next.js - GitHub - Wikipedia |
| React | Website - Docs - GitHub - Wikipedia |
| TypeScript | Website - Docs - GitHub - Wikipedia |
| Tailwind CSS | Website - Docs - GitHub Docs - GitHub |
| React Icons | Website - GitHub |
| ESLint | Website - Configuration - Rules - GitHub |
| Prettier | Website - Docs - Options - GitHub |
| Husky | Website - Docs - GitHub |
| lint-staged | Website - GitHub |
| pnpm | Website - Docs - GitHub |
| GitHub Actions | Website - Docs - Workflow syntax |
| Vercel | Website - Docs - CLI Docs |
To get started, run:
pnpm devThe table below provides names and descriptions of the npm scripts available in this project.
Each script is run using pnpm <script-name>. For example: pnpm dev.
| Name | Description |
|---|---|
prepare |
The prepare life cycle script is used to set up Git pre-commit hooks when people install dependencies, eg. using npm install. This script should not be run manually. |
test |
Runs tests |
dev |
Runs the Next.js development server. |
build |
Generates a production build. |
start |
Runs the Next.js production server built using build script. |
lint |
Runs ESLint to catch linting errors in the source code. |
format |
Formats all source code in the project. |
format:check |
Checks the formatting of all code in the project. |
deploy:vercel |
Deploy a preview deployment to Vercel |
While our project has been a solid learning exercise and created a functional Web service, there are always ways to enhance and expand. Here are some areas for improvement:
- Firebase Integration: Although we planned to use Firebase for some authentication features, we have not fully implemented it yet. Completing this integration could provide a more seamless and secure authentication experience.
- Responsivenes: While our application layouts work well on small screens, they can be further optimized for larger screens. For instance, on wide screens, we could make better use of the available space by implementing a grid layout or multi-column layouts.
- Automated Tests: The implementation of automated testing would be beneficial. This would allow us to catch and resolve potential issues before they reach our users, and make our development process more efficient.
- Google Auth: Integrating Google authentication can significantly improve the user experience. This feature simplifies the sign-in process, making it more user-friendly, and adds an extra layer of security.
While our project has been a solid learning exercise and created a functional Web service, there are always ways to enhance and expand. Here are some areas for improvement:
- Firebase Integration: Although we planned to use Firebase for some authentication features, we have not fully implemented it yet. Completing this integration could provide a more seamless and secure authentication experience.
- Responsivenes: While our application layouts work well on small screens, they can be further optimized for larger screens. For instance, on wide screens, we could make better use of the available space by implementing a grid layout or multi-column layouts.
- Automated Tests: The implementation of automated testing would be beneficial. This would allow us to catch and resolve potential issues before they reach our users, and make our development process more efficient.
- Google Auth: Integrating Google authentication can significantly improve the user experience. This feature simplifies the sign-in process, making it more user-friendly, and adds an extra layer of security.
- Okky Anggoro
- Mesel Ghea
- Nofrialdi
