From f8e816035878fa6bb62f56e81556dc6083b4f29d Mon Sep 17 00:00:00 2001 From: "Benjamin J. Balter" Date: Mon, 15 Apr 2013 11:56:46 -0400 Subject: [PATCH] clarify baseurl usage --- site/_posts/2012-07-01-upgrading.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/site/_posts/2012-07-01-upgrading.md b/site/_posts/2012-07-01-upgrading.md index 34c67f45..6f6e4bca 100644 --- a/site/_posts/2012-07-01-upgrading.md +++ b/site/_posts/2012-07-01-upgrading.md @@ -62,7 +62,9 @@ and add a new markdown file to it. To preview your new post, simply run the ### Baseurl Often, you'll want the ability to run a Jekyll site in multiple places, such as -previewing locally before pushing to a server. Jekyll 1.0 makes that easier with -the new `--baseurl` flag. Throughout your Jekyll site, simply prefix relative -url with `{{ site.baseurl }}` and Jekyll will swap in whatever you pass along -ensuring your links remain true in both environments. +previewing locally before pushing to GitHub pages. Jekyll 1.0 makes that easier +with the new `--baseurl` flag. Throughout your Jekyll site, simply prefix +relative urls with `{{ site.baseurl }}` and add the production `baseurl` to +your `_config.yml` file. When previewing locally, Jekyll will swap in whatever +you pass along via the `--baseurl` flag (most likely `/`), ensuring your links +remain true in both environments. \ No newline at end of file