| Name |
Feature |
Research (link to blog) |
| Mati |
Image Api/AI Chatting |
Link |
| Orlando |
Person to Everyone messaging |
Link |
| Sheryas |
User to User messaging |
Link |
| Shivansh |
AI chatbot integration |
Link |
| Akshat |
Message history integration |
Link |
Put simply, assets that show a great collaboration and design.
Remember, you have several people each which will each have 5 hours of class time to contribute by the end of Checkpoint Part B.
Jupyter Notebook experiments. Perform research and learn how to work with some key technical elements using blogging and code fragment in Jupyter Notebooks.
Setup your repo and determine you methodology for managing code. Undoubtedly it should be based on Issues and Pull requests.
-
Backend Repo - Managed by Orlando, Issues made, Scrum board assigns people to issue, Each person works on their own branch, Push/pull to main according to scrum board and issue
-
Frontend Repo - Managed by Mati, Issues made, Scrum board assigns people to issue, Each person works on their own branch, Push/pull to main according to scrum board and issue
Refer to nighthawkcoders/teacher_portfolio#85
Put simply, assets that show a great collaboration and design.
Wireframe
Research (above)
Remember, you have several people each which will each have 5 hours of class time to contribute by the end of Checkpoint Part B.
Jupyter Notebook experiments. Perform research and learn how to work with some key technical elements using blogging and code fragment in Jupyter Notebooks.
Setup your repo and determine you methodology for managing code. Undoubtedly it should be based on Issues and Pull requests.
Backend Repo - Managed by Orlando, Issues made, Scrum board assigns people to issue, Each person works on their own branch, Push/pull to main according to scrum board and issue
Frontend Repo - Managed by Mati, Issues made, Scrum board assigns people to issue, Each person works on their own branch, Push/pull to main according to scrum board and issue
Refer to nighthawkcoders/teacher_portfolio#85