Mic92/blog
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Readme updates

Browse Source
This commit is contained in:
Brandon Mathis 2011-06-17 22:33:50 -04:00
parent 21813059f2
commit 765c15be62
1 changed files with 2 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.markdown
View File

@ -1,5 +1,5 @@
1. **It sports a clean responsive theme** written in semantic HTML5, focused on readability and friendliness toward mobile devices. 1. **Octopress sports a clean responsive theme** written in semantic HTML5, focused on readability and friendliness toward mobile devices.
2. **Octopress loves programmers.** Embed code (with [Solarized](http://ethanschoonover.com/solarized) styling) in your posts from gists or from your filesystem. 2. **Code blogging is easy and beautiful.** Embed code (with [Solarized](http://ethanschoonover.com/solarized) styling) in your posts from gists or from your filesystem.
3. **Third party integration is simple** with built-in support for Twitter, Pinboard, Delicious, Disqus Comments, and Google Analytics. 3. **Third party integration is simple** with built-in support for Twitter, Pinboard, Delicious, Disqus Comments, and Google Analytics.
4. **It's easy to use.** A collection of rake tasks simplifies development and makes deploying a cinch. 4. **It's easy to use.** A collection of rake tasks simplifies development and makes deploying a cinch.
5. **Get curated plugins.** Plugins are hand selected from the Jekyll community then tested and improved. 5. **Get curated plugins.** Plugins are hand selected from the Jekyll community then tested and improved.
@ -60,9 +60,6 @@ If you'd rather use [POW](http://pow.cx) to serve up your site, you can do this
### Configure Octopress ### Configure Octopress
http://gmarik.info/blog/2010/05/10/blogging-with-jekyll-and-heroku-for-free
http://jstorimer.com/2009/12/29/jekyll-on-heroku.html
Octopress keeps configurations in two places, the `Rakefile` and the `_config.yml`. Octopress keeps configurations in two places, the `Rakefile` and the `_config.yml`.
In the `rakefile` you'll want to set up your deployment configurations. In the `rakefile` you'll want to set up your deployment configurations.