|
1 |
| -# voyage-tasks |
| 1 | +# Schedulicious |
| 2 | + |
| 3 | + The Menu Scheduler is a manual scheduling tool that enables managers to create and share weekly menus with staff. It simplifies communication by providing clear meal plans and accounting for dietary restrictions and allergies. |
| 4 | + |
| 5 | +## 🚀 Getting Started |
| 6 | + |
| 7 | +### Prerequisites |
| 8 | +- Node.js (v18 or higher) |
| 9 | +- Yarn |
| 10 | + |
| 11 | +### Development |
| 12 | + |
| 13 | +#### Install Dependencies |
| 14 | +```bash |
| 15 | +yarn install |
| 16 | +``` |
| 17 | + |
| 18 | +#### Start Development Server |
| 19 | +```bash |
| 20 | +yarn dev |
| 21 | +``` |
| 22 | +## 📖 Development Guide |
| 23 | + |
| 24 | +### Git Workflow |
| 25 | + |
| 26 | +**Branch Structure:** |
| 27 | +``` |
| 28 | +main ← release PR ← dev ← PR ← feature/bug branches |
| 29 | +``` |
| 30 | + |
| 31 | +**Steps:** |
| 32 | +1. Create branch from `dev` |
| 33 | +```bash |
| 34 | +git checkout dev |
| 35 | +git pull origin dev |
| 36 | +git checkout -b feature/your-feature |
| 37 | +``` |
| 38 | + |
| 39 | +2. Push changes & create PR to `dev` |
| 40 | +```bash |
| 41 | +git push origin feature/your-feature |
| 42 | +``` |
| 43 | + |
| 44 | +3. After PR approval & merge: |
| 45 | + - Delete feature branch |
| 46 | + - Changes go to `main` via release PRs |
| 47 | + |
| 48 | +### Commit Messages |
| 49 | +Format: `[type]: message` |
| 50 | + |
| 51 | +Types: |
| 52 | +- `feat`: New features |
| 53 | +- `fix`: Bug fixes |
| 54 | +- `docs`: Documentation |
| 55 | +- `style`: Formatting |
| 56 | +- `refactor`: Code restructuring |
| 57 | +- `test`: Tests |
| 58 | +- `chore`: Maintenance |
| 59 | + |
| 60 | +Examples: |
| 61 | +```bash |
| 62 | +feat: add calendar component |
| 63 | +fix: resolve date picker bug |
| 64 | +docs: update setup guide |
| 65 | +``` |
| 66 | + |
| 67 | +## Our Team |
| 68 | + |
| 69 | +- Chloe Zhou #1: [GitHub](https://github.com/xyzhou-projects) / [LinkedIn](https://www.linkedin.com/in/xyzhou-developer) |
| 70 | +- Nurul Mukhlisa #2: [GitHub](https://github.com/numulaa) / [LinkedIn](https://www.linkedin.com/in/nurul-mukhlisa/) |
| 71 | + |
| 72 | + ... |
| 73 | + |
| 74 | +- Teammate name #n: [GitHub](https://github.com/ghaccountname) / [LinkedIn](https://linkedin.com/in/liaccountname) |
| 75 | + |
| 76 | +--- |
| 77 | +## Original Documentation |
2 | 78 |
|
3 | 79 | Your project's `readme` is as important to success as your code. For
|
4 | 80 | this reason you should put as much care into its creation and maintenance
|
@@ -26,17 +102,3 @@ Meeting Agenda templates (located in the `/docs` directory in this repo):
|
26 | 102 | - Meeting - App Vision & Feature Planning --> ./docs/meeting-vision_and_feature_planning.docx
|
27 | 103 | - Meeting - Sprint Retrospective, Review, and Planning --> ./docs/meeting-sprint_retrospective_review_and_planning.docx
|
28 | 104 | - Meeting - Sprint Open Topic Session --> ./docs/meeting-sprint_open_topic_session.docx
|
29 |
| - |
30 |
| -## Our Team |
31 |
| - |
32 |
| -Everyone on your team should add their name along with a link to their GitHub |
33 |
| -& optionally their LinkedIn profiles below. Do this in Sprint #1 to validate |
34 |
| -your repo access and to practice PR'ing with your team _before_ you start |
35 |
| -coding! |
36 |
| - |
37 |
| -- Chloe Zhou #1: [GitHub](https://github.com/xyzhou-projects) / [LinkedIn](https://www.linkedin.com/in/xyzhou-developer) |
38 |
| -- Nurul Mukhlisa #2: [GitHub](https://github.com/numulaa) / [LinkedIn](https://www.linkedin.com/in/nurul-mukhlisa/) |
39 |
| - |
40 |
| - ... |
41 |
| - |
42 |
| -- Teammate name #n: [GitHub](https://github.com/ghaccountname) / [LinkedIn](https://linkedin.com/in/liaccountname) |
|
0 commit comments