https://github.com/archan937/rich_cms

Enrichments (e9s) module for a pluggable CMS frontend
https://github.com/archan937/rich_cms

Last synced: about 2 months ago
JSON representation

Enrichments (e9s) module for a pluggable CMS frontend

• Host: GitHub
• URL: https://github.com/archan937/rich_cms
• Owner: archan937
• License: mit
• Created: 2010-07-20T19:51:26.000Z (over 14 years ago)
• Default Branch: master
• Last Pushed: 2011-06-28T21:59:59.000Z (over 13 years ago)
• Last Synced: 2024-10-03T08:48:28.584Z (3 months ago)
• Language: Ruby
• Homepage: http://codehero.es/rails_gems_plugins/rich_cms
• Size: 4.18 MB
• Stars: 42
• Watchers: 5
• Forks: 16
• Open Issues: 3
• Metadata Files:
  • Readme: README.textile
  • Changelog: CHANGELOG.rdoc
  • License: MIT-LICENSE

Awesome Lists containing this project

README

        

h1. Rich-CMS

A Rails gem (and also plugin) for a pluggable CMS frontend

h2. Introduction

Rich-CMS is a module of E9s ("http://github.com/archan937/e9s":http://github.com/archan937/e9s) which provides a frontend for your CMS content.

Please check out an online demo of Rich-CMS at the "Rich-CMS":http://codehero.es/rails_gems_plugins/rich_cms or "E9s":http://codehero.es/rails_gems_plugins/e9s page at "http://codehero.es":http://codehero.es.

h2. Installation

h3. Using Rich-CMS as gem in Rails 3

Add Rich-CMS in @Gemfile@ as a gem dependency:


  gem "rich_cms"



Run the following in your console to install with Bundler:


  bundle install



h3. Using Rich-CMS as gem in Rails 2

Add Rich-CMS in @environment.rb@ as a gem dependency:


  config.gem "rich_cms"



Run the following in your console:


  sudo rake gems:install



h2. Use the provided Rails generators

Rich-CMS requires one entity:

* An @ActiveRecord@ model used for CMS content storage

For (optional) authentication, Rich-CMS requires one of the following:

* A @Devise@ authenticated admin model

* A @Authlogic@ authenticated admin model

Fortunately, Rich-CMS is provided with two Rails generators with which you can generate those entities.

h3. CMS admin

h4. In Rails 3

Run the following in your console:


  rails g rich:cms_admin -m



*Note*: At default, it will create a ("Devise":http://github.com/plataformatec/devise powered) @User@ model, the @CreateUsers@ migration and it will configure your routes.

You can alter the class name as follows:


  rails g rich:cms_admin CodeHeroes::User -m



*Note*: Both generators have the @-m@ or @--migrate@ option which runs @rake db:migrate@ after creating the files.

*Using Authlogic*

You can use Authlogic by specifying the @-a@ or @--authlogic@ option:


  rails g rich:cms_admin CodeHeroes::User -a -m



*Note*: As mentioned earlier, Devise is the default authentication logic. Having that said, you can explicitly specify Devise with the @-d@ or @--devise@ option.

h4. In Rails 2

Run the following in your console:


  script/generate rich_cms_admin -m



*Attention*: The @Devise@ Rails generator code is (practically) a copy of the "Devise 1.0.9 generator code":https://github.com/plataformatec/devise/tree/v1.0.9/generators/devise. For there are problems calling the original Devise generators in Rails 2. See also this "Stackoverflow issue":http://stackoverflow.com/questions/3366508/couldnt-find-devise-install-generator-rails-2-3-8-devise-1-0-8.

h3. CMS content

h4. In Rails 3

Run the following in your console:


  rails g rich:cms_content -m



*Note*: At default, it will create the @CmsContent@ model and @CreateCmsContents@ migration. You can alter the class name with the following:


  rails g rich:cms_content CmsItem -m



h4. In Rails 2

Run the following in your console:


  script/generate rich_cms_content -m



In case you have used the Rails generators, you can skip the *Create required entities manually* section and go straight to *Render Rich-CMS in your views*.

h2. Create required entities manually

h3. Specify the authentication mechanism

Rich-CMS can be used without an authentication mechanism (which is the default by the way), you just have to open "/cms" in your browser and you are ready to go. But it is common to have authentication and Rich-CMS support "Devise":http://github.com/plataformatec/devise and "Authlogic":http://github.com/binarylogic/authlogic.

Provide the authentication logic as a symbol (e.g. @:devise@) and the authenticated class like this:


  Rich::Cms::Auth.setup do |config|

    config.logic = :devise

    config.klass = "User"

  end



The following specifications are optional as Rich-Cms uses defaults:

* @:inputs@ (default: @[:email, :password]@) - The attributes used for the login panel of Rich-CMS

* @:identifier@ (default: based on @inputs@) - The method used for displaying the identity of the current Rich-CMS admin (this is the first entry of @inputs@, so usually @:email@)

* @:current_admin_method@ (default: based on @klass@) - The controller method used to retrieve the current Rich-CMS admin (e.g. @current_user@ when configured @User@ as authenticated class)

h3. Register CMS content

Every type of content is identified with its correspending CSS selector (used by the jQuery based Javascript module of Rich-CMS). You will have to provide some specifications:

* @:class_name@ - The class of the CMS content model which contain the data

The following specifications are optional as Rich-Cms uses defaults:

* @:key@ (default: @:key@) - The key used for identification of content. You can also provide an array for a combined key (e.g. @[:key, :locale]@)

* @:value@ (default: @:value@) - The attribute which stores the value of the content instance.

* @:tag@ (default: @:div@) - The HTML tag used for content items.

* @:add@ (default: @[]@) - An array of the content item attributes included within the HTML attributes.

* @:before_edit@ (default: @nil@) - Javascript function called before showing the edit form of a content item.

* @:after_update@ (default: @Rich.Cms.Editor.afterUpdate@) - Javascript function called after update a content item.


  Rich::Cms::Engine.register(".cms_content", {:class_name => "Cms::StaticContent"})

  Rich::Cms::Engine.register(".i18n"       , {:class_name => "Translation", :key => [:key, :locale], :before_edit => "Rich.I18n.beforeEdit", :after_update => "Rich.I18n.afterUpdate"})



h2. Render Rich-CMS in your views

h3. Alter your layout

Add the following line at the beginning of the @@ tag:


  

    <%= rich_cms %>

    ...

  



h3. Use the Rich-CMS helper method

Rich-CMS requires a rendered DOM element provided with meta data of the content instance. Fortunately, you can call a helper method to render Rich-CMS content tags. Just specify the identifier of the content type and the key of the CMS content instance in question:


  >> key = "test_content"

  => "test_content"

  >> rich_cms_tag(".cms_content", key)

  => "
Hello world!
"



When using a combined key for content identification, just call it as follows:


  >> rich_cms_tag(".cms_content", {:key => key, :locale => I18n.locale})

  => "
Hallo wereld!
"



*Note*: In this case, the content was registered with @Rich::Cms::Engine.register(".cms_content", {:class_name => "Cms::StaticContent", :key => [:key, :locale]})@

The helper method is provided with the following options:

* @:as@ (default: auto-determine @:string@ or @:text@) - Specify the input type shown in the edit form (@:string@ for an input text, @:text@ for a textarea and @:html@ for a WYSIWYG HTML editor).

* @:tag@ (default: auto-determine @:div@ or @:span@) - The HTML tag used for content items.

* @:html@ (default: @{}@) - HTML attributes added to the content tag (e.g. @:id@, @:class@)


  ...

  <%= rich_cms_tag ".cms_content", "test_content", :as => :html %>

  <%= rich_cms_tag ".cms_content", {:key => "test_content", :locale => I18n.locale} %>

  ...



h3. Rich-CMS in your browser

Open "http://localhost:3000/cms":http://localhost:3000/cms, log in and start managing CMS content.

h2. Customizing the after update implementation

The @update@ action response of @Rich::CmsController@ is provided with "JSON":http://www.json.org data regarding the updated content item. The response will be passed to the @after_update@ Javascript function. Its default JSON data:


  {"__selector__": ".cms_content", "__identifier__": {"key": "test_paragraph"}, "value": "Hello world!"}



*Note*: @__selector__@ and @__identifier__@ are *always* provided in the JSON data.

When specifying a custom after update Javascript function, you probably want to acquire more information than provided in the default JSON data. You can customize this by defining the @to_rich_cms_response@ method in the CMS content model class:


  class Translation < ActiveRecord::Base


    def to_rich_cms_response(params)

      {:value => value, :translations => Hash[*params[:derivative_keys].split(";").uniq.collect{|x| [x, x.t]}.flatten]}

    end

  end



The JSON data provided will look like:


  {"__selector__": ".i18n", "__identifier__": {"locale": "nl", "key": "word.user"}, "value": "gebruiker", "translations": {"users": "gebruikers"}}



h2. Contact me

For support, remarks and requests please mail me at "[email protected]":mailto:[email protected].

h2. Credit

This Rails gem / plugin depends on:

jQuery


"http://jquery.com":http://jquery.com

Devise (optional)


"http://github.com/plataformatec/devise":http://github.com/plataformatec/devise

AuthLogic (optional)


"http://github.com/binarylogic/authlogic":http://github.com/binarylogic/authlogic

SASS


"http://sass-lang.com":http://sass-lang.com

Jzip


"http://codehero.es/rails_gems_plugins/jzip":http://codehero.es/rails_gems_plugins/jzip 


"http://github.com/archan937/jzip":http://github.com/archan937/jzip

RaccoonTip


"http://codehero.es/jquery_libraries/raccoon_tip":http://codehero.es/jquery_libraries/raccoon_tip 


"http://github.com/archan937/raccoon_tip":http://github.com/archan937/raccoon_tip

SeatHolder


"http://codehero.es/jquery_libraries/seat_holder":http://codehero.es/jquery_libraries/seat_holder 


"http://github.com/archan937/seat_holder":http://github.com/archan937/seat_holder

CLEditor


"http://premiumsoftware.net/cleditor/index.html":http://premiumsoftware.net/cleditor/index.html

h2. Contributors

Mark Mulder - "@bitterzoet":http://twitter.com/bitterzoet - "http://ikbenbitterzoet.com":http://ikbenbitterzoet.com

Stephan Kaag - "@stephankaag":http://twitter.com/stephankaag - "http://hollandonrails.nl":http://hollandonrails.nl

Jeroen Bulters – "@bulters":http://twitter.com/bulters – "http://bulte.rs":http://bulte.rs

Chris Obdam - "@chrisobdam":http://twitter.com/chrisobdam - "http://holder.nl":http://holder.nl

h2. ToDo's

* Support alternative ORM's and key/value stores (with "Toystore":https://github.com/newtoy/toystore and "Moneta":https://github.com/wycats/moneta probably)

* Check out compatibility with Devise 1.2.0

* Provide better conventions for content rendering

* Provide tools to use Textile, MarkDown, image files upload and models (e.g. products)

* Add cache feature which uses the standard Rails cache (rich_cms_tag ".cms_content", "test_content", :cache => true)

h2. Enrichments

The all-in-one gem at - "http://codehero.es/rails_gems_plugins/e9s":http://codehero.es/rails_gems_plugins/e9s - "http://github.com/archan937/e9s":http://github.com/archan937/e9s

h3. E9s modules

* Rich-CMS 
 "http://codehero.es/rails_gems_plugins/rich_cms":http://codehero.es/rails_gems_plugins/rich_cms 
 "http://github.com/archan937/rich_cms":http://github.com/archan937/rich_cms

* Rich-i18n 
 "http://codehero.es/rails_gems_plugins/rich_i18n":http://codehero.es/rails_gems_plugins/rich_i18n 
 "http://github.com/archan937/rich_i18n":http://github.com/archan937/rich_i18n

* Rich-pluralization 
 "http://codehero.es/rails_gems_plugins/rich_pluralization":http://codehero.es/rails_gems_plugins/rich_pluralization 
 "http://github.com/archan937/rich_pluralization":http://github.com/archan937/rich_pluralization

h2. License

Copyright (c) 2010 Paul Engel, released under the MIT license

"http://holder.nl":http://holder.nl - "http://codehero.es":http://codehero.es - "http://gettopup.com":http://gettopup.com - "http://twitter.com/archan937":http://twitter.com/archan937 - "[email protected]":mailto:[email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.