Slate is the most elegant mountable blog engine that can be easily hooked up in the existing Rails application.
- Slick default design that can be easily customized.
- Markdown for everything.
- Drafts that make sense.
- Easy Google Analytics support.
- Akismet support for spam filtering in comments.
- Built-in social sharing with Facebook and Twitter.
- RSS support.
- Tags for posts.
- Photo uploading.
- Complete integration with Devise and CanCan.
- Tested with RSpec and FactoryGirl
- Uses haml, scss, CoffeeScript and Bootstrap for views.
1. Add the gem to your
2. Setup Routes
To hook up Slate routes to your current Rails app simply put this code in your
mount Slate::Engine, :at => '/blog'
You can obviously setup any route you want. E.g.
3. Run Slate Migrations
First off, install Slate migrations:
bundle exec rake slate:install:migrations
Then migrate your database:
bundle exec rake db:migrate
4. Devise and CanCan Setup
Slate relies on Devise and CanCan properly configured in your app. In short, the
current_user variable and CanCan
ability.rb file has to exist. You can setup permissions for the following Slate models:
can :manage, Slate::Post can :manage, Slate::Blog can :manage, Slate::Comment can :manage, Slate::Image
These particular rules will allow the specified user to do anything with any Slate record in the database.
5. Specify User Class Name
Lastly, you'll have to specify the name of your user model. Create a
config/initializers/slate.rb file and add the following line there:
Slate.user_class = "User" # other possibilities: "Author", "Writer", etc.
Slate's models and controllers are tested with RSpec and FactoryGirl. Rails engines, such as Slate, are normally tested with a dummy app that is located inside the 'spec' folder. Migrate your test database from the
rake db:migrate RAILS_ENV=test
Go back to the
slate directory and run
Fork the repo, do work, test it, pull request.