1 of 13

FALL 22:

UNIT 6 PROJECT WEEK

2 of 13

What are we building?

Example of projects

Project awards

Requirements and Features

Schedules Standups Next steps

Groups

TABLE OF CONTENTS

1

2

3

4

5

6

3 of 13

Groups

  • Ethan + Duojay
  • Shaina + Kristen
  • Fabrizio + Jackie
  • Daniel + Natalie
  • SJ + Nico
  • Arly + Clifford
  • Julian + Destiny
  • Nayan + Jah
  • Chuka + Luis
  • Casterly + Staceyann
  • Vinny + Gabe
  • Amanda + Trevon

4 of 13

What are we building?

Fellows, you will...

  • Have fun and build something that you feel proud to show off!
  • How? Combine your Unit 0-6 skills to create a more complex and in-depth project!

5 of 13

Examples of Projects

Consume (GET) and build upon interesting free APIs

    • no JSON server, you're not creating any data!

Mindful

  • A journaling app that uses a text analysis API to record your daily mood on a calendar

Meal Tracker

  • A meal tracking app that uses a nutrition API to record and calculate your calorie and nutrient intake for the day

Cozy Kitchen

  • A recipe app that helps you discover new recipes and jam out to a playlis

6 of 13

Unit 6 Project Week Awards!

This could be you!

For the first time in Marcy Lab School history we are going to have project week awards, voted on by you and the staff!

There will be awards for:

🏅 Fellows Choice (fellow voted)

🤩 Best Looking (staff voted)

🖼️ Best Presentation (Instructors)

Prize: TBD

7 of 13

Requirements

  • Professional look and feel
    • Your team must use a CSS Library!

  • At least one fetch call per team member
    • Each member must own at least one “fetch feature”

  • Complexity
    • Additional fetch calls, interactions between fetch calls, analysis of the data in a novel way

  • Stretch Goal
    • Use localStorage to store and persist user data

8 of 13

Owning a Fetch Feature

Each team member will be responsible for…

  • Planning:
    • Determining the URL endpoint to hit
    • Identifying an example call response and the data values to be used
    • Describing how that data will be presented to the user
  • Implementation:
    • Commit history shows that you've implemented these features using JavaScript, HTML, and CSS

9 of 13

Project Week Schedule

10 of 13

Group Standup

  • Your group will meet to update each other and to update your scrum board!

First standup:

  • Establish working relationships. What are you hoping to get out of the project? What are you hoping to learn? How do you want to communicate / work together?

Subsequent standup

  • Check in on team dynamic. What is working, what isn't?
  • Check in on individual contributions. Does everyone feel as though they are contributing equally? Where do you need help?

11 of 13

Schedule Changes and Due Dates

  • Project Proposals are due Sunday 3/26 at 9pm!
  • Project Presentation Slides are due Wed 3/29!
  • Projects must be deployed by Thursday 3/30 at 9pm!

12 of 13

    • On Canvas, read over Unit 6 Project Guidelines
    • Read the instructions for and start on the Unit 6 Project Proposal due on Sunday at 9pm

    • Identify APIs you want to build your project around.
    • Brainstorm how you can present that data in an interesting way.

Next Steps

13 of 13

Day-By-Day Tips

Day 1 - Project Planning

  • Identify APIs, assign feature ownership, create proposal,

Day 2 - Proof of concept + data collection

  • Create GitHub repo, set up files, create branches, test API with fetch calls, identify functions, minimal styling with CSS Library!

Day 3 - MVP

  • Implement DOM interactions > Fetching > DOM Manipulation

Day 4 - MVP + Style

  • Finalize functionality and advanced styling

Day 5 - Polish

  • Polish your styling and practice presentation