Jonathan, try the Page Definitions, have a look at them and let us know if they fit to your requirements.
Create a masterpage with a navigation list, create two page definitions, A is linking to foo.js in the head container, B is linking to bar.js. Pre-Assign thos two page-definitions to the navigation list. The Editor, who wants to create a new foundation page to the navigation list will be asked to choose between A or B. -alex On Dec 17, 11:21 am, Jonathan Frazier <[email protected]> wrote: > Nobody else has any comments? I find this very difficult to believe, > because it appears as if it restricts sites to: > > a) A very restrictive structure > b) A difficult to maintain structure, violating the DRY principle > c) Templates that require editors to perform a lot of setup work on > initial page creation > > Surely the 'big name' sites aren't putting up with this and have a > workaround ... > > On Dec 16, 3:00 pm, "Jonathan Frazier" <[email protected]> > wrote: > > > Maybe I have misunderstood - if you, or anyone else, can help clarify, it > > would be much appreciated! > > > I don't think containers would help to achieve the nicely structured setup I > > require. What I'd like is something along the following lines: > > > * A single 'top-level page' class/template/whatever. Let's say, for the > > purposes of simplicity, it has two containers: head and body. > > * Two further templates (or whatever they have to be) that share this > > overall structure, but have different content. E.g. template 1 has foo.js > > linked in the head, template 2 has bar.js. > > * Instances of each of those 2 templates can now be created > > > Is that possible using RedDot? > > > And, yes, I *am* a programmer :-) > > > 2008/12/16 <[email protected]> > > > > Mate, > > > you propably have not yet understood the most basic concept of RedDot > > > CMS, > > > where the templates-contentclass (yes, these have to be seen as a tuple) > > > construct is meant to represent a page (intentionally a web page). If you > > > want something alike "template inclusion" (weired - for RedDot know-wells) > > > you surely want to use the container construct. Obviously you might be a > > > kind of programmer or are actually a programmer or someone who is able to > > > write or understand programs and who is able to think on a more "abstract" > > > level - too "abstract" at all! Got it? > > > --Jörn > > > > It's only recently dawned on me that, apparently, you cannot include > > > one template from another in RedDot. I find this almost impossible to > > > believe since it's such a basic feature that every other inclusion > > > mechanism I've come across supports. > > > > Before I embark on a massive workaround, and get even more frustrated > > > with RedDot, is there something obvious I'm missing? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/RedDot-CMS-Users?hl=en -~----------~----~----~----~------~----~------~--~---
