Re: [Radiant] New pages and page parts...
Most excellent. I must have missed that tag option. Thanks, -- Travis Bell [EMAIL PROTECTED] On 26-Jul-07, at 2:05 PM, James Thompson wrote: > This is possible already. In your layout call your part like this: > > > > I do it a good deal myself. > > > -James > > On Jul 26, 2007, at 3:55 PM, Travis Bell wrote: > >> Hey guys, >> >> I was just wondering something about the way Radiant deals with page >> parts. >> >> If I create a new page, wouldn't it be nice if I could have it >> inherit the page above its parts? What I mean is, a project I am >> working on now has a solid 50 or so pages... the way this site is >> setup, we have 5 parts per page... going through, 1 by 1 is awfully >> painful. >> >> I kinda thought that's what the "inherit" option was for in the >> Layout drop-down but it doesn't seem to do this behavior. >> >> Thanks guys, >> >> >> -- >> Travis Bell >> [EMAIL PROTECTED] >> >> >> >> >> >> ___ >> Radiant mailing list >> Post: Radiant@lists.radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >> > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] New pages and page parts...
Ya, on a small site I would use snippets as well, but we have one client in particular who's site has 50 some pages all with per custom footers and keywords... creating 100 different snippets sounds like a bit of a headache to manage :) Cheers, -- Travis Bell [EMAIL PROTECTED] On 26-Jul-07, at 2:07 PM, Kyle Daigle wrote: > I accomplish most of this with snippets, but I guess in terms of > having > clients editing the page it would make more sense to move them into > page > parts. > > Thanks! I'd be interested in hear however anyone else is using them. > > > On 7/26/07 1:05 PM, "Travis Bell" <[EMAIL PROTECTED]> wrote: > >> We're using them for 2 primary reasons. >> >> 1) The obvious "body" and "sidebar" >> 2) For some SEO stuff... custom, per page meta keywords, footers >> etc... >> >> There could be other ways of doing this but this works incredibly >> well and have found it to be the best way our client can understand >> where to go to edit each element ie. keeps the body and sidebar areas >> pretty lean and less chance of them messing shit up :) >> >> Cheers, >> >> >> -- >> Travis Bell >> [EMAIL PROTECTED] >> >> >> >> >> >> On 26-Jul-07, at 1:57 PM, Kyle Daigle wrote: >> >>> Could someone quench my curiosity and explain the format that would >>> require >>> 5 page parts (besides maybe for a custom extension)? I'm not sure >>> I fully >>> understand their usefullness and feel like I'm missing out. >>> >>> Thanks everyone. >>> >>> >>> On 7/26/07 12:55 PM, "Travis Bell" <[EMAIL PROTECTED]> wrote: >>> Hey guys, I was just wondering something about the way Radiant deals with page parts. If I create a new page, wouldn't it be nice if I could have it inherit the page above its parts? What I mean is, a project I am working on now has a solid 50 or so pages... the way this site is setup, we have 5 parts per page... going through, 1 by 1 is awfully painful. I kinda thought that's what the "inherit" option was for in the Layout drop-down but it doesn't seem to do this behavior. Thanks guys, -- Travis Bell [EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant >>> >>> -- >>> >>> Kyle Daigle >>> DigitalWorkbox >>> [EMAIL PROTECTED] >>> C: 860.324.8173 >>> >>> ___ >>> Radiant mailing list >>> Post: Radiant@lists.radiantcms.org >>> Search: http://radiantcms.org/mailing-list/search/ >>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >> >> ___ >> Radiant mailing list >> Post: Radiant@lists.radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > -- > > Kyle Daigle > DigitalWorkbox > [EMAIL PROTECTED] > C: 860.324.8173 > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] New pages and page parts...
In a site I'm working on, I have a page that displays a list of football teams. Each team is a hidden child of the page "Teams". In the Teams page i loop through all its children and I display : * with a h2 the team name (title of the page), * with a h3 the short-description (page part called description), * with a 'p' the story (page part called story) * with another 'p' the team players (page part called players) I used DefaultPageParts extension for the Team page...each time my client click on the add-child button, he has a new page with the 4 default page parts created. Il giorno 26/lug/07, alle ore 21:57, Kyle Daigle ha scritto: > Could someone quench my curiosity and explain the format that would > require > 5 page parts (besides maybe for a custom extension)? I'm not sure > I fully > understand their usefullness and feel like I'm missing out. > > Thanks everyone. > > > On 7/26/07 12:55 PM, "Travis Bell" <[EMAIL PROTECTED]> wrote: > >> Hey guys, >> >> I was just wondering something about the way Radiant deals with page >> parts. >> >> If I create a new page, wouldn't it be nice if I could have it >> inherit the page above its parts? What I mean is, a project I am >> working on now has a solid 50 or so pages... the way this site is >> setup, we have 5 parts per page... going through, 1 by 1 is awfully >> painful. >> >> I kinda thought that's what the "inherit" option was for in the >> Layout drop-down but it doesn't seem to do this behavior. >> >> Thanks guys, >> >> >> -- >> Travis Bell >> [EMAIL PROTECTED] >> >> >> >> >> >> ___ >> Radiant mailing list >> Post: Radiant@lists.radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > -- > > Kyle Daigle > DigitalWorkbox > [EMAIL PROTECTED] > C: 860.324.8173 > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant - Andrea Franz [EMAIL PROTECTED] http://bigchieflabs.com/blog/ http://think.bigchief.it ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] New pages and page parts...
I don't know about five, but with inheritance I suppose you could get to that point. I use two to separate main content from contextual sidebar material. I suppose if you have more extensive regions that you needed to have available for customization you could get to a fair number of page parts. -James On Jul 26, 2007, at 3:57 PM, Kyle Daigle wrote: > Could someone quench my curiosity and explain the format that would > require > 5 page parts (besides maybe for a custom extension)? I'm not sure > I fully > understand their usefullness and feel like I'm missing out. > > Thanks everyone. > > > On 7/26/07 12:55 PM, "Travis Bell" <[EMAIL PROTECTED]> wrote: > >> Hey guys, >> >> I was just wondering something about the way Radiant deals with page >> parts. >> >> If I create a new page, wouldn't it be nice if I could have it >> inherit the page above its parts? What I mean is, a project I am >> working on now has a solid 50 or so pages... the way this site is >> setup, we have 5 parts per page... going through, 1 by 1 is awfully >> painful. >> >> I kinda thought that's what the "inherit" option was for in the >> Layout drop-down but it doesn't seem to do this behavior. >> >> Thanks guys, >> >> >> -- >> Travis Bell >> [EMAIL PROTECTED] >> >> >> >> >> >> ___ >> Radiant mailing list >> Post: Radiant@lists.radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > -- > > Kyle Daigle > DigitalWorkbox > [EMAIL PROTECTED] > C: 860.324.8173 > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] New pages and page parts...
I accomplish most of this with snippets, but I guess in terms of having clients editing the page it would make more sense to move them into page parts. Thanks! I'd be interested in hear however anyone else is using them. On 7/26/07 1:05 PM, "Travis Bell" <[EMAIL PROTECTED]> wrote: > We're using them for 2 primary reasons. > > 1) The obvious "body" and "sidebar" > 2) For some SEO stuff... custom, per page meta keywords, footers etc... > > There could be other ways of doing this but this works incredibly > well and have found it to be the best way our client can understand > where to go to edit each element ie. keeps the body and sidebar areas > pretty lean and less chance of them messing shit up :) > > Cheers, > > > -- > Travis Bell > [EMAIL PROTECTED] > > > > > > On 26-Jul-07, at 1:57 PM, Kyle Daigle wrote: > >> Could someone quench my curiosity and explain the format that would >> require >> 5 page parts (besides maybe for a custom extension)? I'm not sure >> I fully >> understand their usefullness and feel like I'm missing out. >> >> Thanks everyone. >> >> >> On 7/26/07 12:55 PM, "Travis Bell" <[EMAIL PROTECTED]> wrote: >> >>> Hey guys, >>> >>> I was just wondering something about the way Radiant deals with page >>> parts. >>> >>> If I create a new page, wouldn't it be nice if I could have it >>> inherit the page above its parts? What I mean is, a project I am >>> working on now has a solid 50 or so pages... the way this site is >>> setup, we have 5 parts per page... going through, 1 by 1 is awfully >>> painful. >>> >>> I kinda thought that's what the "inherit" option was for in the >>> Layout drop-down but it doesn't seem to do this behavior. >>> >>> Thanks guys, >>> >>> >>> -- >>> Travis Bell >>> [EMAIL PROTECTED] >>> >>> >>> >>> >>> >>> ___ >>> Radiant mailing list >>> Post: Radiant@lists.radiantcms.org >>> Search: http://radiantcms.org/mailing-list/search/ >>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >> >> -- >> >> Kyle Daigle >> DigitalWorkbox >> [EMAIL PROTECTED] >> C: 860.324.8173 >> >> ___ >> Radiant mailing list >> Post: Radiant@lists.radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- Kyle Daigle DigitalWorkbox [EMAIL PROTECTED] C: 860.324.8173 ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] New pages and page parts...
This is possible already. In your layout call your part like this: I do it a good deal myself. -James On Jul 26, 2007, at 3:55 PM, Travis Bell wrote: > Hey guys, > > I was just wondering something about the way Radiant deals with page > parts. > > If I create a new page, wouldn't it be nice if I could have it > inherit the page above its parts? What I mean is, a project I am > working on now has a solid 50 or so pages... the way this site is > setup, we have 5 parts per page... going through, 1 by 1 is awfully > painful. > > I kinda thought that's what the "inherit" option was for in the > Layout drop-down but it doesn't seem to do this behavior. > > Thanks guys, > > > -- > Travis Bell > [EMAIL PROTECTED] > > > > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] New pages and page parts...
We're using them for 2 primary reasons. 1) The obvious "body" and "sidebar" 2) For some SEO stuff... custom, per page meta keywords, footers etc... There could be other ways of doing this but this works incredibly well and have found it to be the best way our client can understand where to go to edit each element ie. keeps the body and sidebar areas pretty lean and less chance of them messing shit up :) Cheers, -- Travis Bell [EMAIL PROTECTED] On 26-Jul-07, at 1:57 PM, Kyle Daigle wrote: > Could someone quench my curiosity and explain the format that would > require > 5 page parts (besides maybe for a custom extension)? I'm not sure > I fully > understand their usefullness and feel like I'm missing out. > > Thanks everyone. > > > On 7/26/07 12:55 PM, "Travis Bell" <[EMAIL PROTECTED]> wrote: > >> Hey guys, >> >> I was just wondering something about the way Radiant deals with page >> parts. >> >> If I create a new page, wouldn't it be nice if I could have it >> inherit the page above its parts? What I mean is, a project I am >> working on now has a solid 50 or so pages... the way this site is >> setup, we have 5 parts per page... going through, 1 by 1 is awfully >> painful. >> >> I kinda thought that's what the "inherit" option was for in the >> Layout drop-down but it doesn't seem to do this behavior. >> >> Thanks guys, >> >> >> -- >> Travis Bell >> [EMAIL PROTECTED] >> >> >> >> >> >> ___ >> Radiant mailing list >> Post: Radiant@lists.radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > -- > > Kyle Daigle > DigitalWorkbox > [EMAIL PROTECTED] > C: 860.324.8173 > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] New pages and page parts...
Could someone quench my curiosity and explain the format that would require 5 page parts (besides maybe for a custom extension)? I'm not sure I fully understand their usefullness and feel like I'm missing out. Thanks everyone. On 7/26/07 12:55 PM, "Travis Bell" <[EMAIL PROTECTED]> wrote: > Hey guys, > > I was just wondering something about the way Radiant deals with page > parts. > > If I create a new page, wouldn't it be nice if I could have it > inherit the page above its parts? What I mean is, a project I am > working on now has a solid 50 or so pages... the way this site is > setup, we have 5 parts per page... going through, 1 by 1 is awfully > painful. > > I kinda thought that's what the "inherit" option was for in the > Layout drop-down but it doesn't seem to do this behavior. > > Thanks guys, > > > -- > Travis Bell > [EMAIL PROTECTED] > > > > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- Kyle Daigle DigitalWorkbox [EMAIL PROTECTED] C: 860.324.8173 ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
