Merge branch 'master' into fix-windows

Author: beardofedu

.github/ISSUE_TEMPLATE.md

@@ -11,10 +11,10 @@
 <If new idea or direction, please create a checklist of proposed ideas or next steps. [Example](https://github.com/github/training-kit/issues/415).>
 
 ### How to Contribute
-- [ ] Comment on this issue if you'd like to work/collaborate on it! 
+- [ ] Comment on this issue if you'd like to work/collaborate on it!
 - [ ] Fork the [repository](https://github.com/github/training-kit).
-- [ ] Use the [GitHub Flow](https://guides.github.com/introduction/flow/) to make changes to your fork. [This](https://services.github.com{{site.baseurl}}/intro-to-github/) is a refresher course if you're unsure about how to make a change on GitHub.
-- [ ] Push your changes to your repository. 
+- [ ] Use the [GitHub Flow](https://guides.github.com/introduction/flow/) to make changes to your fork. [This](https://services.github.com/on-demand/intro-to-github/) is a refresher course if you're unsure about how to make a change on GitHub.
+- [ ] Push your changes to your repository.
 - [ ] Submit a Pull Request
   - Base Dropdown: github/training-kit
   - Compare Dropdown: Your fork
@@ -26,7 +26,7 @@ If you'd like to make and test changes locally (and see how they would look if m
   - [Install Ruby](https://www.ruby-lang.org/en/documentation/installation/)
   - [ ] Run `script/setup`
   - [ ] Run `script/server`.
-    - When successful, the script will initiate a local server at `http://127.0.0.1:4000{{site.baseurl}}`.
+    - When successful, the script will initiate a local server at `http://127.0.0.1:4000/on-demand`.
 
 ### Questions?
 - Leave a comment on this issue! Make sure to use @ mentions if you want a specific person's attention!

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [[email protected]](mailto:[email protected]). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -1,5 +1,9 @@
 # Help Us Improve These Materials
 
-We're always looking for contributions to help improve these materials. If you have corrections, polish, or materials contributions, please submit them via a [Pull Request](https://help.github.com/articles/using-pull-requests). 
+We're always looking for contributions to help improve these materials. If you have corrections, polish, or materials contributions, please submit them via a [Pull Request](https://help.github.com/articles/using-pull-requests).
 
 If your contribution is larger than a syntax fix or sentence re-wording, please initiate a discussion via a new Issue (type `c` after switching focus to the [Issues](https://github.com/github/training-kit/issues) tab) so we can help guide your contribution to the right location in the materials.
+
+## Using Primer
+
+This site uses GitHub's CSS toolkit called [Primer](https://github.com/primer/primer-css). It's easy to use, and if your contribution requires some design or front-end work you should check out the [Primer Docs](http://primercss.io/).

Gemfile.lock

@@ -17,21 +17,21 @@ GEM
     ethon (0.10.1)
       ffi (>= 1.3.0)
     execjs (2.7.0)
-    faraday (0.13.0)
+    faraday (0.13.1)
       multipart-post (>= 1.2, < 3)
     ffi (1.9.18)
     forwardable-extended (2.6.0)
     gemoji (3.0.0)
-    github-pages (151)
+    github-pages (155)
       activesupport (= 4.2.8)
       github-pages-health-check (= 1.3.5)
-      jekyll (= 3.5.1)
+      jekyll (= 3.5.2)
       jekyll-avatar (= 0.4.2)
       jekyll-coffeescript (= 1.0.1)
       jekyll-default-layout (= 0.1.4)
       jekyll-feed (= 0.9.2)
       jekyll-gist (= 1.4.1)
-      jekyll-github-metadata (= 2.6.0)
+      jekyll-github-metadata (= 2.8.0)
       jekyll-mentions (= 1.2.0)
       jekyll-optional-front-matter (= 0.2.0)
       jekyll-paginate (= 1.1.0)
@@ -51,7 +51,7 @@ GEM
       jekyll-theme-midnight (= 0.1.0)
       jekyll-theme-minimal (= 0.1.0)
       jekyll-theme-modernist (= 0.1.0)
-      jekyll-theme-primer (= 0.4.0)
+      jekyll-theme-primer (= 0.5.0)
       jekyll-theme-slate (= 0.1.0)
       jekyll-theme-tactile (= 0.1.0)
       jekyll-theme-time-machine (= 0.1.0)
@@ -70,7 +70,7 @@ GEM
       octokit (~> 4.0)
       public_suffix (~> 2.0)
       typhoeus (~> 0.7)
-    html-pipeline (2.6.0)
+    html-pipeline (2.7.0)
       activesupport (>= 2)
       nokogiri (>= 1.4)
     html-proofer (3.7.2)
@@ -83,7 +83,7 @@ GEM
       typhoeus (~> 0.7)
       yell (~> 2.0)
     i18n (0.8.6)
-    jekyll (3.5.1)
+    jekyll (3.5.2)
       addressable (~> 2.4)
       colorator (~> 1.0)
       jekyll-sass-converter (~> 1.0)
@@ -104,7 +104,7 @@ GEM
       jekyll (~> 3.3)
     jekyll-gist (1.4.1)
       octokit (~> 4.2)
-    jekyll-github-metadata (2.6.0)
+    jekyll-github-metadata (2.8.0)
       jekyll (~> 3.1)
       octokit (~> 4.0, != 4.4.0)
     jekyll-mentions (1.2.0)
@@ -154,7 +154,7 @@ GEM
     jekyll-theme-modernist (0.1.0)
       jekyll (~> 3.5)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-primer (0.4.0)
+    jekyll-theme-primer (0.5.0)
       jekyll (~> 3.5)
       jekyll-seo-tag (~> 2.2)
     jekyll-theme-slate (0.1.0)

README.md

@@ -5,13 +5,13 @@
 # GitHub Training Kit
 ### Home of GitHub's On-Demand training
 
-This repository contains the completely open source on-demand training hosted at https://services.github.com{{site.baseurl}}/. These materials are provided under a [_Creative Commons License_ license](https://github.com/github/training-kit/blob/master/LICENSE).
+This repository contains the completely open source on-demand training hosted at https://services.github.com/on-demand/. These materials are provided under a [_Creative Commons License_ license](https://github.com/github/training-kit/blob/master/LICENSE).
 
 ## We :heart: Contributors Like You!
 
 **We’re eager to work with you**, our user community to improve these materials and develop new ones. Here's how you can help:
 
-- **You spotted a mistake:** please feel free to fork the repository and submit a change via Pull Request (not sure how to do that, [we have a course for you](https://services.github.com{{site.baseurl}})).
+- **You spotted a mistake:** please feel free to fork the repository and submit a change via Pull Request (not sure how to do that, [we have a course for you](https://services.github.com/on-demand/)).
 - **You have an idea to make it better:** we :heart: new ideas! We invite you to open a new [Issue](https://github.com/github/training-kit/issues) if you want to talk about it, or you can [fork this repository](https://help.github.com/articles/working-with-forks/) and submit your idea via a Pull Request.
 - **You just want to help:** check out the [open issues](https://github.com/github/training-kit/issues) for projects you can tackle, review an [open pull request](https://github.com/github/training-kit/pulls), or check out [the project ROADMAP](https://github.com/github/training-kit/projects/1).
 
@@ -21,8 +21,8 @@ For more information on contributing to this repository, check out our [CONTRIBU
 
 This repository contains three primary resources:
 
-- Our current [on-demand courses](https://services.github.com{{site.baseurl}}/) can be found in the [paths directory](/paths)
-- The translations of our popular [Git Cheat Sheets](https://services.github.com{{site.baseurl}}/downloads/github-git-cheat-sheet.pdf) can be found in the [downloads directory](/downloads). We're always looking for more. _P.S._ Right now the PDF generation is a manual process so please mention @github/services-training for assistance in getting your translation moved to the PDF.
+- Our current [on-demand courses](https://services.github.com/on-demand/) can be found in the [paths directory](/paths)
+- The translations of our popular [Git Cheat Sheets](https://services.github.com/on-demand/downloads/github-git-cheat-sheet.pdf) can be found in the [downloads directory](/downloads). We're always looking for more. _P.S._ Right now the PDF generation is a manual process so please mention @github/services-training for assistance in getting your translation moved to the PDF.
 - The recommended Training Path can be found [here](https://services.github.com/resources/learning-path/).
 
 ## Our Content Philosophy
@@ -47,7 +47,7 @@ To perform a build of the materials perform the following:
 
 1. Run `script/setup`
 1. Run `script/server`.
-    - When successful, the script will initiate a local server at `http://127.0.0.1:4000{{site.baseurl}}`.
+    - When successful, the script will initiate a local server at `http://127.0.0.1:4000/on-demand/`.
 1. Simply paste that into your favorite web-browser and you will be ready to test.
 1. You'll also need to run the following script to compile the SCSS (you can remove the `watch` flag if desired):
 ```
@@ -69,7 +69,7 @@ If you'd like to have a copy of the files to be served from a web server inside
 Site content is licensed under [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/). CC-BY-4.0 gives you permission to use content for almost any purpose but does not grant you any trademark permissions, so long as you note the license and give credit, such as follows:
 
 > Content based on
-> <a href="https://services.github.com{{site.baseurl}}/">services.github.com{{site.baseurl}}</a>
+> <a href="https://services.github.com/on-demand/">services.github.com/on-demand/</a>
 > used under the
 > <a href="https://creativecommons.org/licenses/by/4.0/">CC-BY-4.0</a>
 > license.</a>

_config.yml

@@ -78,7 +78,9 @@ include:
 - _stylesheets
 - _javascript
 sass:
-  sass_dir: assets/_scss
+  load_paths:
+    - assets/_scss
+    - node_modules
   style: :compressed
 
 # Custom site configuration

_includes/activity/gh-pages/02-create-profile.md

@@ -30,5 +30,5 @@ Don't worry if you don't want to put your actual information up online. It's OK
   {{ activity-text | markdownify }}
 </div>
 
-Need help? **Open an issue** [in our class repository](https://github.com/githubschool{{site.baseurl}}-github-pages/issues/new) for answers from GitHub trainers!
+Need help? **Open an issue** [in our class repository](https://github.com/githubschool/on-demand-github-pages/issues/new) for answers from GitHub trainers!
 {: .notice--success}

_includes/activity/gh-pages/03-create-new-page.md

@@ -15,5 +15,5 @@ Time to add our work history as a page to our Jekyll site.
   {{ activity-text | markdownify }}
 </div>
 
-Need help? **Open an issue** [in our class repository](https://github.com/githubschool{{site.baseurl}}-github-pages/issues/new) for answers from GitHub trainers!
+Need help? **Open an issue** [in our class repository](https://github.com/githubschool/on-demand-github-pages/issues/new) for answers from GitHub trainers!
 {: .notice--success}

_includes/activity/gh-pages/04-more-content.md

@@ -24,5 +24,5 @@ You might also look into the "collections" functionality in Jekyll. This would l
   {{ activity-text | markdownify }}
 </div>
 
-Need help? **Open an issue** [in our class repository](https://github.com/githubschool{{site.baseurl}}-github-pages/issues/new) for answers from GitHub trainers!
+Need help? **Open an issue** [in our class repository](https://github.com/githubschool/on-demand-github-pages/issues/new) for answers from GitHub trainers!
 {: .notice--success}