add screenshots and more context to responses

Author: hectorsector

config.yml

@@ -162,6 +162,10 @@ steps:
     title: Congratulations
     body: congratulations.md
     action_id: congratulationsIssue
+    data:
+      learningPathURL: 'https://github-learning-lab-staging.herokuapp.com/githubtraining/paths/innersource:-theory-to-practice'
+      forkURL: '%payload.repository.html_url%/fork'
+      downloadURL: '%payload.repository.html_url%/archive/master.zip'
   - type: respond
     with: goto-pr.md
     data:

responses/congratulations.md

@@ -1,8 +1,15 @@
 # :tada: Congratulations
 
-You are finished with this course. You can see a deployed version of our work together at [LINK]. Feel free to share this link directly with others, or move it to your own organization.
+You are finished with this course. You can see a deployed version of our work together at [LINK]. Feel free to share this link directly with others, or you can save the resources in one of the following ways.
 
-- If your organization is on GitHub.com, [fork it]().
-- If your organization is on GitHub Enterprise Server, [clone and push it]() to your instance. 
+### Saving course resources
 
-Your next steps are in the [Innersource learning path]().
+1. If you'd like to just save the contents to your machine, you can:
+    - Use this shortcut link to [download the files]({{ downloadURL }})
+    - Manually download the files by clicking on the **Code** tab, clicking on **Clone or download** and clicking **Download ZIP**.
+    - [Clone the repository](https://help.github.com/en/articles/cloning-a-repository) to your machine.
+1. If you'd like to transfer the repository to an organization on GitHub:
+    - If your organization is on GitHub.com, [fork it]({{ forkURL }}).
+    - If your organization is on GitHub Enterprise Server, [transfer the repository](https://help.github.com/enterprise/2.2/admin/articles/moving-a-repository-from-github-com-to-github-enterprise)
+
+Your next steps are in the [Innersource learning path]({{ learningPathURL }}).

responses/discoverability-answer.md

@@ -1,6 +1,6 @@
 ### Answer :crystal_ball:
 
-This repository is actually for ___.
+This repository is the source code for https://services.github.com.
 
 Did you guess it? Probably not, because it doesn't contain many of the necessary elements to make a repository discoverable.
 
@@ -9,4 +9,6 @@ Some suggestions to ensure your teammates can find your repository are:
 - give your repository a description
 - provide a URL for the deployment of the app, or documentation about this project
 
+Discover more about how to make a repository discoverable by visiting the **Files Changed** tab. It's OK if you want to do this later, any resources we cover throughout the course will be available at the end. 
+
 Please merge this PR.

responses/discoverable.md

@@ -4,6 +4,6 @@ This PR is all about how to make your repositories more discoverable.
 
 What is this repository for?
 
-[SCREENSHOT OF BARE REPOSITORY WITHOUT DOCS]
+![screenshot of a repository with no description, link, or and just a few folders: .github, .vscode, _appendix, _events, _includes, _layouts](https://user-images.githubusercontent.com/16547949/56039355-2430b380-5d02-11e9-999c-aa139a8146c2.png)
 
 I'll respond when I detect you've submitted a comment on this PR.

responses/metrics-answer.md

@@ -2,7 +2,10 @@
 
 Those are great ideas!
 
-Here are some other ideas of measuring how well you're doing:
-- IDEAS HERE
+Here are some other ideas for measuring how well you're doing:
+- Time to market
+- PRs to fix bugs
+- PRs to implement suggested features
+- number of collaborators to a project outside of maintaining team
 
 I'll respond when you merge this PR. 

responses/projects.md

@@ -2,13 +2,14 @@ This to discuss project management!
 
 ### Challenge question
 
-Here's some open issues in this company project. Which one should you work on?
+Here's some open issues in this company project. You're eager to help with this project. Which issue should you work on?
 
-[SCREENSHOT OF A HANDFUL OF ISSUES]
+![screenshot of a repository with 5 open issues, none without labels and all opened by @githubteacher. The issues are: restyle the slides, improve the readme, add a caption to an existing slide, add a new slide, activity 1: your first caption](https://user-images.githubusercontent.com/16547949/56040343-30b60b80-5d04-11e9-90c7-58e9791b8ebf.png)
 
-- [ ] issue 1
-- [ ] issue 2
-- [ ] issue 3
-- [ ] issue 4
+- [ ] Issue 6: Restyle the slides
+- [ ] Issue 5: Improve the README
+- [ ] Issue 4: Add a caption to an existing slide
+- [ ] Issue 3: Add a new slide
+- [ ] Issue 2: Activity 1: Your first caption
 
 I'll respond when you check one of the boxes above. 

responses/repo-owner-answer.md

@@ -1,15 +1,18 @@
 ### Answer :crystal_ball:
 
-A repository _does_ exist at githubtraining/training-manual.
+A repository _does_ exist at githubtraining/training-manual, but it is private.
+
+![screenshot of repository, pointing to ownership by githubtraining organization, and to a private visibility](https://user-images.githubusercontent.com/16547949/56038959-31996e00-5d01-11e9-8a08-5dadb0f026ce.png)
 
 <details>
-<summary>Why can't you see it then? Review the **Files Changed** tab and see if you can figure it out. Collapse this text if you'd like an explanation.</summary>
+<summary>Why can't you see it then? Review the <b>Files Changed</b> tab and see if you can figure it out. Collapse this text if you'd like an explanation.</summary>
 
 The repository `training-manual` in the @githubtraining organization is private, and only visible to memebers of that organization. If you're not a member of the organization, it'll appear like the repository doesn't exist to you. This is an example of why having the right ownership structure is important. Having too many organizations with restrictive permissions means that each organization's work will be siloed. 
 </summary>
 
 Here are some recommendations based on some :sparkles: use of GitHub that we've seen:
 - aim for as few organizations as possible, remember: each organization is a black box to those outside of that organization
 - name your repositories in a meaningful manner, usually a simple project or application name will suffice
+</summary>
 
 Please merge this PR.

responses/repo-owner.md

@@ -4,7 +4,7 @@ This pull request is all about repository ownership and naming conventions.
 
 Does a repository exist at https://github.com/githubtraining/training-manual?
 
-- [ ] True, there is at the given URL.
+- [ ] True, there is a repository at the given URL.
 - [ ] False, no repository exists at the given URL.
 
 I'll respond when I detect you've checked one of the boxes above. 

responses/templates.md

@@ -4,9 +4,9 @@ Let's now learn about issue and pull request templates.
 
 Here are four different ways you could submit a bug report. Which is the _right_ way? 
 
-- [ ] [SCREENSHOT 1]
-- [ ] [SCREENSHOT 2]
-- [ ] [SCREENSHOT 3]
-- [ ] [SCREENSHOT 4]
+- [ ] Open an issue on GitHub
+- [ ] Create a Jira issue
+- [ ] Open an internal support ticket
+- [ ] DM or email the maintainer
 
 I'll respond when you check one of the boxes above. 

responses/workflows.md

@@ -2,10 +2,14 @@ This PR covers a few common workflow that are likely in use within your organiza
 
 ### Challenge question
 
-I'd like to contribute to this repository. Which branch should I target my changes for? 
+Suppose you'd like to contribute to the repository whose branches are pictured below. Which branch should I use as a base for my contributions?
+
+![a screenshot of a repository's branches, they are: a protected master branch, a protected release-v1.0 branch. The rest are unprotected: bug-fix, green-colors, config-release-drafter, add-template](https://user-images.githubusercontent.com/16547949/56039935-5d1d5800-5d03-11e9-8a26-29d36cfc7499.png)
+
 - [ ] `master`
-- [ ] `release-candidate`
-- [ ] `dev`
-- [ ] Don't know
+- [ ] `release-v1.0`
+- [ ] `bug-fix`
+- [ ] `green-colors`
+- [ ] `config-release-drafter`
 
 I'll respond when I detect you've checked one of the boxes above.