> 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.
You are right , but that why You will never make dynamic site. 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? Think about something like dynamic menu or something like that? In style element You can include snippet which contains the code for dynamic menu. And here it only depends on You how You will solve it. > 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? <(content)> displays that what is in page / subpage etc. There are many tricks , but the power of midgard IMHO is that as many solutions as persons using midgard. It really depends on what You need. Piotras --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
