Skip to content
Blog module for Spina CMS.
Ruby HTML CSS JavaScript CoffeeScript
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
app
bin
config
db/migrate
lib
test
.gitignore
.travis.yml
Gemfile
Gemfile.lock
MIT-LICENSE
README.md
Rakefile
spina_blog.gemspec

README.md

Spina::Blog

Build Status

Blog module to add to Spina CMS.

Usage

Just add the gem file and run the rake task to install the migrations... and then run the migrations, obviously.

This will add an extra section to the 'website' navigation.

Justification

While blog posts are essentially just pages, they usually have a separate structure for date information. Rather than creating a bunch of pages, this plugin creates a scope called blog for the front-end, under which all the posts reside (using the standard /:year/:month/:day/:slug format).

Installation

Add this line to your application's Gemfile:

gem 'spina', '~> 0.12'
gem 'spina_blog', github: 'mattr/spina_blog'

And then execute:

$ bundle

Contributing

  1. Fork it ( https://github.com/mattr/spina_blog/fork )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request

In addition to contributing code, you can help to triage issues. This can include reproducing bug reports, or asking for vital information such as version numbers or reproduction instructions.

License

The gem is available as open source under the terms of the MIT License.

TODO

  1. Move the URL generation to use materialized_path.
  2. Add configuration options to allow alternate namespaces (e.g. news). (See branch: feature/namespaced-blogs)
  3. Allow multiple instances (e.g. news and blog). (See branch: feature/namespaced-blogs)
  4. Move field definitions to spina content types (i.e. spina_blog becomes a wrapper and custom routing module)
  5. Extract published_at and tags to separate content type gems (spina_datetime and spina_tags respectively)
You can’t perform that action at this time.