This repo contains everything you need to know about capstones - due dates, expectations, etc. Click on one of the links below to find out more.

• Deadlines
• Capstone Requirements
  • Technical Requirements
  • Planning
  • Documentation
  • Project NoNos
• Initial Proposal
• Mentor Checkins
• Demo Day Tips

• Capstone Planning - Week 22
• Capstone Coding - Weeks 23 - 24

• Week 20 (May 29) - Saturday: Initial Proposal Due (Use the Google form found on the initial proposal page) - please don't wait until the actual due date for this. Get it in this weekend before someone else takes your topic.
• Week 21 (June 1) - Tuesday: Project ERD AND if using an API, Postman Data Examples due - again get this to me ASAP so nobody needs to wait

• Week 22 (DUE: June 8) - Tuesday: 1-on-1s with mentor to determine MVP. (If you are able to get this in sooner, if approved, you can begin coding sooner)
  • Come prepared with: User stories, tickets, wireframes, personal biosite COMPLETED, and LOOM VIDEO due
  • SUBMIT HERE
• Week 23 (June 12) - Saturday: Coding begins - assuming your mentor is satisfied with your planning
• Week 24 (June 26) - Saturday: MVP is due - EVERY person will do a soft demo
• July 10 - FE Capstone Demos to E15 and E16

• React
• Firebase CRUD
• Bootstrap/Reactstrap/Styled Components
• Deployed Site (Firebase or Netlify)
• It is NOT required to use an external API.

• Use Github Projects for planning
• Create wireframes (use whatever tool you want - moqups, lucid charts, photoshop, adobe XD, Figma, etc.)
• If you are using an external API, gather all sample data and be prepared to demo your api at your first checkin (via Postman) before committing to use the API.
• If you have not fleshed out your planning enough, your capstone mentor will not let you code.

• A completed README with details and deployment link. Remember our planning from the beginning of the cohort.
• Also include the link to your deployed Personal Bio Site on the README.

• Projects shouldn't be something for your day job
• Projects shouldn't be for someone who will pay you 💰.
• No MVP can include a calendar
• No apps that require use of the spotify API.
• No recipe apps of ANY kind - they have all been done, they all look the same, there are no good free APIs.
• No games - there isn't enough time to make games for your capstone. Feel free to do one or 12 as a side project
• No game tracking applications - ie dashboards for DnD, WoW, etc
• No projects that are super similar to things we have done in class

During capstone time you will have 3 meetings with your mentor. These meetings are NOT a time for you to talk about broken code. They are a time to reflect on your progress and set easily attainable goals to make sure you will be finished with your project by the MVP deadline. Below is an outline of what you should have done before each check in:

• This is your first check in
• Purpose: to outline and agree on your capstone MVP.
• Preparation for this meeting:

1. Completed wireframes
2. A github project with your application planned out - cards written by feature, lots of detail in each card
3. Some sample JSON that matches your ERD - put this in a data ticket
4. A working API get request. If you plan to use another API you need to demonstrate the ability to connect to this API and return data back. Use the react-setup project we made. Add a component with an axios call to demonstrate that you are able to hit your API and return back the data you need. NO EXTENSIONS in time will be granted for this. If you do not have a working API call on this date then use of your API will be a stretch goal and not part of your MVP.

• At the end of this meeting you should have:

1. A list of your MVP goals
2. An ordered list of your stretch goals
3. A set of goals to complete by your next meeting

• This is your second check in
• Purpose: To make sure you are still on track for getting to MVP by Week 24 Saturday
• Preparation for this meeting:

1. Complete the coding goals from your first check in
2. Be prepared to talk about any difficulties you see coming up.

• At the end of this meeting you should have:

1. A good sense of if you are on track or need to work hard this week
2. A set of goals to complete by your next meeting.

• This is your final check in
• Purpose: To determine what (if any) remaining code you need to write to be at MVP for Saturday.
• Preparation for this meeting:

1. Complete the coding goals from your second check in
2. Be prepared to talk about any difficulties you see coming up.

• At the end of this meeting you should have:

1. A solid understanding of what you need to finish to be at MVP
2. A list of remaining things that need to be completed for your MVP demo on Saturday.