dan
/
jekyll
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

hard wrap *all* the things!

This commit is contained in:
Benjamin J. Balter 2013-04-15 16:09:02 -04:00
parent 91bcb83c8a
commit 343d56dfe3
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
site/_posts/2012-07-01-upgrading.md
View File

@ -9,7 +9,9 @@ Upgrading from an older version of Jekyll? A few things have changed in 1.0.
<div class="note feature"> <div class="note feature">
<h5 mardown="1">Diving in</h5> <h5 mardown="1">Diving in</h5>
<p markdown="1">Want to get a new Jekyll site up and running quickly? Simply run `jekyll new [sitename]`, to create a new folder with a bare bones Jekyll site.</p> <p markdown="1">Want to get a new Jekyll site up and running quickly? Simply
run `jekyll new [sitename]`, to create a new folder with a bare bones
Jekyll site.</p>
</div> </div>
### The Jekyll Command ### The Jekyll Command
@ -83,5 +85,5 @@ previewing locally before pushing to GitHub pages. Jekyll 1.0 makes that easier
with the new `--baseurl` flag. Throughout your Jekyll site, simply prefix with the new `--baseurl` flag. Throughout your Jekyll site, simply prefix
relative urls with `{{ site.baseurl }}` and add the production `baseurl` to relative urls with `{{ site.baseurl }}` and add the production `baseurl` to
your `_config.yml` file. When previewing locally, Jekyll will swap in whatever your `_config.yml` file. When previewing locally, Jekyll will swap in whatever
you pass along via the `--baseurl` flag (most likely `/`), ensuring your links you pass along via the `--baseurl` flag (most likely `/`), ensuring your
remain true in both environments. links remain true in both environments.