use Airtable to store studio data

Will be easier to maintain versus MongoDB rn, and won't require mode code to develop editing interfaces.

a lot of the fetching code can be lifted from dtr-mdb2airtable

some tables that we should have:

Social structures
- People: names, roles, project(s) they are on, sig membership
- SIGs
- Committees: include head and members
Venues
- SIGs
- Mysore/Office Hours (need to support different office hour times for each proj)
- Studio
Tools
- Sprint log
- Research canvases
- LIP signup
- Pair Research
Processes/events
- Status Updates: dates + projects/people signed up (in the future, we can use this to schedule it during the first DTR class)
- Sprints
- Events: things like open house, interview day, etc.

Navigation Menu