Guest User

Untitled

a guest
Jun 21st, 2018
91
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.68 KB | None | 0 0
  1. ### Initial Notes
  2.  
  3. ## Depending on team size, assign roles for responsibiliites.
  4.  
  5. Front End - Designer (Pages layout, font, colors, CSS)
  6. Front End - Coder (frameworks used, coding mvp, HTML )
  7. Back End - Architect (database, github, firebase
  8. Back End - Coder ( coding MVP, javascript,
  9. ### Initial Notes
  10.  
  11. ## Depending on team size, assign roles for responsibiliites.
  12.  
  13. Front End - Designer (Pages layout, font, colors, CSS)
  14. Front End - Coder (frameworks used, coding mvp, HTML )
  15. Back End - Architect (database, github, firebase
  16. Back End - Coder ( coding MVP, javascript,
  17. Project Lead (User and Design Requirements, timeline, leading meetings, email and github communication)
  18. Tester/s - (Debug and review mvps)
  19.  
  20.  
  21. ## Team Members
  22. Lisa
  23. Abbi
  24. Ch
  25.  
  26. ## Tools
  27. Trello
  28. GitHub and GitHub Issues
  29.  
  30.  
  31. ## Requirements
  32.  
  33. must use 2 apis
  34. must use ajax to pull data
  35. must use anew library or technology
  36. must polished front end
  37. must meet good quality coding standards
  38. must not use alerts, confirms or prompts
  39. must have some sort of repeating element (table, colums, etc)
  40. must use Bootstrap or Alternate CSS Framework
  41. must be Deployed (Github Pages)
  42. Must have User Input Validation (Face++ library)
  43.  
  44. ### Nice to Haves
  45. Use firebase for data storage
  46. Mobile Responsive Media queries ( pick 2-3 mobile sizes )
  47. use an alternate CSS framework like Materialize
  48.  
  49. ### Presentation Requirements
  50. give 10 mnnute presetntaion
  51. Explain
  52. Your overall application conccep
  53. motivation for the development
  54. design processes
  55. technologies you used
  56. demonstration of its functionality (Ideas for future development and improvments)
  57.  
  58. ### Metrics
  59. concept
  60. design
  61. functionality
  62. collaboration
  63. presentation
  64.  
  65. ### Awards
  66. Most Awe inspiring
  67. most useful
  68. most creative
  69. best use of tech
  70. best ui/ux
  71.  
  72.  
  73. ### Ideas
  74. 1. Sports Landing Page
  75. Enter your favoirte team
  76. display
  77. latest news
  78. schedule and tiem of upcoming games
  79. odds of winning
  80.  
  81.  
  82.  
  83.  
  84.  
  85.  
  86.  
  87.  
  88.  
  89.  
  90.  
  91.  
  92. Part I: Branching and Submitting a Pull Request
  93.  
  94. In this section we will create a branch, add a feature, and submit a pull request. Only one group member should complete this section, everyone else should observe.
  95.  
  96. Clone the project repo onto your computer and cd into it.
  97.  
  98. Run the following command in your terminal to create and checkout to a new branch:
  99.  
  100. git checkout -b create-html-skeleton
  101.  
  102. You should now be on a new branch named “create-html-skeleton”. In order to verify this worked, run the following command in your terminal:
  103.  
  104. git branch
  105.  
  106. You should see two branches listed: master and create-html-skeleton. The create-html-skeleton branch should have an asterisk to the left of it. This indicates that this is the branch you’re currently on.
  107.  
  108. At the root of the repo, create a new file named index.html. Inside this file, add code for a basic HTML skeleton and save.
  109.  
  110. In your terminal, add and commit the changes. Then push up your code by running following in your terminal:
  111.  
  112. git push origin create-html-skeleton
  113.  
  114. This should push up your code to to GitHub on a branch with the same name (create-html-skeleton).
  115.  
  116. Go to the main repo page at github.com and you should see an button that says “Compare & pull request” -- click this.
  117.  
  118. On the next screen, add a description of the work that was done in the textarea and click the “Pull Request” button.
  119.  
  120. If completed successfully, you should see the pull request listed under the repo’s “Pull request” tab.Project Lead (User and Design Requirements, timeline, leading meetings, email and github communication)
  121. Tester/s - (Debug and review mvps)
  122.  
  123.  
  124. ## Team Members
  125. Lisa
  126. Abbi
  127. Ch
  128.  
  129. ## Tools
  130. Trello
  131. GitHub and GitHub Issues
  132.  
  133.  
  134. ## Requirements
  135.  
  136. must use 2 apis
  137. must use ajax to pull data
  138. must use anew library or technology
  139. must polished front end
  140. must meet good quality coding standards
  141. must not use alerts, confirms or prompts
  142. must have some sort of repeating element (table, colums, etc)
  143. must use Bootstrap or Alternate CSS Framework
  144. must be Deployed (Github Pages)
  145. Must have User Input Validation (Face++ library)
  146.  
  147. ### Nice to Haves
  148. Use firebase for data storage
  149. Mobile Responsive Media queries ( pick 2-3 mobile sizes )
  150. use an alternate CSS framework like Materialize
  151.  
  152. ### Presentation Requirements
  153. give 10 mnnute presetntaion
  154. Explain
  155. Your overall application conccep
  156. motivation for the development
  157. design processes
  158. technologies you used
  159. demonstration of its functionality (Ideas for future development and improvments)
  160.  
  161. ### Metrics
  162. concept
  163. design
  164. functionality
  165. collaboration
  166. presentation
  167.  
  168. ### Awards
  169. Most Awe inspiring
  170. most useful
  171. most creative
  172. best use of tech
  173. best ui/ux
  174.  
  175.  
  176. ### Ideas
  177. 1. Sports Landing Page
  178. Enter your favoirte team
  179. display
  180. latest news
  181. schedule and tiem of upcoming games
  182. odds of winning
  183.  
  184.  
  185.  
  186.  
  187.  
  188.  
  189.  
  190.  
  191.  
  192.  
  193.  
  194.  
  195. Part I: Branching and Submitting a Pull Request
  196.  
  197. In this section we will create a branch, add a feature, and submit a pull request. Only one group member should complete this section, everyone else should observe.
  198.  
  199. Clone the project repo onto your computer and cd into it.
  200.  
  201. Run the following command in your terminal to create and checkout to a new branch:
  202.  
  203. git checkout -b create-html-skeleton
  204.  
  205. You should now be on a new branch named “create-html-skeleton”. In order to verify this worked, run the following command in your terminal:
  206.  
  207. git branch
  208.  
  209. You should see two branches listed: master and create-html-skeleton. The create-html-skeleton branch should have an asterisk to the left of it. This indicates that this is the branch you’re currently on.
  210.  
  211. At the root of the repo, create a new file named index.html. Inside this file, add code for a basic HTML skeleton and save.
  212.  
  213. In your terminal, add and commit the changes. Then push up your code by running following in your terminal:
  214.  
  215. git push origin create-html-skeleton
  216.  
  217. This should push up your code to to GitHub on a branch with the same name (create-html-skeleton).
  218.  
  219. Go to the main repo page at github.com and you should see an button that says “Compare & pull request” -- click this.
  220.  
  221. On the next screen, add a description of the work that was done in the textarea and click the “Pull Request” button.
  222.  
  223. If completed successfully, you should see the pull request listed under the repo’s “Pull request” tab.
Add Comment
Please, Sign In to add comment