Mark out code describing template parts in README
Twitter account now @gettypo
Fix typo news date format with distance_of_time_in_words

When a blog is configured with the distance_of_time_in_words
date_format, the typo news feed on the dashboard crashes because
new_js_distance_of_time_in_words_to_now assumes a Time object that
responds to #utc.  But the _typo_dev.html.erb partial passes a date
object, which does not respond to #utc.

It would make sense to format just the date, but then we'd need to
update the translations to handle the date-only format.  Or perhaps
we'd could call show_dates_as_local_time() on the page, which uses
the browser's locale's date format and makes the server-rendered date
mostly irrelevant.

For now, fix the crash by converting the parameter to_time before
formatting it.
Fix latest posts date format with distance_of_time_in_words

The Latest Posts on the admin dashboard is showing
"distance_of_time_in_words" as the date of each post, because that
is what is configured as my blog's date format.  Elsewhere, this
date format is treated as a special case rather than a strftime format.

Format the date with display_date_and_time rather than directly calling
strftime on the date and time format of the blog.
Remove redundant cookie secret
Refactors almost all scopes to use Rails 3/4 style
Merge pull request #139 from slainer68/ar_scopes

Refactors almost all scopes to use Rails 3/4 style
Merge pull request #136 from mcary/fix-dashboard-date-format

Fix dashboard date formats
Merge pull request #135 from randomecho/copyedit-readme

Mark out code describing template parts in README
Adds secret token generation to existing blog
Update to Rails 3.2.12
Upgrading Gemfile.heroku to Rails 3.2.12
Fixes the secret token generation on an existing blog.

Moves the code to Admin:BaseController, cleans duplicate code.
Fixes issue #142.
Fixes a bug where already published articles publication date would be changed by autosave.

This issue was caused because editing an existing article creates a draft with a parent id so the existing article doesn't get updated with autosave before the user clicks on publish. The autosave mechanisme didn't check for an existing parent_id before updating the published_at field.

I wonder how I can add tests to this, any feedback appreciated.
Solves issue #141.
Closes issue #69
Prepare 6.1.4 release
Inicial commit
Portuguease translation
Para criar setup inicial usando Fruga
Bootstrap default layout for portuguease lang