Skip to content

build-week-foodie-fun/Project-Overview

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 

Repository files navigation

Foodie-Fun-Lambda

The following project relates to the process known as Build Weeks at Lambda School. Students building apps together in teams to demonstrate your mastery over the material you have thus far learned at Lambda School, preparing you to enter the job force one project at a time.

Build Week Objectives

The Objectives for an effective build week are:

  • Allow each student to demonstrate their proficiency across the objectives learned over the last Unit at Lambda School.
  • Prepare each student in their respective section to develop a firm understanding of how Lambda Labs operates.
  • Provide students with as many opportunities as possible to learn what it's like to develop software in a real world environment.
  • Provide students time to develop at least 5 projects worthy of professional portfolio during their time at Lambda School.
  • Encourage cross section and cross course collaboration amongst our student body.

Project Overview

MVP Feature Breakdown:

Login/Signup Pages

User can login into an existing account with Username and Password and a Phone Number or a user can sign up for an account with a username and password and phone number.

Home Page

On login a user is sent to a list view page where they can see a list of plants.

Edit User Profile

User can change their username and phone number

Plant Page

User can create a watering schedule for a plant by adding a plant type/name + species name, watering schedule.

Delete Plant Schedule Page

User can delete a plant from their watering schedule.

Notifications

When it's time for a plant to be watered user will receive text notifications through Twilio sent to their phone number provided on sign up.

Deployment:

Recommend to deploy your server to Heroku, and your front end to netlify. Both services provide free tiers and easy to use interfaces.

It is recommended that you keep your front end and backend codebases in separate GitHub repositories.

Technical Design Document

View Only: TDD

Resources

Notion links:

Policies and Procedures

Build Week Schedule and Daily Milestones

Git Workflow

Roles:

Web User Interface Developer Role

Front End Architect Role

Backend Architect Role

iOS Developer Role

Team Leader Role

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published