project 0.9.0 → 0.9.2

data/VERSION

@@ -1 +1 @@
-0.9.0
+0.9.2

data/lib/project/runner.rb

@@ -17,7 +17,6 @@ module Project
     
     def run!
       say "* Opening project '#{self.key}' using workflow '#{self.project.workflow}'"
-      seperator
       
       self.workflow.each_with_index do |command, index|
         command = Template.new(command, self.project).parse

data/project.gemspec

@@ -5,7 +5,7 @@
 
 Gem::Specification.new do |s|
   s.name = %q{project}
-  s.version = "0.9.0"
+  s.version = "0.9.2"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Josh Nesbitt"]

data/readme.rdoc

@@ -7,10 +7,13 @@
 * Note on Patches/Pull Requests
 
 
+
 == Overview
 
 Project aims to make working with multiple projects as simple as possible. By registering projects with workflows you can quickly create a set of commands that will be run against each project.
 
+
+
 == Installation
 
 The project is hosted on rubygems.org. Getting it is simple:
@@ -23,13 +26,17 @@ Once the gem is installed run:
 
 Assuming you haven't already had the gem installed this will create a file at ~/.project. This is the main configuration file used to drive project.
 
+
+
 == Usage
 
 Project uses a YAML file for its configuration. Edit the file located in at ~/.project to you liking.
 
+
+
 === Projects
 
-A project can be anything revolving around a particular context. A typical use would be opening your default environment surrounding a project. An example project configuration might look like this:
+A project can be anything revolving around a particular context. A typical use case would be opening your default environment surrounding a particular project. An example project configuration might look like this:
 
   :name:
     :path: /path/to/project
@@ -37,14 +44,25 @@ A project can be anything revolving around a particular context. A typical use w
 
 The only required key within a project is *workflow*. This is important as you need to tell project which workflow to apply against the project. Any other variables specified here will be passed through to a workflow (more on this below).
 
+
+
 ==== Workflows
 
-A workflow is a set of command you want run against a particular project. An example workflow might look something like this:
+A workflow is a set of commands you want run against a particular project. An example workflow might look something like this:
 
   :default:
     - cd %path
 
-A workflow is just a YAML array of templated commands. Any variable used in a workflow will get looked up on the project that is running it. In the example above the %path variable has been replaced by the path variable specified within the project. Using this method you can quickly build up a set of common workflows to use against any project.
+A workflow is just a YAML array of templated commands. Any variable used in a workflow will get looked up on the project that is running it. In the example above the %path variable has been replaced by the path specified within the project. Using this method you can quickly build up a set of common workflows to use against any project.
+
+
+=== Running a project
+
+Running a project is simple, just specify the name of the project you want to load and the workflow will run for it:
+
+  project name
+
+
 
 == Bugs
 

metadata

@@ -5,8 +5,8 @@ version: !ruby/object:Gem::Version
   segments: 
   - 0
   - 9
-  - 0
-  version: 0.9.0
+  - 2
+  version: 0.9.2
 platform: ruby
 authors: 
 - Josh Nesbitt