Merge branch 'master' into rename-default-branch

Author: brianamarie

config.yml

@@ -1,10 +1,42 @@
-Learning Lab helps people build real world skills through hands-on activities. This course streamlines the course building process, and gives you all the tools you need to help others learn. 
+Learning Lab helps people build real world skills through hands-on activities. This course streamlines the course building process, and gives you all the tools you need to help others learn.
 
-Register for this course to get the starter files needed to build your Learning Lab course, or complete the course steps for a fully guided experience. If you choose to complete the course, you'll be able to:
+If you'd like to get started in building courses for others, this is the course for you! 
 
-- Identify the structure of a Learning Lab course
-- Define a title and description for your course
-- Define a template repository
-- Create course steps
-- Create responses
-- Publish a course to GitHub Learning Lab
+# What you'll learn
+
+This course will answer questions like:
+- How does a Learning Lab course work?
+- What are GitHub events?
+- What's a step?
+- How do I write responses?
+- What topic is a good candidate for a Learning Lab course?
+- How do I give a learner feedback?
+- How do I list a course in the catalog and publish it? 
+
+After taking this course, you'll be able to:
+- Design a course using your chosen topic
+- Create your course on GitHub Learning Lab
+- Break down your topic into smaller steps for GitHub
+- Create a template repository
+
+# What you'll build
+
+![screenshot of a sample config.yml file](https://user-images.githubusercontent.com/16547949/75559284-2fbbc480-5a11-11ea-8288-49ac143dfa4a.png)
+
+For this course, the best reference point is any other completed Learning Lab course! Take a look at the [source code for all our courses](https://github.com/search?q=topic%3Alearning-lab+org%3Agithubtraining+fork%3Atrue). Feel free to dive into the `config.yml` file for each course and explore!
+
+# Prerequisites
+
+We recommend you first complete the following courses:
+
+- [Introduction to GitHub](https://lab.github.com/githubtraining/introduction-to-github/) to learn how to use GitHub and pull requests to edit files.
+- [Communicating using Markdown](https://lab.github.com/githubtraining/communicating-using-markdown) to learn Markdown, which is used to create response files and throughout the course creation process.
+- [Getting started with GitHub Apps](https://lab.github.com/githubtraining/getting-started-with-github-apps) for understanding webhooks, events, and the basics of the GitHub API.
+
+# Projects used
+
+This course uses all original content, we didn't use any open source projects to create it.
+
+# Audience
+
+Developers, teachers, and team leads.

course-details.md

@@ -0,0 +1,43 @@
+# Welcome!
+
+This course will walk you through creating your own Learning Lab course. If you've ever wanted to create a learning resource using Learning Lab, then you're in the right place! Together, we'll go through:
+
+- Picking a topic
+- Breaking the topic down into small steps
+- Designing a learner centered course flow
+- Choosing a project repository
+- Mapping the small steps into GitHub events
+- Writing responses
+- Importing and creating your course
+
+### Prerequisites
+
+- **GitHub knowledge**: For this course, you'll need to know how to use GitHub to work with text files. If you need a refresher on the GitHub flow, check out [the Introduction to GitHub course]({{ host}}/courses/introduction-to-github). If you need a refresher on Markdown, check out [the Communicating using Markdown course]({{ host}}/courses/communicating-using-markdown).
+- **Webhooks & the GitHub API**: You'll also need a general understanding of webhooks and the GitHub API.  Try [the Getting started with GitHub Apps course]({{ host}}/courses/getting-started-with-github-apps).
+
+### Choosing a topic
+
+The first thing we're going to do is talk about and choose a topic.
+
+You may already have something in mind for your first course. In this course, you can actually start writing that idea and making it reality! If you're just curious about how to write a course or don't have an idea (yet), try  Markdown as a topic.
+
+Here are some things to think about as you select your topic:
+
+#### Things that work with GitHub
+
+Does it happen on GitHub anyway? Learning Lab is best when it's working with something that it can interact with naturally. Things like painting would be difficult! Commits or interactions with GitHub are the perfect fit.
+
+#### Scope and size
+
+What's the scope or size? For example, JavaScript makes a lot of sense to teach on Learning Lab because code happens on GitHub. But, it's a really big topic. It may be a good idea to segment your topic into smaller parts. Remember, users can take a series of Labs. If you aren't sure what the right size is, that's OK - that should become more clear as we go on.
+
+## Step 1: Choose a topic for your course
+
+Whether you choose your own topic or one of ours, you'll stick with the same one throughout this course. Don't worry, you don't have to publish it right away - we'll show you how to keep your course hidden as a _Draft_ until you are ready to show it to the world.
+
+### :keyboard: Activity: Tell us what you'd like to teach
+
+1. Please comment below with the subject that you'd like to teach in your Learning Lab course. If you don't have an idea yet, you can use Markdown as your topic.
+
+<hr>
+<h3 align="center">I'll respond below when I detect a comment in this pull request.</h3>

responses/00.0_welcome.md

@@ -0,0 +1,52 @@
+Great! When you commented, you triggered something called a webhook that I heard, and now I'm here! You may be wondering if I checked to see if  what you wrote was a _real_ topic. We'll talk about that kind of logic later - both how to use it, and when to use it. (Spoiler - for this step, I didn't check! I am pretty smart, but not smart enough to tell if you typed a good idea or not.)
+
+### Breaking goals into smaller steps
+
+Now that you know what you want to teach, the next thing to do is break it down into steps. This can be tricky - put on a teacher hat and an engineer hat at the same time.
+
+To break down the thing you want to teach, think about the observable behaviors. They should show that the user is doing it right. If you were watching this person, how would you know they've mastered the thing? Some examples are:
+
+- Close an issue
+- Write a functional SQL query
+- Merge a pull request
+- Change code so a particular test passes
+
+### How many goals?
+
+The right number of "goals" may be different for different courses. But, our courses usually have between 7 and 20. For example, in the Communicating Using Markdown course, the steps (or goals) are:
+
+- Create a task list
+- Turn on GitHub Pages
+- Add headers
+- Merge your headers
+- Add an image
+- Add a profile link
+- Merge your image and profile link
+- Add a list
+- Use emphasis
+- Merge lists and emphasis
+
+### What NOT to do
+
+It is _not_ a good idea to have huge or ambiguous steps.
+
+Put yourself in the shoes of a beginner. If you're asked to do something too big that you don't understand, it can be frustrating. Asking the learner to do something poorly defined creates confusion and misunderstandings. This can make the learner give up!
+
+> Imagine you're taking a course on SQL as a beginner. If one of the steps is to write a full query, you might not know where to start. You may try your best, but still be confused about what isn't working. Or, if you can get it right from copying and pasting, you wouldn't understand it well enough to do it on your own. Stick to smaller steps, and include prerequisites at the beginning of the course.
+
+## Step 2: Break your course into smaller steps
+
+In the file in this pull request, write the steps as observable behaviors. It's OK if there are a lot. It's better to break it down into small steps. Then, you may realize the scope of the course is wrong. That is better than having huge or unmanageable steps.
+
+> What's `#` in YAML? Any lines starting with `#` in the `config.yml` file are _comments_. We will use these for planning and documentation.
+
+### :keyboard: Activity: Break down what you'd like to teach into smaller learning objectives
+
+1. [Edit the `config.yml` document]({{ url }}). Break down the larger goal into smaller steps and add them to the commented descriptions on lines 26, 35, 40, 47, and 54.
+2. In each step, notice the fields for `title` and `description`. These will be shown to the learner on Learning Lab. Write the titles and descriptions of each of your steps.
+    - _You only need to worry about the title and description now. We'll fill in the rest later!_
+3. Commit your changes.
+4. Navigate _back_ to this pull request.
+
+<hr>
+<h3 align="center">I'll respond in this pull request when I detect a commit on this branch.</h3>