pndpo - https://github.com/VikingPeter/danebook_pages.git phyman - https://github.com/phyman/danebook_pages.git
This pair project concludes Week 1 of the Viking Code School
The project is created using an Agile Development approach and managed with a Pivotal Tracker project. You will complete it by pair programming with your partner, making sure to switch off every 25 minutes (determined by a pomodoro timer.
- Check out the Pivotal Tracker Project to see the stories for this project. The Acceptance Criteria for each story is listed in the Tasks field. The mockups are included as comments on their respective Epics (you might need to click the "Epics" tab to display them). Familiarize yourself with what you'll be building.
- Each partner should fork this repository to make a copy and then clone their fork locally.
- Each partner should add a remote to their local clone called "pair" which points to their partner's fork (e.g.
$ git remote add pair https://github.com/partner_username/repo_name.git). This is how you'll pass changes between each other when it's time to switch roles.
You will produce the desired pages using your understanding of HTML, CSS, SASS and Bootstrap.
- Choose the first driver and start screen sharing. For starters, add a link to each partner's Github repo to this README on the first driver's machine.
- Begin working through the stories on the first driver's machine. Start the pomodoro timer for 25 minutes.
- Commit often -- do it whenever some useful piece of markup is finished.
- When the pomodoro interval is up, commit all current changes and then push them up to Github.
- The new driver should update their repo from their partner's fork using the remote you set up already --
$ git pull pair.
Once you've completed all the stories and pages, you will need to submit your work back to the main repository and perform code review.
- When all stories are complete, the last driver should push their copy to their fork as normal. The last navigator should update their repository as if he/she was about to switch roles and then push these changes to his/her fork. Now both partners should have current forks.
- Each partner should submit their fork as a separate pull request back to the main upstream repository.
- After submitting your pull request, you will perform a code review on your assigned partner for the upcoming week. As before, identify that person's pull request on the Pull Requests tab and reviewing the files it contains.
- Submit your review as comments to the pull request.