# Layouts [![Gem Version](https://badge.fury.io/rb/trusty-layouts-extension.svg)](http://badge.fury.io/rb/trusty-layouts-extension) Merges share_layouts and nested_layouts, making the whole layout adventure a lot more enjoyable ## Share Layouts ### Introduction Allows Rails controllers/actions to use Trusty CMS layouts as their "layout". content_for blocks are mapped to page parts, with the exception of :title and :breadcrumbs, which map to their specific default tags. The default content, or @content_for_layout, is mapped to the 'body' part. #### Inside a controller Controller SomeController < SiteController trusty_layout 'Layout name' # or trusty_layout { |controller| c.action_name == "index" ? "main" : "alt" } # and def delete @trusty_layout = 'delete' end end trusty_layout takes the same options as the built-in layout. To specifically override the Trusty CMS layout and use a standard Rails one use :layout => "mine", or :layout => false for no layout, as options to render. To choose a different Trusty CMS layout, set the @trusty_layout instance variable to the name of a Trusty CMS layout in your controller or view. ### Acknowledgments * Merged into radiant-layouts-extension, Dirk Kelly, August 2010 * Updated to work with 0.8 RC1 by: Johannes Fahrenkrug (http://springenwerk.com), May 22, 2009 * Created by: Sean Cribbs (seancribbs AT gmail DOT com), September 20, 2007 * Thanks to John Long for clarifying and simplifying the process for me! * Thanks to xtoddx for improving the tests and support for tags that use the request and response. * Thanks to Digital Pulp, Inc. for funding the initial development of this extension as part of the Redken.com project. ## Nested Layouts ### Introduction Nested Layouts enables reuse of a top-level "master" layout (one that contains your tags and the overall structure/wrapper of your site) for several different "nested" layouts (i.e. a one-column layout and a two-column layout). Keep your layouts DRY! A simple example is of the following wrapper and page layout

Hi

 This would render the following if Page Layout was called

Hi

### Acknowledgments * Merged into radiant-layouts-extension, Dirk Kelly, August 2010 * Original Source: http://github.com/moklett/radiant-nested-layouts-extension ## Haml Layouts [http://haml-lang.com/](http://haml-lang.com/) ### Introduction Write your layouts and radius tags in haml, with support for nested layouts and radius attributes // Parent Layout - with content/type set as 'haml' %div{:id=>"parent",:title=>""} %r:content_for_layout // Child Layout - with content/type set as 'haml' %r:inside_layout{:name=>"Parent"} %h2 %:title

some title

Integrates the work of [SaturnFlyer](http://github.com/saturnflyer) creating a haml_filter on pages and snippets. Additional task involved. changing the order which objects with this type are renders. The content is turned into html before the radius tags are passed. ### Acknowledgments * [SaturnFlyer](http://github.com/saturnflyer) [@SaturnFlyer](http://twitter.com/saturnflyer) (Jim Gay) | Original idea http://github.com/saturnflyer/radiant-haml_filter-extension * [Tissak](http://github.com/tissak) [@Tissak](http://twitter.com/tissak) (Tony Issakov) | Insisted that this was possible, and then wrote up an implementation in 10 minutes * [DirkKelly](http://github.com/dirkkelly) [@DirkKelly](http://twitter.com/dirkkelly) (Dirk Kelly) | Merged into radiant-layouts-extension and hooked page parse_object to support snippets and content haml radius tags