From df46d6d7be45527eca73e68a4d47079b98e082c7 Mon Sep 17 00:00:00 2001 From: Ian Date: Thu, 24 Aug 2017 21:39:09 -0700 Subject: Updated the schemes in the sample links to HTTPS instead of HTTP HTTPS is now enforced for all URLs using github.io, e.g. userName.github.io must use https://userName.github.io You can no longer use HTTP:// as mentioned at the bottom of this blog post: https://github.com/blog/2186-https-for-github-pages --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 5d9e420..45c2020 100644 --- a/README.md +++ b/README.md @@ -22,7 +22,7 @@ In a few minutes you'll be set up with a minimal, responsive blog like the one b Fork this repo, then rename the repository to yourgithubusername.github.io. -Your Jekyll blog will often be viewable immediately at (if it's not, you can often force it to build by completing step 2) +Your Jekyll blog will often be viewable immediately at (if it's not, you can often force it to build by completing step 2) ![Step 1](/images/step1.gif "Step 1") @@ -30,7 +30,7 @@ Your Jekyll blog will often be viewable immediately at - if not, give it ten minutes as GitHub suggests and it'll appear soon +Making a change to _config.yml (or any file in your repository) will force GitHub Pages to rebuild your site with jekyll. Your rebuilt site will be viewable a few seconds later at - if not, give it ten minutes as GitHub suggests and it'll appear soon > There are 3 different ways that you can make changes to your blog's files: -- cgit v1.2.3