Let's say I have a page footer made of navigation hyperlinks to my site's pages. This footer is seen in all the other pages of my site.
The common sense says it must go in a style element or in an overridden page element if one is to reach the economy factor that a CMS is supposed to offer. Based on the above style organisation, what if one would like those navigation elements to grow or shrink as one is adding new pages and/or topics/articles. Then, this style would have to be dynamic, therefore should contain "code" to retrieve all the subtopics (for example) or all the pages (for example) under a hat topic or page. My point is that "no code should be put in style or page elements" in order to separate logic and presentation. My question is : how can we have at the same time relatively static styles that contain a small amount of logic to scan directories and be updated as new section are added or subtracted? I see as a big constraint the suggestion/best practice saying that all "coding" and dynamics should only go in page "content" by referring to it with "<[content]>. Why is it a big constraint? Because page "content" becomes a big "melting pot" where everything disappears. Are there other tricks? What is tolerable as far as stretching the rule is concerned? Are there other ways to organize things? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
