Team Cookbook
Our project aims to be an adaptive digital cookbook in which people can add their own recipes and make modifications and comments to other people’s recipes.
The Home Page will be a cover for our digital cookbook, we will ask users to login and sign up before they add things to the cookbook so that we can track additions and modifications by different people.
Profile adjustments -
Product information and blogging.
Inventory and Accounting
Trio 1 / Home Page, User Profile, API Request to Venmo
(assistant scrum master), BLOG
Integration and Branching strategy, APIs and Database changes
Bailey Leeder (scrummer #1), BLOG
Home Page of Site and design, JavaScript code to update user profile and order updates
Joanna Hu (scrummer #2), BLOG
APIs and Database for orders. User blogging and satisfaction on products.
Lalita Narayanan(Assistant to Scrum Master), BLOG
Assists scrum master with backend SQLalchemy data definition and initialization while also working with my trio on APIs for orders and feedback
Trio 2 / Product Page
Yuva Bala (scrum master), BLOG
Kanban Board, backend SQLalchemy data definition and initialization
Nathan (scrummer #3), BLOG
API's and methods for Adding Products, Administrative UI to support product adds, inventory updates.
Ahmad Imran (scrummer #4), BLOG
Figma Designs for site, API's and methods. API's and methods to show Sale History, Administrative UI to show sales.
Next Steps
[-] Clone + share repositories
[-] Make a home page
[-]
What we’ve planned to do so far: Team Cookbook
Social media site where you can post your own recipes to public cookbook
Input ingredients in a provided format
Take the ingredients to make an “ai” system where other users can put what ingredients they have and we will provide already posted recipes with similar ingredients
These r some notes cause he gathered us for a quick lesson today in class about connecting frontend/ backend and authenticate
Inspect:
Jwt cookie and authenticate (boolean)
Token:
jsaw and web token
Use chatgpt to code this token
When logout, token disappears
3 big files that are very important! Are key to token login/ logout stuff, study these files
Home.html
Header.html
login.js
Body tags: body of webpage, all content under “content” or “github pages”
Under home.html
Header.html:
Call Login js
Login js loads the page, git credentials, fetch
Returns data from api point (can see in console.log in inspect)
Home.html:
Submenu code, now wrapping it into logic so it’s conditional (sometimes shows, sometimes doesn’t show)
Doesn’t use if statement,
Goes to authenticate, if true then removes css (display none), then the html will display the submenu (only if authenticated)
This looks like notes from lecture and not much on plans. Only one statement about ingredients to make a recipe. That is not very logical to me as an approach to make further comments.
Joanna, Bailey, Yuva, Nathan, Ahmad, Lalita
Team Cookbook Our project aims to be an adaptive digital cookbook in which people can add their own recipes and make modifications and comments to other people’s recipes.
GitHub IO link is working: _ Frontend repo: https://github.com//flocker_frontend Backend repo: https://github.com/___/flocker_backend
The Home Page will be a cover for our digital cookbook, we will ask users to login and sign up before they add things to the cookbook so that we can track additions and modifications by different people. Profile adjustments - Product information and blogging. Inventory and Accounting
Trio 1 / Home Page, User Profile, API Request to Venmo (assistant scrum master), BLOG Integration and Branching strategy, APIs and Database changes Bailey Leeder (scrummer #1), BLOG Home Page of Site and design, JavaScript code to update user profile and order updates Joanna Hu (scrummer #2), BLOG APIs and Database for orders. User blogging and satisfaction on products. Lalita Narayanan(Assistant to Scrum Master), BLOG Assists scrum master with backend SQLalchemy data definition and initialization while also working with my trio on APIs for orders and feedback
Trio 2 / Product Page Yuva Bala (scrum master), BLOG Kanban Board, backend SQLalchemy data definition and initialization Nathan (scrummer #3), BLOG API's and methods for Adding Products, Administrative UI to support product adds, inventory updates. Ahmad Imran (scrummer #4), BLOG Figma Designs for site, API's and methods. API's and methods to show Sale History, Administrative UI to show sales.
Next Steps
[-] Clone + share repositories [-] Make a home page [-]
What we’ve planned to do so far: Team Cookbook Social media site where you can post your own recipes to public cookbook Input ingredients in a provided format Take the ingredients to make an “ai” system where other users can put what ingredients they have and we will provide already posted recipes with similar ingredients
These r some notes cause he gathered us for a quick lesson today in class about connecting frontend/ backend and authenticate
Inspect: Jwt cookie and authenticate (boolean)
Token: jsaw and web token Use chatgpt to code this token When logout, token disappears
3 big files that are very important! Are key to token login/ logout stuff, study these files Home.html Header.html login.js
Body tags: body of webpage, all content under “content” or “github pages” Under home.html
Header.html: Call Login js Login js loads the page, git credentials, fetch Returns data from api point (can see in console.log in inspect)
Home.html: Submenu code, now wrapping it into logic so it’s conditional (sometimes shows, sometimes doesn’t show) Doesn’t use if statement, Goes to authenticate, if true then removes css (display none), then the html will display the submenu (only if authenticated)