---
# System prepended metadata

title: Untitled

---

Schedule

---

### Bare minimum

* Set up - 1
* Set up database - 1
* Log in/ sign up/ log out - 1
* Create itinerary - 2
* View itineraries - 1
* View individual itinerary - 1

### Stretch
* My profile - 4
* Pop-up if signed in - 4
* 
---

## Schedule

--- 
## Week 1

Homework
Everyone create two itineraries
Rosie - create issues

---

Tuesday - Set up

Morning 
Stand up - 15 min
Set up repo
Database: discuss and design schema and set up

Afternoon
Deployment (database and website)

--- 

Wednesday - Authentication

*agreed on 01/06 to work on auth in morning and API in afti*

Morning

Stand up - 15 min
Research time - 1hr - React leaflet, database hosting, authentication method
Play with API query 

Afternoon

Authentication - log in/ log out

---

Thursday - Input data to database


Stand up - 15 min
View itinerary page
View individual itinerary

---

Week 2

Assumptions:
Finished log in and sign up - DONE(nearly)
Finished view all itineraries and view individual itinerary and displaying map in each of these (no points yet) NOT DONE(lol)

---

To do this week:
Priority - UX and CSS 
Add itinerary page (user)
Add points on map
Testing

---

## Monday
Stand up - 15 min

### Morning
Add env variable to Vercel (Antonio)
Database - change tables and input data - complete and push this - Evgeny and Rosie
Home page - tidying up - Saki and Antonio
Testing for home page

### Afternoon
View all itineraries page
Individual itineraries - dynamic routes

Sit down - 15 min

## Tuesday
Stand up - 15 min

### Morning
Cont. individual itineraries - dynamic routes
Complete view all itineraries page
Login/ signup pages

### Afternoon

User testing: 2-4pm

Sit down - 15 min

## Wednesday
Stand up - 15 min

### Morning
Login/sign up/ Logout
Testing

### Afternoon
Add itinerary page
Testing

Sit down - 15 min

## Thursday 
Stand up - 15 min

### Morning
Complete add itinerary page
Testing

### Afternoon
Tidying up
Testing 
Party

Sit down - 15 min

---


End of week 1 - re-scoping, new structure

Moscow method
must haves
should haves
could haves
wont haves

Need to sort into must haves, should haves (think are quite important)

make a board on github with those four columns

focus on proof of concept of product, not generic problems. Also, focus on prioritising problems that you want to solve for your own learning


Must Haves

Database
View all itineraries
View individual itineraries
Styling

Database - 1.5hr

- [ ] Add img column into itinieraties table and delete img_table, and alter map function
- [ ] Update everyones local database and Heroku database

Front page/ view all itineraries - 1 day

View individual itinerary - 1 day

Login/ signup - 1/2 day



Week 2 - Wednesday Stand Up

Re-evaluation of priorities.
Options:

* showing name when logged in - M
* log in button to log out button when logged in - M
* successful or unsucessful signup - setting message to let you know - M
* showing message when successfully logged in - M
* uploading image
* profile page
* react leaflet and geo-location





Additions for thursday afternoon:

Home button isn't clear - lets add to hamburger menu
