Decide on changes to Github page(s)...

[chalmerlowe]

Right now, the table of contents has two links on the overhaul branch related to github, that need some work:

https://github.com/chalmerlowe/intro_to_sprinting/blob/overhaul/class_materials/github_setup.md
https://github.com/chalmerlowe/intro_to_sprinting/blob/overhaul/class_materials/fork_a_repo.md

Right now, the github setup page has the content needed in the fork_a_repo page.

ACTION: decide on whether we need two pages OR not.
IF yes, then migrate the right materials to each page.

feel free to discuss here.

[steve-lorenz]

@chalmerlowe I think this depends if the 'fork page' will talk about syncing a fork. If this is out of the scope of this tutorial, then I would say it should be on a single page.

[chalmerlowe]

@Lorenz21 the benefit to having it on two pages is that the table of contents (TOC) will allow folks to get closer to their end goal faster, if they need a quick refresher on how to fork a repo.
it is not inherently obvious just looking at the TOC that github setup is OR should include steps on fork a repo.

[chalmerlowe]

I looked at the setting up github page in the tutorial.
if we separate out the content into two pages...

• setting up github
• forking a repo

both pages will be short, but will clearly point to what can be expected on that page.
@seawolf42 do you have any thoughts on this?

[seawolf42]

@chalmerlowe I think that's a great idea... also bumps the time down to about 5m each, and in this case the actual step should be something people can do with little variance in how long it takes.