rubyonrailsin

A Ruby and Rails talk

Thursday, March 11, 2010


Re: [Radiant-Dev] Solving the Radiant theme and template problem

by rubyonrailsin 0 comments

Tag


Share this post:
Design Float
StumbleUpon
Reddit

I know my biggest problem with layouts is the amount of code repetition, the first extension I ever used was nested_layouts.


Saves you defining your html meta etc tags for every layout.

On Thu, Mar 11, 2010 at 10:35 PM, John Long <johnwlong2000@gmail.com> wrote:
On Thu, Mar 11, 2010 at 8:08 AM, rubybox <voorruby@gmail.com> wrote:
> So what Im interested in is any experienced developer interested in
> this? Am I the only one so frustrated by this, or can we get together and
> create a working extension for this?

I talked to Chris Rankin yesterday about his Site Theme yesterday
discussed some modifications to his extension that would make it more
flexible in the way that you describe.
To me there are two major areas of improvement needed:

1. Making destruction of layouts, pages, and snippets optional

2. Creating a standard template specification that templates can
conform to (or not) at the author's discretion

The idea behind a standard template specification is that the names of
pages, page parts, snippets, and layouts should be consistent across
most templates. This would allow a high degree of reusability and make
theming much more flexible.

Chris was excited about both ideas but could probably use some help
with the implementation. Also I think it would be good to get a
consensus from the community on what the standard template
specification should be.

--
John Long
http://wiseheartdesign.com
http://recursivecreative.com

--
Radiant CMS Dev Mailing List
Post:        radiantcms-dev@googlegroups.com
Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
Group Site:  http://groups.google.com/group/radiantcms-dev/

--
Radiant CMS Dev Mailing List
Post: radiantcms-dev@googlegroups.com
Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
Group Site: http://groups.google.com/group/radiantcms-dev/

No comments:

Post a Comment

Subscribe feeds via e-mail

Blog Archive