Sean Cribbs said the following on 03/16/2009 11:39 AM: > I don't understand. Do you mean a Table of Contents?
Yes, but more than that. I realise my "subject" isn't quite right but I really don't know how to explain it in one line. Here's the business use-model: While many sites that list presentation and events have the speaker bio/background on the same page as the event, our board has decided that there will be ONE page that has ALL the speakers we have ever had listed, along with whatever else we can get, photos, contact etc. This means that has to be some way to link INTO that page from a remote page, in particular the page with the event on it. Yes, there needs to be a table of contents at the top of the page (which is updated as new speaker details are added), but I can figure that out. The index isn't the killer; referencing INTO the page is. As I said, my current idea is the page-per-speaker model and the <r:children:each> loop to build the page. This takes care of the browsable single page and the automatic update as new (child) pages get added. I think I can figure a ToC, but suggestions are welcomed. While I can figure the link from the presentation page to a single (child-of...) page for the speaker I can't figure out how to make that a reference INTO the page built by the <r:children:each> loop. I realise that I can actually have one page where the information is edited in and the ToC is built by hand and has the relevant markers to link to, but it seems a lot of hard work. I though CMSs were supposed to help you get around all that 'do-it-by-hand' stuff. -- The way that can be followed is not the Way The truth that can be told is not the Truth _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
