slawosz / content-slice Goto Github PK

ContentSlice
============

A slice for the Merb framework.

------------------------------------------------------------------------------
   

To see all available tasks for ContentSlice run:

rake -T slices:content_slice

------------------------------------------------------------------------------

Instructions for installation:

file: config/init.rb

# add the slice as a regular dependency

dependency 'content-slice'

# if needed, configure which slices to load and in which order

Merb::Plugins.config[:merb_slices] = { :queue => ["ContentSlice", ...] }

# optionally configure the plugins in a before_app_loads callback

Merb::BootLoader.before_app_loads do
  
  Merb::Slices::config[:content_slice][:option] = value
  
end

file: config/router.rb

# example: /content_slice/:controller/:action/:id

add_slice(:ContentSlice)

# example: /:lang/:controller/:action/:id

add_slice(:ContentSlice, :path => ':lang')

# example: /:controller/:action/:id

slice(:ContentSlice)

Normally you should also run the following rake task:

rake slices:content_slice:install

------------------------------------------------------------------------------

You can put your application-level overrides in:

host-app/slices/content-slice/app - controllers, models, views ...

Templates are located in this order:

1. host-app/slices/content-slice/app/views/*
2. gems/content-slice/app/views/*
3. host-app/app/views/*

You can use the host application's layout by configuring the
content-slice slice in a before_app_loads block:

Merb::Slices.config[:content_slice] = { :layout => :application }

By default :content_slice is used. If you need to override
stylesheets or javascripts, just specify your own files in your layout
instead/in addition to the ones supplied (if any) in 
host-app/public/slices/content-slice.

In any case don't edit those files directly as they may be clobbered any time
rake content_slice:install is run.