#  Project #3: Group Project
#  Project #3:MEAN Stack - Group Project
## Overview
## Overview
For your 3rd project, you will be collaborating to make an application using Angular.
For your 3rd project, you will be collaborating to make an application using the MEAN stack.
Use your imagination! You get to create whatever you want for this app. Everyone will get a chance to **be creative**, and work through some really **tough programming challenges**, but you'll have a partner to help you carry the load.
Use your imagination! You get to create whatever you want for this app. Everyone will get a chance to **be creative**, and work through some really **tough programming challenges**, but you'll have a partner to help you carry the load.
@ -10,7 +10,10 @@ Use your imagination! You get to create whatever you want for this app. Everyone
Your app must:
Your app must:
* Use **Angular** as a front-end framework.
* M - Use mongoose with Mongodb
* E - Use Express
* A - Use **Angular** as a front-end framework
* N - Use Node
* Reference a third-party API.
* Reference a third-party API.
* Be deployed online where the rest of the world can access it.
* Be deployed online where the rest of the world can access it.
@ -42,7 +45,7 @@ By the time the project is over, we will expect the following from you:
* A **working app, built by you**, hosted somewhere on the internet
* A **working app, built by you**, hosted somewhere on the internet
* A **link to your hosted working app**
* A **link to your hosted working app**
* A **git repository hosted on Github** NOT inside your wdi-remote repository. Frequent commits dating back to the very beginning of the project
* A **git repository hosted on Github** NOT inside your wdi-remote repository. Frequent commits dating back to the very beginning of the project. **One branch for each feature**.
* **A ``readme.md`` file** with explanations of the technologies used, the approach taken, a link to your live site, a link to your daily tracker, your user stories, mvp, stretch goals, installation instructions, unsolved problems, etc.
* **A ``readme.md`` file** with explanations of the technologies used, the approach taken, a link to your live site, a link to your daily tracker, your user stories, mvp, stretch goals, installation instructions, unsolved problems, etc.
Most importantly a **technical demonstration** of your app which:
Most importantly a **technical demonstration** of your app which:
@ -56,9 +59,9 @@ Most importantly a **technical demonstration** of your app which:
## Project Feedback + Evaluation
## Project Feedback + Evaluation
* __Project Workflow__: Do you have a Github respository for your project (not inside your wdi-remote repo) and make good use of branching? Did you complete the user stories, wireframes, and the README.md file as specified above? Did you use the daily tracker and split the work load appropriately?
* __Project Workflow__: Do you have a Github respository for your project (not inside your wdi-remote repo) and make good use of branching (one branch for each feature all merged to your `master` branch)? Did you complete the user stories, wireframes, and the README.md file as specified above? Did you use the daily tracker and split the work load appropriately?
* __Technical Requirements__: Did you deliver a project that met all the technical requirements? Given what the class has covered so far, did you build something that was reasonably complex?
* __Technical Requirements__: Did you deliver a project that met all the technical requirements? Given what the class has covered so far, did you build something that was reasonably complex? Did you use Angular as a front-end framework? Did you use a third-party API?
* __Creativity__: Did you add a personal spin or creative element into your project submission? Did you deliver something of value to the end user (not just a login button and an index page)?
* __Creativity__: Did you add a personal spin or creative element into your project submission? Did you deliver something of value to the end user (not just a login button and an index page)?
@ -73,7 +76,7 @@ Most importantly a **technical demonstration** of your app which:
**7** | Project Workflow | Do you have a Github respository for your project (not inside your wdi-remote repo) and make good use of branching? (0-2) | Did you complete the user stories, wireframes, and the README.md file as specified above? (0-3) | Did you use the daily tracker and split the work load appropriately? (0-2) |
**7** | Project Workflow | Do you have a Github respository for your project (not inside your wdi-remote repo) and make good use of branching (one branch per feature)? (0-2) | Did you complete the user stories, wireframes, and the README.md file as specified above? (0-3) | Did you use the daily tracker and split the work load appropriately? (0-2) |
**10** | Technical Requirements | Did you use Angular as a front-end framework? (0-2) | Did you use a third-party API? (0-2) | Did you deliver a project that met all the technical requirements? (discussed in your MVP (a score between 0-3 will be given))| Given what the class has covered so far, did you build something that was reasonably complex? (complexity will be given a grade 0-3) |
**10** | Technical Requirements | Did you use Angular as a front-end framework? (0-2) | Did you use a third-party API? (0-2) | Did you deliver a project that met all the technical requirements? (discussed in your MVP (a score between 0-3 will be given))| Given what the class has covered so far, did you build something that was reasonably complex? (complexity will be given a grade 0-3) |
**5** | Creativity | Did you add a personal spin or creative element into your project submission? (0-2)| Did you deliver something of value to the end user (not just a login button and an index page)? (0-3) |
**5** | Creativity | Did you add a personal spin or creative element into your project submission? (0-2)| Did you deliver something of value to the end user (not just a login button and an index page)? (0-3) |
**2** | Code Quality | Did you follow code style guidance and best practices covered in class, such as spacing, modularity, and semantic naming? (1) | Did you comment your code as your instructors have in class? (1)|
**2** | Code Quality | Did you follow code style guidance and best practices covered in class, such as spacing, modularity, and semantic naming? (1) | Did you comment your code as your instructors have in class? (1)|
@ -112,17 +115,8 @@ _Your instructor will contact you to setup a meeting time_
- You will have a 15 minute meeting with an instructor in the afternoon to get your project approved.
- You will have a 15 minute meeting with an instructor in the afternoon to get your project approved.
- Create your daily tracker.
- Create your daily tracker.
**Tuesday, July 12**<br>
**Tuesday, July 12** - **Friday, July 15**<br>
15-30 minute progress check-in and look at your daily tracker. Students should be developing thier app.
15-30 minute progress check-ins and look at your daily tracker. Students should be developing thier app.
**Wedesday, July 13**<br>
15-30 minute progress check-in and look at your daily tracker. Students should be developing thier app.
**Thursday, July 14**<br>
15-30 minute progress check-in and look at your daily tracker. Students should be developing thier app.
**Friday, July 15**<br>
15-30 minute progress check-in and look at your daily tracker before you go into the weekend. Help to decide what to finish and what stretch goals should be attempted.
**Monday, July 18**<br>
**Monday, July 18**<br>
- Submit a Github issue by 10 am EDT with a live link to your project and a link to your Github repo.
- Submit a Github issue by 10 am EDT with a live link to your project and a link to your Github repo.
Thom Page
10 years ago