Re: [Radiant] How can i display a particular part of a page?
I think i didn't explain my problem so well. I want to display parts depending on the url. I have a page with e.g. 4 parts. This page will never be displayed as a whole, but only one part at a time. Or should i create one page for every part? Would this be a better solution? Thanks, Tino 2006/11/30, Sean Cribbs [EMAIL PROTECTED]: Use r:content part=parta / to display the part. If you want to create an anchor too, either put it in the first containing block of that part, or do something like this: div id=partar:content part=parta //div Sean Cribbs seancribbs.com On 11/30/06, Tino Breddin [EMAIL PROTECTED] wrote: Hi, i have several links which point to the same page but different parts like: a class=partlink href=/list#partaGo to part a of the list/a But i do not know how i manage to display the requested part. Can someone help? Bye, Tino ___ 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] How can i display a particular part of a page?
I think r:if_url / would fit my needs, but meanwhile your solution is should work, too. Thanks, Tino 2006/11/30, Sean Cribbs [EMAIL PROTECTED]: If you made the 'parts' into child pages, you could do this: r:children:each a class=partlink href=#r:slug /Go to part r:slug / of the list/a /r:children:each ... r:children:each div id=r:slug / r:content / /div /r:children:each Cheers, Sean On 11/30/06, Tino Breddin [EMAIL PROTECTED] wrote: I think i didn't explain my problem so well. I want to display parts depending on the url. I have a page with e.g. 4 parts. This page will never be displayed as a whole, but only one part at a time. Or should i create one page for every part? Would this be a better solution? Thanks, Tino 2006/11/30, Sean Cribbs [EMAIL PROTECTED]: Use r:content part=parta / to display the part. If you want to create an anchor too, either put it in the first containing block of that part, or do something like this: div id=partar:content part=parta //div Sean Cribbs seancribbs.com On 11/30/06, Tino Breddin [EMAIL PROTECTED] wrote: Hi, i have several links which point to the same page but different parts like: a class=partlink href=/list#partaGo to part a of the list/a But i do not know how i manage to display the requested part. Can someone help? Bye, Tino ___ 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 ___ 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] Our first site in Radiant, finally
Hi Loren,congratulations that you finished your site, while i am still working on my first radiant powered site :-) And it looks nice, too.Just in case you did't notice it yet, some links provided in the navigation bar above the header point to non existing parts of your site. Bye,Tino2006/11/1, Loren Johnson [EMAIL PROTECTED]: Our first site in Radiant is up and runningOur first site in Radiant is up and running. We've got lots of work still to do, but we're happy with the manageability of things in Radiant even after a chaotic and compressed release schedule: http://www.diopa.orgThe CMS we used before this for this site was ModX (php) which had a few very good things going for it: 1) feature rich and, 2) dead simple to implement exactly the visual design we wanted, 3) mature. However where it lacked and what ultimately pushed us over to Radiant, despite it's relative lack of features: 1) More enjoyable / simpler to use, 2) Ruby, 3) Rails.We hope to be building applications in Rails all next year and didn't want to be dragged down by a PHP legacy app. Available Behaviors UtilizedMailer Behavior,Search Behavior,RSS Feed Behavior,Redirect Behavior (just a code snippet grabbed from Sean here off the list) MUCH GRATITUDE TO EVERYONE WHO SET OFFERED THESE BEHAVIORS TO THE OPEN. We couldn't have gotten the site done in Radiant without at least this much of a jump start. Custom Behaviors / Global Tags CreatedCustom global tagsIn the course of getting what we needed out of Radiant for this release I hack-in the following custom tags They're all a little obscure and nothing genius going on so I won't bother explaining them -- if someone is interested in any more detail just ask: r:find_level level=r:section_namer:if_request_uri r:navigation_level level= iCal fed Calendar DisplayI also created a custom behavior called calendar including a set of tags and virtual pages for displaying a grouping of calendars fed from Google Calendar feeds. The Event and Calendar models are created and administered in another Rails app and database. If you go to: http://www.diopa.org/calendar/master/all you'll see it in action.This behavior needs to be revisited and implemented using page_virtual and such (for now I override find_page_by_url and manually parse the path to get parameters...), but hopefully I'll get a chance to clean it up into something self contained and worth sharing. Modsof anything outside the Vendor, Log and Public directoriesBeing the first attempt to seriously use Radiant much of my energy in this project was diverted to finding ways to stay out of the app directory. I want us to stay on track with Radiant as new releases are formulated. The only change I had to make was in /app/views/page/new.rhtmlwhere I added a row in the more...and included the published_at date such that it could be modified to reflect the correct date on content converted from the previous site.Wish List1. A new plugin system / page types (same thing, right?). How much I'd love to be able to be free to build madly and freely on top of Radiant without feeling like I was branching or going to need to create an auxiliary Rails app. 2. Page reordering andre-parenting so that I can3.A more sophisticated navigation generation tag or tags which has options for dynamically generating navigation based on the tree which would go hand and hand with arbitrary ordering of pages and probably a new page attribute or status to indicate whether an article should show-up in navigation or not. Thanks to everyone for the bits of help throughout. I hope that through continuing to improve this site we'll have some help and code to offer back to the community. Loren JohnsonFN Group[EMAIL PROTECTED]AIM: NL7XF ___Radiant mailing listPost: 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] Presentation PDF
On 9/29/06, Nathan Wright [EMAIL PROTECTED] wrote: I gave a presentation to our local Ruby/Rails meeting the other night, so I thought I'd post the slides here in case anyone is interested. It's pretty basic stuff, but it might help some who are new to Radiant. Hi, your presentation was great and would have been a good introduction for radiant users, like i was one a few days ago. I hope there will be some blogging about this. Bye, Tino ___ 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] How to add css styles to a website?
2006/9/20, John W. Long [EMAIL PROTECTED]: It's probably better to create a layout with a content type of text/css and put just the tag r:content / in the layout. Then create a page, assign the layout, and paste your css in the body part. Well, i figured out how to apply css to one page, but the children won't use the styles. I just don't get a site-wide css working with the possibilties radiant offers. How it works with a static css file is clear to me. Can someone give me a little more help :-) ? Thanks, Tino ___ 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] How to add css styles to a website?
Hi,thank for your help. I will test which method fits to me, probably editing the css file with my editor.Bye,Tino ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
