Go to file
2009-10-31 23:17:29 -05:00
source updated rakefile to use FSSM in rake watch, generate a sitemap, and moved typography to a debug folder 2009-10-31 12:52:56 -05:00
_config.yml paramaterized feed, rsync deployment, and unified layouts 2009-10-20 08:50:16 -05:00
.gitignore added compass, added some basic stylesheets 2009-10-18 20:10:45 -05:00
config.rb added twitter feed to sidebar, moved to compass-edge gem 2009-10-30 00:31:02 -05:00
Rakefile fixed a few issues with the rakefile, and updated the readme 2009-10-31 23:17:29 -05:00
README.markdown fixed a few issues with the rakefile, and updated the readme 2009-10-31 23:17:29 -05:00
rubypants.rb improved starting point 2009-10-18 19:07:36 -05:00

What is Octopress?

Octopress gives developers a well designed starting point for a Jekyll blog. It's easy to configure and easy to deploy. Sweet huh?

Why?

  1. Building a Jekyll blog from scratch is a lot of work.
  2. Jekyll doesn't have default layouts or themes.
  3. Most developers don't want to do design.

Octopress is made of

  • Jekyll a blog aware static site generator (Henrik's fork adds HAML support)
  • Compass an awesome SASS framework.
  • FSSM + a rake task, automatically regenerates the blog as you work.
  • Serve for live previews of the site while in development
  • Rsync for easy deployment.

Setup

First, clone Octopress locally.

git clone git://github.com/imathis/octopress.git

Second, install required gems

sudo gem install henrik-jekyll
sudo gem install compass-edge
sudo gem install fssm
sudo gem install serve

Third

  1. Edit the top of the Rakefile settings to match your web hosting info.
  2. Edit the top of the atom.haml and _layout/default.haml

Usage

You should really read over the Jekyll wiki because most of your work will be using Jekyll. Beyond that Octopress is mostly some rake tasks, HAML, and SASS/Compass that has been meticulously crafted for ease of use and modification.

Rake tasks

rake preview: Generates the site, starts the local web server, and opens your browser to show the generated site.

rake watch: Watches the source for changes and regenerates the site every time you save a file. You'll forget your working with a static site.

rake deploy: Generates the site and then uses rsync (based on your configurations in the Rakefile) to synchronize with your web host. In order to use rsync you'll need shell access to your host, and you'll probably want to use your public key for authentication.

rake stop_serve: Kills the local web server process.

There are more but these are the ones you'll use the most. Read the Rakefile if you want to learn more