Should project target file live on gh-pages branch?

[thatandromeda]

Right now the goal is 'add your name to a file on master'. Proposal: possibly keeping modify-master as an intermediate goal, add a final goal of 'edit a page on the gh-pages branch'.

Advantages:

• also teaches git branching, which is super useful for workflow in more complex projects
• creates something that lives on the web -- can be a showpiece for the IG and something participants can point non-githubbers to

Disadvantages:

• harder, more confusing

Thoughts?

[phette23]

I think branching is an extra complication here, since Github renders Markdown right in the browser participants can still point to it (albeit at an ugly URL).

Maybe this is our step two? Doing something with Pages? I guess that's exactly what you're saying with modifying master being an "intermediary step." Pages is a great opportunity to play with branching because it gives you the website. On the other hand, Pages are orphan branches and sort of different from usual usage. Should I draft a Part II that's along the lines of "merge your Getting Started changes into gh-pages branch"?