Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- ### Initial Notes
- ## Depending on team size, assign roles for responsibiliites.
- Front End - Designer (Pages layout, font, colors, CSS)
- Front End - Coder (frameworks used, coding mvp, HTML )
- Back End - Architect (database, github, firebase
- Back End - Coder ( coding MVP, javascript,
- ### Initial Notes
- ## Depending on team size, assign roles for responsibiliites.
- Front End - Designer (Pages layout, font, colors, CSS)
- Front End - Coder (frameworks used, coding mvp, HTML )
- Back End - Architect (database, github, firebase
- Back End - Coder ( coding MVP, javascript,
- Project Lead (User and Design Requirements, timeline, leading meetings, email and github communication)
- Tester/s - (Debug and review mvps)
- ## Team Members
- Lisa
- Abbi
- Ch
- ## Tools
- Trello
- GitHub and GitHub Issues
- ## Requirements
- must use 2 apis
- must use ajax to pull data
- must use anew library or technology
- must polished front end
- must meet good quality coding standards
- must not use alerts, confirms or prompts
- must have some sort of repeating element (table, colums, etc)
- must use Bootstrap or Alternate CSS Framework
- must be Deployed (Github Pages)
- Must have User Input Validation (Face++ library)
- ### Nice to Haves
- Use firebase for data storage
- Mobile Responsive Media queries ( pick 2-3 mobile sizes )
- use an alternate CSS framework like Materialize
- ### Presentation Requirements
- give 10 mnnute presetntaion
- Explain
- Your overall application conccep
- motivation for the development
- design processes
- technologies you used
- demonstration of its functionality (Ideas for future development and improvments)
- ### Metrics
- concept
- design
- functionality
- collaboration
- presentation
- ### Awards
- Most Awe inspiring
- most useful
- most creative
- best use of tech
- best ui/ux
- ### Ideas
- 1. Sports Landing Page
- Enter your favoirte team
- display
- latest news
- schedule and tiem of upcoming games
- odds of winning
- Part I: Branching and Submitting a Pull Request
- 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.
- Clone the project repo onto your computer and cd into it.
- Run the following command in your terminal to create and checkout to a new branch:
- git checkout -b create-html-skeleton
- 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:
- git branch
- 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.
- 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.
- In your terminal, add and commit the changes. Then push up your code by running following in your terminal:
- git push origin create-html-skeleton
- This should push up your code to to GitHub on a branch with the same name (create-html-skeleton).
- Go to the main repo page at github.com and you should see an button that says “Compare & pull request” -- click this.
- On the next screen, add a description of the work that was done in the textarea and click the “Pull Request” button.
- 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)
- Tester/s - (Debug and review mvps)
- ## Team Members
- Lisa
- Abbi
- Ch
- ## Tools
- Trello
- GitHub and GitHub Issues
- ## Requirements
- must use 2 apis
- must use ajax to pull data
- must use anew library or technology
- must polished front end
- must meet good quality coding standards
- must not use alerts, confirms or prompts
- must have some sort of repeating element (table, colums, etc)
- must use Bootstrap or Alternate CSS Framework
- must be Deployed (Github Pages)
- Must have User Input Validation (Face++ library)
- ### Nice to Haves
- Use firebase for data storage
- Mobile Responsive Media queries ( pick 2-3 mobile sizes )
- use an alternate CSS framework like Materialize
- ### Presentation Requirements
- give 10 mnnute presetntaion
- Explain
- Your overall application conccep
- motivation for the development
- design processes
- technologies you used
- demonstration of its functionality (Ideas for future development and improvments)
- ### Metrics
- concept
- design
- functionality
- collaboration
- presentation
- ### Awards
- Most Awe inspiring
- most useful
- most creative
- best use of tech
- best ui/ux
- ### Ideas
- 1. Sports Landing Page
- Enter your favoirte team
- display
- latest news
- schedule and tiem of upcoming games
- odds of winning
- Part I: Branching and Submitting a Pull Request
- 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.
- Clone the project repo onto your computer and cd into it.
- Run the following command in your terminal to create and checkout to a new branch:
- git checkout -b create-html-skeleton
- 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:
- git branch
- 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.
- 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.
- In your terminal, add and commit the changes. Then push up your code by running following in your terminal:
- git push origin create-html-skeleton
- This should push up your code to to GitHub on a branch with the same name (create-html-skeleton).
- Go to the main repo page at github.com and you should see an button that says “Compare & pull request” -- click this.
- On the next screen, add a description of the work that was done in the textarea and click the “Pull Request” button.
- 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