A long time ago, John solicited contributions of "templates" with the opportunity for people to get them included in the main Radiant distribution. I think this is a fabulous idea and I'd like to reinitiate it. I'm going to up the ante some and say that the top submissions will get a Radiant T-shirt and/or other swag in addition to inclusion of their template in the core. I've been itching to get some tangible Radiant goods out anyway. I'll put this up on the Radiant site later and announce the link via the blog.
> I was thinking of a couple of things regarding the ongoing > documentation effort and the recent request for converting a static > website to a Radiant based site and this got me wondering.
> One of the questions that has been asked in the past is why Radiant > doesn't have any templates/ designs. Of course, I know the answer to > that - Radiant doesn't really care what you manage with it and every > site is unique and so, it doesn't offer anything.
> On the other hand, the 'Blog' is offered as an example that people > could use.
> If you think about it, Radiant is an absolutely fantastic replacement > for someone who wants to replace a static website such as a small > company website. In that case, would it make sense to add a couple of > other options to the db bootstrap - like 'small company website'. If > we do that, we could end up creating: > * A header and footer snippet > * A menu bar (standard top horizontal menu) > * Two layouts - one for the home page and one for a site page > * A stylesheet > * A few sections - Home, About Us, Press, Products, etc.
> This has a few advantages: > [1] This could be a very simple site and we can align to use some > standard accepted names for the CSS classes. That way, it gives > others a set of sections that they could design 'templates' for. A > 'template' might comprise a stylesheet and some graphics. > [2] It creates a more 'live' site that can simply be adopted and > adapted even by people who are less tech-savvy. Someone could install > it for them, and they can use it from there. The sample sections > would use just enough tags to help them get started.
> What do you think? Does someone have something that they can > contribute towards this?
On Mon, Sep 8, 2008 at 10:03 AM, Sean Cribbs <seancri...@gmail.com> wrote:
> Mohit,
> A long time ago, John solicited contributions of "templates" with the > opportunity for people to get them included in the main Radiant > distribution. I think this is a fabulous idea and I'd like to > reinitiate it. I'm going to up the ante some and say that the top > submissions will get a Radiant T-shirt and/or other swag in addition to > inclusion of their template in the core. I've been itching to get some > tangible Radiant goods out anyway. I'll put this up on the Radiant site > later and announce the link via the blog.
> Sean
> Mohit Sindhwani wrote: > > Hi Guys
> > I was thinking of a couple of things regarding the ongoing > > documentation effort and the recent request for converting a static > > website to a Radiant based site and this got me wondering.
> > One of the questions that has been asked in the past is why Radiant > > doesn't have any templates/ designs. Of course, I know the answer to > > that - Radiant doesn't really care what you manage with it and every > > site is unique and so, it doesn't offer anything.
> > On the other hand, the 'Blog' is offered as an example that people > > could use.
> > If you think about it, Radiant is an absolutely fantastic replacement > > for someone who wants to replace a static website such as a small > > company website. In that case, would it make sense to add a couple of > > other options to the db bootstrap - like 'small company website'. If > > we do that, we could end up creating: > > * A header and footer snippet > > * A menu bar (standard top horizontal menu) > > * Two layouts - one for the home page and one for a site page > > * A stylesheet > > * A few sections - Home, About Us, Press, Products, etc.
> > This has a few advantages: > > [1] This could be a very simple site and we can align to use some > > standard accepted names for the CSS classes. That way, it gives > > others a set of sections that they could design 'templates' for. A > > 'template' might comprise a stylesheet and some graphics. > > [2] It creates a more 'live' site that can simply be adopted and > > adapted even by people who are less tech-savvy. Someone could install > > it for them, and they can use it from there. The sample sections > > would use just enough tags to help them get started.
> > What do you think? Does someone have something that they can > > contribute towards this?
Looks great! As I've been working out the details for the contest, I've decided only original contributions (not ports) will be eligible for prizes, but if you can remove the requirement for the "settings" extension, we'll consider including it in the distribution. FYI, import_export templates are designed to be compatible with rake db:bootstrap.
Charlie Robbins wrote: > Hey All, > I've completed a port of the Scribbish > <http://quotedprintable.com/pages/scribbish> theme to Radiant, you can > check it out here: http://scribbish.levelglabs.com. I've been meaning > to do this for a while and Sean's post finally galvanized me into > doing it. Happy Theming!
> On Mon, Sep 8, 2008 at 10:03 AM, Sean Cribbs <seancri...@gmail.com > <mailto:seancri...@gmail.com>> wrote:
> Mohit,
> A long time ago, John solicited contributions of "templates" with the > opportunity for people to get them included in the main Radiant > distribution. I think this is a fabulous idea and I'd like to > reinitiate it. I'm going to up the ante some and say that the top > submissions will get a Radiant T-shirt and/or other swag in > addition to > inclusion of their template in the core. I've been itching to get > some > tangible Radiant goods out anyway. I'll put this up on the > Radiant site > later and announce the link via the blog.
> Sean
> Mohit Sindhwani wrote: > > Hi Guys
> > I was thinking of a couple of things regarding the ongoing > > documentation effort and the recent request for converting a static > > website to a Radiant based site and this got me wondering.
> > One of the questions that has been asked in the past is why Radiant > > doesn't have any templates/ designs. Of course, I know the > answer to > > that - Radiant doesn't really care what you manage with it and every > > site is unique and so, it doesn't offer anything.
> > On the other hand, the 'Blog' is offered as an example that people > > could use.
> > If you think about it, Radiant is an absolutely fantastic > replacement > > for someone who wants to replace a static website such as a small > > company website. In that case, would it make sense to add a > couple of > > other options to the db bootstrap - like 'small company > website'. If > > we do that, we could end up creating: > > * A header and footer snippet > > * A menu bar (standard top horizontal menu) > > * Two layouts - one for the home page and one for a site page > > * A stylesheet > > * A few sections - Home, About Us, Press, Products, etc.
> > This has a few advantages: > > [1] This could be a very simple site and we can align to use some > > standard accepted names for the CSS classes. That way, it gives > > others a set of sections that they could design 'templates' for. A > > 'template' might comprise a stylesheet and some graphics. > > [2] It creates a more 'live' site that can simply be adopted and > > adapted even by people who are less tech-savvy. Someone could > install > > it for them, and they can use it from there. The sample sections > > would use just enough tags to help them get started.
> > What do you think? Does someone have something that they can > > contribute towards this?
That's cool, it wasn't for the swag, just to get it done :). I can easily remove the requirement of settings, it just seemed like the easiest way to do title and subtitle. I was having some issues when using import_export. In the end, I removed the Users table portion of the .yml file. So now what happens is you bootstrap with "Empty" as the choice, so it only creates the admin user. Since all of the other tables don't have anything in them the db:import command works. To be consistent though, I'll try it again tonight and see if I can get it working right out of the box.
On Wed, Sep 10, 2008 at 12:29 PM, Sean Cribbs <seancri...@gmail.com> wrote: > Charlie,
> Looks great! As I've been working out the details for the contest, I've > decided only original contributions (not ports) will be eligible for prizes, > but if you can remove the requirement for the "settings" extension, we'll > consider including it in the distribution. FYI, import_export templates are > designed to be compatible with rake db:bootstrap.
> On Mon, Sep 8, 2008 at 10:03 AM, Sean Cribbs <seancri...@gmail.com> wrote:
>> Mohit,
>> A long time ago, John solicited contributions of "templates" with the >> opportunity for people to get them included in the main Radiant >> distribution. I think this is a fabulous idea and I'd like to >> reinitiate it. I'm going to up the ante some and say that the top >> submissions will get a Radiant T-shirt and/or other swag in addition to >> inclusion of their template in the core. I've been itching to get some >> tangible Radiant goods out anyway. I'll put this up on the Radiant site >> later and announce the link via the blog.
>> Sean
>> Mohit Sindhwani wrote: >> > Hi Guys
>> > I was thinking of a couple of things regarding the ongoing >> > documentation effort and the recent request for converting a static >> > website to a Radiant based site and this got me wondering.
>> > One of the questions that has been asked in the past is why Radiant >> > doesn't have any templates/ designs. Of course, I know the answer to >> > that - Radiant doesn't really care what you manage with it and every >> > site is unique and so, it doesn't offer anything.
>> > On the other hand, the 'Blog' is offered as an example that people >> > could use.
>> > If you think about it, Radiant is an absolutely fantastic replacement >> > for someone who wants to replace a static website such as a small >> > company website. In that case, would it make sense to add a couple of >> > other options to the db bootstrap - like 'small company website'. If >> > we do that, we could end up creating: >> > * A header and footer snippet >> > * A menu bar (standard top horizontal menu) >> > * Two layouts - one for the home page and one for a site page >> > * A stylesheet >> > * A few sections - Home, About Us, Press, Products, etc.
>> > This has a few advantages: >> > [1] This could be a very simple site and we can align to use some >> > standard accepted names for the CSS classes. That way, it gives >> > others a set of sections that they could design 'templates' for. A >> > 'template' might comprise a stylesheet and some graphics. >> > [2] It creates a more 'live' site that can simply be adopted and >> > adapted even by people who are less tech-savvy. Someone could install >> > it for them, and they can use it from there. The sample sections >> > would use just enough tags to help them get started.
>> > What do you think? Does someone have something that they can >> > contribute towards this?
Yes, neither way of exporting (/admin/export or import_export) produces a 100% compatible template, but they are not hard to massage into the correct form.
Charlie Robbins wrote: > That's cool, it wasn't for the swag, just to get it done :). I can > easily remove the requirement of settings, it just seemed like the > easiest way to do title and subtitle. I was having some issues when > using import_export. In the end, I removed the Users table portion of > the .yml file. So now what happens is you bootstrap with "Empty" as > the choice, so it only creates the admin user. Since all of the other > tables don't have anything in them the db:import command works. To be > consistent though, I'll try it again tonight and see if I can get it > working right out of the box.
> Charlie
> On Wed, Sep 10, 2008 at 12:29 PM, Sean Cribbs <seancri...@gmail.com > <mailto:seancri...@gmail.com>> wrote:
> Charlie,
> Looks great! As I've been working out the details for the > contest, I've decided only original contributions (not ports) will > be eligible for prizes, but if you can remove the requirement for > the "settings" extension, we'll consider including it in the > distribution. FYI, import_export templates are designed to be > compatible with rake db:bootstrap.
> Sean
> Charlie Robbins wrote: >> Hey All, >> I've completed a port of the Scribbish >> <http://quotedprintable.com/pages/scribbish> theme to Radiant, >> you can check it out here: http://scribbish.levelglabs.com. I've >> been meaning to do this for a while and Sean's post finally >> galvanized me into doing it. Happy Theming!
>> On Mon, Sep 8, 2008 at 10:03 AM, Sean Cribbs >> <seancri...@gmail.com <mailto:seancri...@gmail.com>> wrote:
>> Mohit,
>> A long time ago, John solicited contributions of "templates" >> with the >> opportunity for people to get them included in the main Radiant >> distribution. I think this is a fabulous idea and I'd like to >> reinitiate it. I'm going to up the ante some and say that >> the top >> submissions will get a Radiant T-shirt and/or other swag in >> addition to >> inclusion of their template in the core. I've been itching >> to get some >> tangible Radiant goods out anyway. I'll put this up on the >> Radiant site >> later and announce the link via the blog.
>> Sean
>> Mohit Sindhwani wrote: >> > Hi Guys
>> > I was thinking of a couple of things regarding the ongoing >> > documentation effort and the recent request for converting >> a static >> > website to a Radiant based site and this got me wondering.
>> > One of the questions that has been asked in the past is why >> Radiant >> > doesn't have any templates/ designs. Of course, I know the >> answer to >> > that - Radiant doesn't really care what you manage with it >> and every >> > site is unique and so, it doesn't offer anything.
>> > On the other hand, the 'Blog' is offered as an example that >> people >> > could use.
>> > If you think about it, Radiant is an absolutely fantastic >> replacement >> > for someone who wants to replace a static website such as a >> small >> > company website. In that case, would it make sense to add >> a couple of >> > other options to the db bootstrap - like 'small company >> website'. If >> > we do that, we could end up creating: >> > * A header and footer snippet >> > * A menu bar (standard top horizontal menu) >> > * Two layouts - one for the home page and one for a site page >> > * A stylesheet >> > * A few sections - Home, About Us, Press, Products, etc.
>> > This has a few advantages: >> > [1] This could be a very simple site and we can align to >> use some >> > standard accepted names for the CSS classes. That way, it >> gives >> > others a set of sections that they could design 'templates' >> for. A >> > 'template' might comprise a stylesheet and some graphics. >> > [2] It creates a more 'live' site that can simply be >> adopted and >> > adapted even by people who are less tech-savvy. Someone >> could install >> > it for them, and they can use it from there. The sample >> sections >> > would use just enough tags to help them get started.
>> > What do you think? Does someone have something that they can >> > contribute towards this?
