This is an opinion - based on some experience - it is not a rule, just a 
general guide line, mileage may vary...

>>
>>
>>Topic
>>-> Name ( Text?)
>>-> Description (HTML/Text)
>>-> Extra (HTML/Text)
>>-> Code (HTML/Text)
>>
>>Article
>>-> Extra1 (HTML/Text)
>>-> Extra2 (HTML/Text)
>>-> Extra3 (HTML/Text)
>>-> Abstract (HTML/Text)
>>-> Content (HTML/Text)
>>
** avoid putting code in topic/articles - as you lower level users 
should have access to this, and letting them play with code could be 
dangerous..
topic extra can be used for topic titles if you map topics->directories 
and articles->files

>>
>>Page / Page Element 
>>-> Content (HTML?,  Text?<[page/style element]>? ( Code - generally limited to ifs 
>or class method calls)
>>
** dont normally use page elements other than code init - it can get confusing

>>
>>Page Element (code init)
>>->Content (Code)  -- usually a small amount of code - calling/starting/loading a 
>class from mgd_snippet
>>
>>
>>
>>Style Element 
>>->Content (HTML?, Text?<[style element]>?)( Code - generally limited to ifs or class 
>method calls)
>>
Dont get too carried away with Style elements as doing page layout work 
with style elements can be difficult.

>>
Snippets = code, generally not html other than <[style element]> to 
include style elements from classes.
-- 1 snippet per class



regards
alan





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to