...
Michael’s idea would have to change many of the useContext variables.
ID for the timetable needs to be very unique, so that thinking for social timetabling, the ID can be shared to different users.
Still want Confirmed that we still want the timetables stored in Local Storage.