rubyonrailsin

Im working on a true thought structure of templates and snippets to
build a web 2.0 site.
It has CSS build from best practice using SASS, im using the blueprint
grid as a foundation. I could share this template with you guys if
interested we could modify it with several people
to get the best practice. Although I believe its already very flexible
and cool right at this moment.

I still have to implement nested layouts though for even more
flexibility.
Its still in progress if any interest let me post it to github in a
few days when im fully done with it.

On Mar 11, 5:01 pm, Chris Rankin <rankin.de...@gmail.com> wrote:
> Yeah I made the site_theme extension for a proprietary application. I had no
> intention on releasing it so it's not really built to satisfy the community
> needs. I fully plan on re-working it with the suggestions John made, but
> like he said I think it's a good idea to get more community feed back.
>
> Jim + Scott,
>
> Would you guys like to be added as contributors to my repo? That way we can
> have a central place to work on this extension, so we don't end up with 3
> totally different, versions.
>
> Also I'd really like to find a way to support single site installations,
> multi_site, and vhosts.
>
> Thanks,
>
> Chris
>
> On Thu, Mar 11, 2010 at 9:57 AM, [Square Talent] Dirk Kelly <
>
>
>
> dirk.ke...@squaretalent.com> wrote:
> > 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 <johnwlong2...@gmail.com>wrote:
>
> >> On Thu, Mar 11, 2010 at 8:08 AM, rubybox <voorr...@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.
>
> >>http://ext.radiantcms.org/extensions/207-site-theme
>
> >> 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/

--
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/