From ad6808247ab24c2017e61237382e2505e777cb26 Mon Sep 17 00:00:00 2001 From: Kristyn Bryan Date: Fri, 8 Jul 2016 12:14:16 -0400 Subject: [PATCH 01/13] Update README.md --- projects/project_03/README.md | 135 ++++++++++++++++++++++++++++++++++ 1 file changed, 135 insertions(+) diff --git a/projects/project_03/README.md b/projects/project_03/README.md index e69de29..b495d2d 100644 --- a/projects/project_03/README.md +++ b/projects/project_03/README.md @@ -0,0 +1,135 @@ +# ![](https://ga-dash.s3.amazonaws.com/production/assets/logo-9f88ae6c9c3871690e33280fcf557f33.png) Project #3: Group Project +​ +## Overview +​ +For your 3rd project, you will be collaborating to make an application using Angular. +​ +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. + +## Technical Requirements +​ +Your app must: +​ +* Use a **Angular** as a front-end framework. +* Reference a third-party API. +* Be deployed online where the rest of the world can access it. +​ + +### Requirements before you get started (Please put these in your `README.md` file: +​ +* **User Stories** - +* **Wireframes** - One for each page / view of your application. +* **MVP** - +* **Stretch Goals** +* **Github Repo** - This should be outside of your wdi-remote class repo. One person should create this and then make their partner a "Contributor" + +### Suggestions on how to get started +* **Break the project down into different components** (data, presentation, views, style, DOM manipulation) and brainstorm each component individually. +* **Use your Development Tools** (console.log, inspector, alert statements, etc) to debug and solve problems +* Work through the lessons in class for help and inspiration! Think about adding relevant code each day; COMMIT OFTEN. We will be looking at your commit dates and comments are part of your scoring. +* **Commit early, commit often.** Don’t be afraid to break something because you can always go back in time to a previous version. +* **Consult documentation resources** (MDN, jQuery, etc.) at home to better understand what you’ll be getting into. +* **Don’t be afraid to write code that you know you will have to remove later.** Create temporary elements (buttons, links, etc) that trigger events if real data is not available. For example, if you’re trying to figure out how to change some text when the game is over but you haven’t solved the win/lose game logic, you can create a button to simulate that until then. +​ + +## Deliverables + +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 **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 ``readme.md`` file** with explanations of the technologies used, the approach taken, a link to your live site, installation instructions, unsolved problems, etc. + +Most importantly a **technical demonstration** of your app which: + +* Is 5 minutes in length +* Shows off all features of the app +* Explains the technical details +* Explains the technical challenges +* Explains which improvements you might make + +## Project Feedback + Evaluation +​ +* __Project Workflow__: Do you have a Github respository for your project (not inside your wdi-remote repo)? Did you complete the user stories, wireframes, and the README.md file as specified above? Did you use source control (Github commits) as expected for the phase of the program you’re in (detailed above)? +​ +* __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? +​ +* __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)? +​ +* __Code Quality__: Did you follow code style guidance and best practices covered in class, such as spacing, modularity, and semantic naming? Did you comment your code as your instructors have in class? +​ +* __Deployment__: Did you deploy your application to a public url using GitHub Pages? +​ +* __Total__: Your instructors will give you a total score on your project between: +​ + + Score | Category | Expectation | Expectation | Expectation | Expectation | Expectation | + :-----: | ------------ | ---------------- | --- | --- | --- | --- | + **6** | Project Workflow | Do you have a Github respository for your project (not inside your wdi-remote repo)? | Did you complete the user stories and are they in your Github issues (2 points) | wireframes | README.md with specified information | source control with Github (commits) | + **6** | Technical Requirements | Did you deliver a project that met all the technical requirements? (discussed in your MVP (a score between 1-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 1-3) | + **2** | 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)? | + **2** | Code Quality | Did you follow code style guidance and best practices covered in class, such as spacing, modularity, and semantic naming? | Did you comment your code as your instructors have in class? | + **2** | Deployment | Did you deploy your application to a public url using GitHub Pages? | + **2** | Technical demonstration | Is 5 minutes in length & shows off all the features of your app. | Expalins technical details, technical challenges, and any improvements you might make. | + _Maximum possible points_ | **20** | +​ + + + + +--- +# Project Week + +## Attendance +You are required to be present by 10:00 am EDT each day during the project. + +## Standups +We will have student-run stand-ups each morning at 10:15 am EDT where you will answer the following questions: +- What did I work on yesterday +- What am i trying to get done today +- What is preventing me from getting this done. + +This meeting should take no longer than 15 minutes. + +If you have ideas on how you can help a fellow-student with work that they are stuck on, please follow-up with information AFTER the stand up. + +## Meetings with instructors +_Your instructor will contact you to setup a meeting time_ + +**Tuesday, June 7**
+15 minute meeting to get your project approved. You will come with your [MVP](https://en.wikipedia.org/wiki/Minimum_viable_product) and an initial wireframe. + +**Wedesday, June 8**
+15 minute progress check-in + +**Thursday, June 9**
+Whole class instruction on how to deploy your project to the world wide web. + +**Friday, June 10**
+15 minute check in to see where you are before you go into the weekend. Help you to decide what to finish and what features should be stretch goals. + +## Where to go for help during project week +1. Seek out help online +2. Seek out help with your classmates +3. Seek out help with Derek (TA) +4. Submit a Github issue **on the wdi-remote** class Github account to receive help from an instructor + +## Formatting your GitHub Issue for wdi-remote to ask for help + +*PUSH OFTEN! Your code on GitHub should be up to date. Submiting an issue and linking us to old, out-of-date code will hinder the process.* + +1. **WHAT YOU ARE TRYING TO SOLVE:** + - Write a detailed explanation of the feature or user story you're working on. + +2. **DETAILED DESCRIPTION OF THE BUG/ERROR:** + - A detailed description of the problem, the bug, and/or the error. This means: the full steps to reproduce, a link to the file on github, and the line number of where the relavent code is. +The error(s) returned, copy and pasted/typed out/screenshot, not paraphrased. + - If there is other code in a different file that is also essential to the functioning of the code that currently works point us to that and explain the relationship. + +3. **WHAT I'VE TRIED** + - List everything you've done to solve the bug on your own in detail. list all resources you've looked up and tried to implement and provide links. Providing code if you have it surrounded by the md syntax to display nicely is very helpful. + +4. **QUESTION** + - After going through all this what is your questions specifically, more specifically than how can I make this work? + From 2e745e7a771bd108941612c192347b9ea1f72ebd Mon Sep 17 00:00:00 2001 From: Kristyn Bryan Date: Fri, 8 Jul 2016 12:19:35 -0400 Subject: [PATCH 02/13] Update README.md --- projects/project_03/README.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/projects/project_03/README.md b/projects/project_03/README.md index b495d2d..5c70a6d 100644 --- a/projects/project_03/README.md +++ b/projects/project_03/README.md @@ -15,13 +15,17 @@ Your app must: * Be deployed online where the rest of the world can access it. ​ -### Requirements before you get started (Please put these in your `README.md` file: +## Requirements before you get started +### Please put these in your `README.md` file: ​ * **User Stories** - * **Wireframes** - One for each page / view of your application. -* **MVP** - +* **MVP** - A minimum viable product which has just those core features sufficient to deploy the product, and no more. * **Stretch Goals** -* **Github Repo** - This should be outside of your wdi-remote class repo. One person should create this and then make their partner a "Contributor" +* **Github Repo** and use of **branches** - This should be outside of your wdi-remote class repo. One person should create this and then make their partner a "Contributor". + +## Once your project is approved +* Creat a **daily tracker** with a day-by-day breakdown of what features will be worked on to meet the MVP and any stretch goals that you would like to tackle ### Suggestions on how to get started * **Break the project down into different components** (data, presentation, views, style, DOM manipulation) and brainstorm each component individually. @@ -29,7 +33,7 @@ Your app must: * Work through the lessons in class for help and inspiration! Think about adding relevant code each day; COMMIT OFTEN. We will be looking at your commit dates and comments are part of your scoring. * **Commit early, commit often.** Don’t be afraid to break something because you can always go back in time to a previous version. * **Consult documentation resources** (MDN, jQuery, etc.) at home to better understand what you’ll be getting into. -* **Don’t be afraid to write code that you know you will have to remove later.** Create temporary elements (buttons, links, etc) that trigger events if real data is not available. For example, if you’re trying to figure out how to change some text when the game is over but you haven’t solved the win/lose game logic, you can create a button to simulate that until then. +* **Don’t be afraid to write code that you know you will have to remove later.** ​ ## Deliverables @@ -39,7 +43,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 **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 ``readme.md`` file** with explanations of the technologies used, the approach taken, a link to your live site, 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: From 2929bfff7fa0fea3f57b779187a716d4ed2605bf Mon Sep 17 00:00:00 2001 From: Kristyn Bryan Date: Fri, 8 Jul 2016 12:23:14 -0400 Subject: [PATCH 03/13] Update README.md --- projects/project_03/README.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/projects/project_03/README.md b/projects/project_03/README.md index 5c70a6d..fd80383 100644 --- a/projects/project_03/README.md +++ b/projects/project_03/README.md @@ -55,15 +55,17 @@ Most importantly a **technical demonstration** of your app which: ## Project Feedback + Evaluation ​ -* __Project Workflow__: Do you have a Github respository for your project (not inside your wdi-remote repo)? Did you complete the user stories, wireframes, and the README.md file as specified above? Did you use source control (Github commits) as expected for the phase of the program you’re in (detailed above)? +* __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? ​ * __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? ​ * __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)? ​ -* __Code Quality__: Did you follow code style guidance and best practices covered in class, such as spacing, modularity, and semantic naming? Did you comment your code as your instructors have in class? +* __Code Quality__: Did you follow code style guidance and best practices covered in class, such as spacing, modularity, and semantic naming? Did you **comment your code** as your instructors have in class? ​ -* __Deployment__: Did you deploy your application to a public url using GitHub Pages? +* __Deployment__: Did you deploy your application to a public url? +​ +* __Collaboration__: Did you contribute to the project as much as you should have (did you pull your weight)? ​ * __Total__: Your instructors will give you a total score on your project between: ​ From b0f8b39d558453a4bd84c835580f0eaae691ad09 Mon Sep 17 00:00:00 2001 From: Kristyn Bryan Date: Fri, 8 Jul 2016 12:32:10 -0400 Subject: [PATCH 04/13] Update README.md --- projects/project_03/README.md | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/projects/project_03/README.md b/projects/project_03/README.md index fd80383..27413e8 100644 --- a/projects/project_03/README.md +++ b/projects/project_03/README.md @@ -72,18 +72,16 @@ Most importantly a **technical demonstration** of your app which: Score | Category | Expectation | Expectation | Expectation | Expectation | Expectation | :-----: | ------------ | ---------------- | --- | --- | --- | --- | - **6** | Project Workflow | Do you have a Github respository for your project (not inside your wdi-remote repo)? | Did you complete the user stories and are they in your Github issues (2 points) | wireframes | README.md with specified information | source control with Github (commits) | - **6** | Technical Requirements | Did you deliver a project that met all the technical requirements? (discussed in your MVP (a score between 1-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 1-3) | - **2** | 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)? | - **2** | Code Quality | Did you follow code style guidance and best practices covered in class, such as spacing, modularity, and semantic naming? | Did you comment your code as your instructors have in class? | - **2** | Deployment | Did you deploy your application to a public url using GitHub Pages? | - **2** | Technical demonstration | Is 5 minutes in length & shows off all the features of your app. | Expalins technical details, technical challenges, and any improvements you might make. | - _Maximum possible points_ | **20** | + **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) | + **6** | Technical Requirements | 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) | + **4** | 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-2) | + **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)| + **1** | Deployment | Did you deploy your application to a public url? (1)| + **3** | Collaboration | Did you contribute to the project as much as you should have (did you pull your weight)? (0-3) | + **2** | Technical demonstration | Is 5 minutes in length & shows off all the features of your app. (1)| Expalins technical details, technical challenges, and any improvements you might make. (1)| + _Maximum possible points_ | **25** | ​ - - - --- # Project Week From a03ef98e2f599ae473d6dc7bad154cc3b52bd93d Mon Sep 17 00:00:00 2001 From: Kristyn Bryan Date: Fri, 8 Jul 2016 12:33:03 -0400 Subject: [PATCH 05/13] Update README.md --- projects/project_03/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/projects/project_03/README.md b/projects/project_03/README.md index 27413e8..9c35352 100644 --- a/projects/project_03/README.md +++ b/projects/project_03/README.md @@ -69,7 +69,7 @@ Most importantly a **technical demonstration** of your app which: ​ * __Total__: Your instructors will give you a total score on your project between: ​ - + Score | Category | Expectation | Expectation | Expectation | Expectation | Expectation | :-----: | ------------ | ---------------- | --- | --- | --- | --- | **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) | @@ -86,7 +86,7 @@ Most importantly a **technical demonstration** of your app which: # Project Week ## Attendance -You are required to be present by 10:00 am EDT each day during the project. +You are required to be present by 10:00 am EDT and again at 2:30 pm EDT each day during the project. ## Standups We will have student-run stand-ups each morning at 10:15 am EDT where you will answer the following questions: From 8b2b1dce678e862448eaf69a72804395f931f128 Mon Sep 17 00:00:00 2001 From: Kristyn Bryan Date: Fri, 8 Jul 2016 13:04:57 -0400 Subject: [PATCH 06/13] Update README.md --- projects/project_03/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/projects/project_03/README.md b/projects/project_03/README.md index 9c35352..9246882 100644 --- a/projects/project_03/README.md +++ b/projects/project_03/README.md @@ -73,13 +73,13 @@ Most importantly a **technical demonstration** of your app which: Score | Category | Expectation | Expectation | Expectation | Expectation | Expectation | :-----: | ------------ | ---------------- | --- | --- | --- | --- | **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) | - **6** | Technical Requirements | 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) | - **4** | 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-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) | + **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)| **1** | Deployment | Did you deploy your application to a public url? (1)| **3** | Collaboration | Did you contribute to the project as much as you should have (did you pull your weight)? (0-3) | **2** | Technical demonstration | Is 5 minutes in length & shows off all the features of your app. (1)| Expalins technical details, technical challenges, and any improvements you might make. (1)| - _Maximum possible points_ | **25** | + _Maximum possible points_ | **30** | ​ --- From a753c95096116429fc2587b5ed530af35d1b73b2 Mon Sep 17 00:00:00 2001 From: Kristyn Bryan Date: Fri, 8 Jul 2016 13:25:11 -0400 Subject: [PATCH 07/13] Update README.md --- projects/project_03/README.md | 35 +++++++++++++++++++++++++---------- 1 file changed, 25 insertions(+), 10 deletions(-) diff --git a/projects/project_03/README.md b/projects/project_03/README.md index 9246882..6eebff5 100644 --- a/projects/project_03/README.md +++ b/projects/project_03/README.md @@ -47,7 +47,8 @@ By the time the project is over, we will expect the following from you: Most importantly a **technical demonstration** of your app which: -* Is 5 minutes in length +* Is 5-10 minutes in length +* **BOTH** partners should speak during the presentation * Shows off all features of the app * Explains the technical details * Explains the technical challenges @@ -78,7 +79,7 @@ Most importantly a **technical demonstration** of your app which: **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)| **1** | Deployment | Did you deploy your application to a public url? (1)| **3** | Collaboration | Did you contribute to the project as much as you should have (did you pull your weight)? (0-3) | - **2** | Technical demonstration | Is 5 minutes in length & shows off all the features of your app. (1)| Expalins technical details, technical challenges, and any improvements you might make. (1)| + **2** | Technical demonstration | Is 5-10 minutes in length & shows off all the features of your app. (1)| Expalins technical details, technical challenges, and any improvements you might make. (1)| _Maximum possible points_ | **30** | ​ @@ -101,17 +102,31 @@ If you have ideas on how you can help a fellow-student with work that they are s ## Meetings with instructors _Your instructor will contact you to setup a meeting time_ -**Tuesday, June 7**
-15 minute meeting to get your project approved. You will come with your [MVP](https://en.wikipedia.org/wiki/Minimum_viable_product) and an initial wireframe. +**Monday, July 11**
+- Projects and groups are announced. +- Meet to discuss your ideas with your teammate and choose one (remember - you can always use these other ideas in our 4th project). +- Create a new Github repo outside of your wdi-remote repository. +- Create your user stories and add them to your `README.md` +- Write your MVPs & stretch goals and add them to your `README.md` +- Make your wireframes and add them to your `README.md` +- You will have a 15 minute meeting with an instructor in the afternoon to get your project approved. +- Create your daily tracker. -**Wedesday, June 8**
-15 minute progress check-in +**Tuesday, July 12**
+15-30 minute progress check-in and look at your daily tracker. Students should be developing thier app. -**Thursday, June 9**
-Whole class instruction on how to deploy your project to the world wide web. +**Wedesday, July 13**
+15-30 minute progress check-in and look at your daily tracker. Students should be developing thier app. -**Friday, June 10**
-15 minute check in to see where you are before you go into the weekend. Help you to decide what to finish and what features should be stretch goals. +**Thursday, July 14**
+15-30 minute progress check-in and look at your daily tracker. Students should be developing thier app. + +**Friday, July 15**
+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**
+- Submit a Github issue by 10 am EDT with a live link to your project and a link to your Github repo. +- Technical demonstration of your app (both partners are expected to speak) ## Where to go for help during project week 1. Seek out help online From 07abce51820110101bbff8650cae343066024aa9 Mon Sep 17 00:00:00 2001 From: Kristyn Bryan Date: Fri, 8 Jul 2016 13:25:35 -0400 Subject: [PATCH 08/13] Update README.md --- projects/project_03/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/projects/project_03/README.md b/projects/project_03/README.md index 6eebff5..30d510c 100644 --- a/projects/project_03/README.md +++ b/projects/project_03/README.md @@ -10,7 +10,7 @@ Use your imagination! You get to create whatever you want for this app. Everyone ​ Your app must: ​ -* Use a **Angular** as a front-end framework. +* Use **Angular** as a front-end framework. * Reference a third-party API. * Be deployed online where the rest of the world can access it. ​ From 82d21e6ca307fd42bba9e37938644188c8ecc70d Mon Sep 17 00:00:00 2001 From: Kristyn Bryan Date: Fri, 8 Jul 2016 13:26:31 -0400 Subject: [PATCH 09/13] Update README.md --- projects/project_03/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/projects/project_03/README.md b/projects/project_03/README.md index 30d510c..d20a5be 100644 --- a/projects/project_03/README.md +++ b/projects/project_03/README.md @@ -16,7 +16,7 @@ Your app must: ​ ## Requirements before you get started -### Please put these in your `README.md` file: +**Please put these in your `README.md` file:** ​ * **User Stories** - * **Wireframes** - One for each page / view of your application. From 88e210f07c0bf5d458902e711be27a0c52465f1a Mon Sep 17 00:00:00 2001 From: Kristyn Bryan Date: Fri, 8 Jul 2016 13:26:50 -0400 Subject: [PATCH 10/13] Update README.md --- projects/project_03/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/projects/project_03/README.md b/projects/project_03/README.md index d20a5be..b139a2a 100644 --- a/projects/project_03/README.md +++ b/projects/project_03/README.md @@ -18,7 +18,7 @@ Your app must: ## Requirements before you get started **Please put these in your `README.md` file:** ​ -* **User Stories** - +* **User Stories** * **Wireframes** - One for each page / view of your application. * **MVP** - A minimum viable product which has just those core features sufficient to deploy the product, and no more. * **Stretch Goals** From b6ec6c1fe1e189a6ab91e96a8928c92fcebe6fa6 Mon Sep 17 00:00:00 2001 From: Kristyn Bryan Date: Fri, 8 Jul 2016 13:27:52 -0400 Subject: [PATCH 11/13] Update README.md --- projects/project_03/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/projects/project_03/README.md b/projects/project_03/README.md index b139a2a..17a9283 100644 --- a/projects/project_03/README.md +++ b/projects/project_03/README.md @@ -71,8 +71,8 @@ Most importantly a **technical demonstration** of your app which: * __Total__: Your instructors will give you a total score on your project between: ​ - Score | Category | Expectation | Expectation | Expectation | Expectation | Expectation | - :-----: | ------------ | ---------------- | --- | --- | --- | --- | + Score | Category | Expectation | Expectation | Expectation | Expectation | + :-----: | ------------ | ---------------- | --- | --- | --- | **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) | **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) | From 57858bdd0892bb4f85548975b087103d94de141a Mon Sep 17 00:00:00 2001 From: Kristyn Bryan Date: Fri, 8 Jul 2016 13:29:53 -0400 Subject: [PATCH 12/13] Update README.md --- projects/project_03/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/projects/project_03/README.md b/projects/project_03/README.md index 17a9283..cd96faa 100644 --- a/projects/project_03/README.md +++ b/projects/project_03/README.md @@ -152,3 +152,5 @@ The error(s) returned, copy and pasted/typed out/screenshot, not paraphrased. 4. **QUESTION** - After going through all this what is your questions specifically, more specifically than how can I make this work? +5. **TAG YOUR INSTRUCTORS** + - In the comment section, tag your instructors so that they are alerted to your Github Issue as soon as you submit it. From 6fe7ddbf311d7f5f64f1a68bd6a1fd9db7c5fa69 Mon Sep 17 00:00:00 2001 From: Kristyn Bryan Date: Fri, 8 Jul 2016 13:37:24 -0400 Subject: [PATCH 13/13] Update README.md --- projects/project_03/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/projects/project_03/README.md b/projects/project_03/README.md index cd96faa..356093d 100644 --- a/projects/project_03/README.md +++ b/projects/project_03/README.md @@ -25,7 +25,7 @@ Your app must: * **Github Repo** and use of **branches** - This should be outside of your wdi-remote class repo. One person should create this and then make their partner a "Contributor". ## Once your project is approved -* Creat a **daily tracker** with a day-by-day breakdown of what features will be worked on to meet the MVP and any stretch goals that you would like to tackle +* Creat a **daily tracker** with a day-by-day breakdown of what features will be worked on to meet the MVP and any stretch goals that you would like to tackle. Include a link to his in your `README.md` station. Consider using Github Issues or Trello for this. ### Suggestions on how to get started * **Break the project down into different components** (data, presentation, views, style, DOM manipulation) and brainstorm each component individually.