- A link to a website to calculate latitude and longitude
- Earlier direct link to a Github import section
- Earlier mention of CUSTOMIZATION.md

All these questions arose when I did my first website setup.

Thanks to @karinlag to report the out of date instructions.

Close #236.

Close #238.

took me a while to track it down ...

To avoid distracting folks with a large, in-your-face URL.  They can
always mouse over the link (or just click it) if they want to see
where it points.

I've also used a reference-style link.  The text we use for the link
and the URL we're pointing at are pretty orthogonal, so splitting them
up makes it easier to version each independently with a line-based
diff/merge tool like Git.  It's also easier to read the source text
without the long URL cluttering up the human-readable portion.

The import url needed '.git' on the end to function, and it wasn't immediately clear to me that "Check URL" was a button.

1.  Changed `lesson_repo` and `lesson_site` to `workshop_repo` and `workshop_site` in `_config.yml`.
2.  Updated `_includes/footer.html` to match.
3.  Updated docs in `README.md` to match.

Rationale is that this is the workshop repo, not a lesson repo, so we shouldn't use `lesson_` as a prefix for variables.

This reverts commit fa77a5ac, reversing
changes made to 5843bc4d.

On Fri, Jan 23, 2015 at 04:30:14AM -0800, Matt Burke (GitHub Staff) wrote:
> The importer was supposed to be setting the HEAD ref.  There was a
> race condition that prevented it from doing so in some cases.  I
> just pushed out an update that should fix this issue.  Please let me
> know if it's still not working.

So the issue we were working around with #143 should be fixed now.

Added note re: cloning using -b gh-pages.

1.  Modify README.md and other files to reflect use of GitHub Import.
2.  Modified URLs for shared files in `_include` files to get the right images and CSS.

This turned up #137: the CSS files for the workshop template, the main
website, and the lesson repository are all out of step and need to be
synchronized.  Once that is done, the URLs in the
`_includes/header.html` file should be updated

Add link for "below" installing ruby/github-pages, and disclaimer that these need to be installed, earlier in the document

This is based on swcarpentry/workshop-template@5451fb9c1 (Enumerating
setup/run instructions for installation test scripts, 2014-12-17).
Greg suggested he switch from "Students" to "Learners" because some
professors attend workshops as students but don't feel comfortable
being called students [1]?  Or something like that.  I don't mind
either way, so we'll just go with Greg's preference.

The addition of a "For" in the section headings seems like a good
change though, since it makes it clear that the noun in the heading
marks the intended audience for that section, not the intended
subject.

I went with 'Sentence case' titles because I think they're more
readable and it's easier to be consistent.  There are a number of
folks who agree with me [2,3], including (apparently) the Oxford Guide to
Style [4] (I'm ok with title case for book and organization titles ;).
Although the American Psychological Association perfers 'Title Case'
for the first two levels of headings as well [5].

[1]: https://github.com/swcarpentry/workshop-template/pull/89#issuecomment-67718126
[2]: http://www.snappysentences.com/sentence-case-v-title-case/
[3]: http://www.stickycontent.com/blog/are-you-team-title-case-or-team-sentence-case.php
[4]: http://ux.stackexchange.com/a/48620
[5]: http://blog.apastyle.org/apastyle/2012/03/title-case-and-sentence-case-capitalization-in-apa-style.html



Based-on-patch-by: Greg Wilson <gvwilson@third-bit.com>

Address issue reported by @willingc.

We should avoid mixing HTTP and HTTPS. For accomplish this we
are using `//` at the start of the links at the homepage so that
the same protocol is used. For that reason to preview/test the
links you need to launch a HTTP server.

Thanks to @aaren for reviews and comments.

When following the instructions, I tried to run `git push` to push my changes, but the local `gh-pages` branch was still tracking the upstream branch, rather the branch in the `origin` remote repository where I wanted it to go. This adds an explicit example to make sure you try to push to your own repo.