I'd recommend a virtual page. Check out how the archive pages work in Radiant.
Basically, you would create a JobPage page type that overrides, at the very least: 1) Page#virtual? to return true 2) Page#find_by_url to retrieve the Job for the requested id and store it in an instance variable for the page (let's say @job) 3) probably title, breadcrumb, and slug 4) some Radius tags to use in the body of the page that allow you to access the data in the @job instance variable You may also need to define a JobListingPage to be the parent to the JobPage and allow you to list links to the job pages. -Andrew On 10/3/07, James Hargreaves <[EMAIL PROTECTED]> wrote: > Hi everyone! > > I am asking the same question - is Radiant right for me? Obviously the > CMS capabilities are great, but I need to be able to serve some dynamic > content too - for instance - I have a load of jobs I need to list and > they need to be shown on a page as required: > > http://www.mydomain.com/jobs - all jobs > > http://www.mydomain.com/jobs/my-job-category - all jobs for the chosen > category > > http://www.mydomain.com/job/my-job - the job matching the selected id > > Obviously I can add an extension for storing the jobs info and I can > create a jobs page to show ALL jobs. But how do I make it so I can have > a dynamic directory under the 'jobs' page. I note this has been done on > two of the links Sean provides (http://www.thegroggysquirrel.com and > http://diopa.org). Well, I assume it has, either that or someone is > doing a lot of admin work keeping everything up-to-date. > > Any help would be appreciated... > > Thanks > Jay > > > Sean Cribbs wrote: > > Richard, > > > > Radiant does sound like a good fit. Simply because a lot of people use > > it for blog software doesn't mean it has to be that. Take a look at the > > various sites linked from the wiki page called RadiantUsers. There's a > > lot of sites that use the built-in templates (or modified versions) but > > there are also sites built from scratch. Radiant does especially well > > with "brochure-ware" sites because of the flexibility given to the > > content designer and its orientation toward mostly-static content. For > > reference, here are a few sites built by core-team members: > > > > Me: http://kckcc.edu (ignore the design, they screwed it up after I > > left) > > Daniel: http://www.thegroggysquirrel.com/ > > Loren: http://diopa.org > > > > Cheers, > > > > Sean > > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > > Radiant mailing list > Post: [email protected] > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
