Otherwise we see errors like this:

heroku run rake db:migrate
 !    Multiple apps in folder and no app specified.
 !    Specify app with --app APP.

Blog post requires:

• title
• content
• timestamps

Acceptance criteria:

• rake deploy:staging deploys current branch to staging.jbrunton.com.

Note: this will require postgres on production.

E.g. as per the Jekyll implementation of the site.

Pages have:

• title
• content

Use friendly_id to provide pretty urls.

Scenario: view posts

Given a blog post "Some Post" created yesterday
And a blog post "Another Post" created today
When I am on the page for blog posts
Then I should see the post "Some Post"
And I should see the post "Another Post"
And the first blog post should be "Another Post"

Testing is awkward because it's purely dependent on environment variables. It should be possible to construct admin users purely using FactoryGirl.

Count selectors:

page.should have_css(selector, count: count.to_i)

Generalize steps for resources

etc.

Acceptance criteria:

Given a blog post "Some Post" with content "lorem ipsum"
When I view the post "Some Post"
Then there should be the html "

lorem ipsum

"

It's not to elegant to read. Consider e.g. http://typeplate.com/

Possible font stack: Constantia, "Lucida Bright", Lucidabright, "Lucida Serif", Lucida, "DejaVu Serif", "Bitstream Vera Serif", "Liberation Serif", Georgia, serif;

There's no coverage for the markdown method on the BlogPostsHelper, yet coverage stats seem to be universally 100%. It's possible cucumber tests are being included in those metrics.

For when the permalink is edited, if a user visits a url with the incorrect title in the permalink then they should be redirected (based on the id) to the correct post

Should include 'only' yaml item.

As a user
I would like to view individual posts
So that I can read them more easily

Acceptance criteria:

Scenario: view post

Given a blog post "Some Post" with content "Lorem ipsum"
When I am on the page for the blog post "Some Post"
Then I should see the post "Some Post"
And I should see the text "Lorem ipsum"

A heroku deploy gem could be useful across projects. Suggested behavior:

• Allow optional development, staging and production heroku servers.
• deploy:development, deploy:staging and deploy:production would deploy to appropriate servers with varying behavior:
  • deploy:development would push HEAD directly
  • deploy:staging would push the tip of master to staging, provided it's not ahead of origin
  • deploy:production would push the tip of master to production, provided that it's not ahead of origin; and, if there is a staging server, providing it's not ahead of staging.

Config file could look something like this:

apps:
  development: jbrunton-com-development
  staging: jbrunton-com-staging
  production: jbrunton-com

checks:
  staging:
    behind: true
  production:
    behind: true
    staged: true

Could probably build on top of https://github.com/fastestforward/heroku_san

A few posts with lorem ipsum text will be sufficient

Seems to occur when assets are recompiled. Slow dev significantly:

Warning. Error encountered while saving cache 853427f86ce78bf493d1a0fa8323f631846cc6f0/_functions.scssc: can't dump anonymous class #<Class:0x007fa6d1da5730>

Acceptance criteria:

1. Blog posts should have a permalink field based on the title of the post
2. The url for each post should be in the form 'blog/id/permalink'

Each blog post listing should include only the first few paragraphs, up to some constant number of words.

Each listing should include a link to 'Continue Reading'.

Acceptance criteria:

Given a blog post "Some Post"
When I am on the page for blog posts
Then there should be a blog post "Some Post"
And it should have a link "Continue Reading" which links to the blog post "Blog Post"

Set a config variable to define valid admin user id

Pages should exist at the root level, rather than '/pages'.

Acceptance criteria:

• Passing CI on Travis running rspec and cucumber tests
• Pull requests tested automatically
• Travis CI sticker on readme

The user is an admin in all cases. Should be more fine-grained, and require the least permissions for each action.

Should include title and sign out links

As a user
I would like to see recent blog posts on the home page
So that I can easily browse recent content

Acceptance criteria:

Given a blog post "Some Post"
When I navigate to the home page
Then I should see the post "Some Post"

Acceptance criteria:

Given a blog post "Some Post"
When I am on the page for blog posts
Then there should be a blog post "Some Post"
And the title should link to the blog post "Some Post"

See: https://codeclimate.com/repos/52d2b00769568031da00c2c8/BlogPostsController

Acceptance criteria:

Given I am on the home page
Then I should see the text "Welcome!"

Notes:

• home page = root url

Running rake spec and rake cucumber execute without errors.

Add a 'login' page with this option instead.

Acceptance criteria:

Given a blog post "Some Post" created on "2013-05-01"
When I am on the page for blog posts
Then there should be the blog post "Some Post"
And its date should be "May 1, 2013"

Given a blog post "Some Post" created on "2013-05-01"
When I am on the page for the blog post "Some Post"
Then there should be the blog post "Some Post"
And its date should be "May 1, 2013"