Proclaim

Most Rails blogging tools include everything you could ever want, including things you don't. Proclaim tries to provide the simplest (yet beautiful) implementation of a blog you could want-- posts, comments, and subscriptions. It's not meant to be your entire website-- it's a mountable engine. Mount it where you want it, configure it, and you have a blog. It otherwise stays out of your way.

Proclaim stays minimal by making use of HTML5's contenteditable attribute. It also uses the Medium Editor clone by Davi Ferreira, in concert with Pavel Linkesch's Image Insert plugin tied to CarrierWave for image uploads.

Proclaim doesn't include any users or authentication. It was made to be able to work with whatever setup you're using. All that it requires is that your application has users and authentication (Devise is recommended). In Proclaim 0.4, authentication is also used as authorization. If a user is logged in, it can create/publish/edit/delete posts and edit/delete comments. If no user is logged in, it can only read posts and create comments.

More information about configuring Proclaim for your specific authentication scheme is given below.

Proclaim 0.5 works with Rails 4.2 and on, with Ruby 1.9.3 and on. Add it to your Gemfile with:

gem 'proclaim', "~> 0.5.6"

Run bundle install to install it.

After you've added Proclaim to your gemfile, you can install it with:

rails generate proclaim:install

The generator will install an initializer which describes all of Proclaim's configuration options. You should check those out, and change them if necessary. It will also mount Proclaim in your config/routes.rb at the path /blog.

Now run rake db:migrate

Include Proclaim in Javascript manifest file:

//= require proclaim

Include Proclaim in Stylesheet manifest file:

*= require proclaim

Proclaim sends emails when:

• A new subscription is added (A welcome email)
• A new comment is made on a post to which subscriptions exist
• A new post is made and subscriptions exist on the blog itself

Because of this, ensure that the mailer has default URL options in each environment. Here is a possible configuration for config/environments/development.rb:

config.action_mailer.default_url_options = { host: 'localhost', port: 3000 }

A default root path must also be defined in the application's routes:

root to: "home#index"

The Proclaim engine has a number of configurable parameters that mostly relate to tying the engine in with the rest of the site. Proclaim tries to be as unobtrusive as possible-- as mentioned above, it doesn't provide users or authentication. It does, however, require some concept of authors, expecting that they authenticate somehow, and posts will belong to whichever author publishes them.

All configuration items (and their defaults) follow:

Proclaim.author_class = "User"
Proclaim.author_name_method = :name
Proclaim.current_author_method = :current_user
Proclaim.authentication_method = :authenticate_user!
Proclaim.excerpt_length = 500
Proclaim.editor_toolbar_buttons = ['bold', 'italic', 'underline', 'anchor',
                                   'header1', 'header2', 'quote']
Proclaim.editor_whitelist_tags = %w(h1 h2 h3 h4 h5 h6
                                    div p blockquote
                                    ul ol li
                                    a b strong i u
                                    img figure
                                    pre sup sub br)
Proclaim.editor_whitelist_attributes = %w(class id style href title src alt
                                          align draggable)
Proclaim.mailer_sender = nil
Proclaim.secret_key = nil

• Proclaim.author_class

  The class to which posts belong. Changing this also changes the default Proclaim.current_author_method and Proclaim.authentication_method. For example, setting author_class = "Admin" changes the default current_author_method to be :current_admin, etc.

• Proclaim.author_name_method

  Method to obtain the name of the author. This should be a method on the author class.

• Proclaim.current_author_method

  Method to obtain the currently-authenticated user. This should be a method on the ApplicationController, and it should return nil if no user is currently authenticated.

• Proclaim.authentication_method

  ApplicationController method to verify that a user is authenticated, and if not, to redirect to some sort of authentication page.

• Proclaim.excerpt_length

  Maximum length for the excerpts shown on the posts index. The excerpts may be less than this, but will never exceed it.

• Proclaim.editor_toolbar_buttons

  The buttons to be displayed on the Medium Editor toolbar. For a full list of options, see the README for that project.

• Proclaim.editor_whitelist_tags

  A list of all HTML tags that are allowed in the post body.

• Proclaim.editor_whitelist_attributes

  A list of all HTML attributes that are allowed in the post body.

• Proclaim.mailer_sender

  The email address to use in the "from" field of all emails from Proclaim. If not specified (the default), the mailer's default params will be used, which means it should be set in your environment.

• Proclaim.secret_key

  The secret key to use for generating subscription tokens. Changing this will invalidate any tokens already generated.

Astute readers may note that the defaults corresponds to defaults from Devise (on the User class). If that's not your setup, all of these options can be changed in the initializer installed by rails generate proclaim:install.

Each of Proclaim's included views stores its associated page title in the content identifier :proclaim_title. In order to actually get that into one's page title, then, one must simply throw something like this in one's layout header:

<head>
	...
	<title><%= content_for :proclaim_title %></title>
	...
</head>

Proclaim can notify your main application when certain things happen. These are all configured in the initializer installed by rails generate proclaim:install.

To register callbacks for when a post is published, use after_post_published in the initializer, for example:

Proclaim.setup do |config|
	# Can specify multiple callbacks. You can use a Proc:
	config.after_post_published lambda { |p| puts "Post published: #{p.title}"}

	# Or you can use a block:
	config.after_post_published do |p|
		puts "Post published: #{p.title}"
	end
end

To register callbacks for when a comment is made, use after_new_comment in the initializer, for example:

Proclaim.setup do |config|
	# Can specify multiple callbacks. You can use a Proc:
	config.after_new_comment lambda { |c| puts "Comment made by #{c.author}"}

	# Or you can use a block:
	config.after_new_comment do |c|
		puts "Comment made by #{c.author}"
	end
end

To register callbacks for when a subscription is created, use after_new_subscription in the initializer, for example:

Proclaim.setup do |config|
	# Can specify multiple callbacks. You can use a Proc:
	config.after_new_subscription lambda { |s| puts "New subsciber: #{s.name}"}

	# Or you can use a block:
	config.after_new_subscription do |s|
		puts "New subsciber: #{s.name}"
	end
end

Proclaim was built to help you quickly develop an application that includes a blog. However, it shouldn't be in your way when you need to customize it. Since Proclaim is an engine, all of its views are packaged inside the gem. These views will get you started, and you can always implement new styles via CSS, but you may wish to change them completely. You can simply copy them into your application and alter them by using the generator:

rails generate proclaim:views