Should visuals be added?

[MicFin]

Should visuals be added to the README? a solution branch? or as image files? at all?

@nayana487

Just from past experience, I know that students have a hard time understanding local and remote repositories. I spent a good amount of time upfront talking about how what we did with git so far only applied to the code we have on our local machines. Then I asked, so what if we're working with others and want them to be able to access the code on their own machines or if somehow we lost the code on our own machines..setting up the case for why we use github. I also showed them the photos from this DC lesson: https://github.com/ga-wdi-lessons/git-intro so they can visualize the process.

[BenGitsCode]

I do like the Wallace and Gromit diagram in that link, mostly because it's using the same metaphor that the git documentation uses to describe itself.

[MicFin]

I absolutely rely on whiteboard diagrams for this talk. @payne-chris-r also used a white board diagram the next morning to emphasize the fork, clone, and push workflow. It would be beneficial to have a diagram in the repository in some fashion as Delivery Notes or part of the talk.

[BenGitsCode]

Rachel and I were just talking about this and one of the best ways I think for now (as we refine a delivery notes workflow) is to open an issue including an image of any diagrams used in delivery, Those are great resources to see in an issue, as someone who is prepping it for delivery.

[MicFin]

More diagrams were used for creating a repository locally and then on github as well as for addinga remote but this is a start.