Override node templates or new classes with dedicated templates?

Next topic

Author	Message
Tore Skobba	Thursday 06 November 2003 9:31:51 am Hi all My design strategy is to use as few node templates overrides as possible. Instead I make new content classes, and then genereal override templates for the new classes, this means that I do not have to override them on node level. But I have 4 very similar "folder" classes, that is classes consisting of a name, description and children of various type. I think this is better as I think it is easier to get an overview of the design of the site, secondly it allows for more flexibility as the various classes can be altered. Just wondering if anyone else have given any thought to this and have any recommandations. Cheers Tore
Marco Zinn	Thursday 06 November 2003 1:26:17 pm Yes, we thought about that, too. For example, we have several news folders, which we want to sort my date and display the "modified" date, while we do not want to print date for all other folders. Creating similar (or identycal) classes to override on class ID has some pro's and con's: + your authors can decide, which design they want, without having to temper the override.ini + you can introduce different fields as you need - when you want to make changes to one folder class, that you need for all, you must change all classes, as there is no option to inherit classes - when you want to change an existing object from one class to another (Folder Type 1 -> Folder Type 2), you will have some problems and probably must create a new object and move all children to the new object and then delete the old one. The other option is fiddling with the Database ;) Marco http://www.hyperroad-design.com

Author

Message

Thursday 06 November 2003 9:31:51 am

Hi all

My design strategy is to use as few node templates overrides as possible. Instead I make new content classes, and then genereal override templates for the new classes, this means that I do not have to override them on node level. But I have 4 very similar "folder" classes, that is classes consisting of a name, description and children of various type. I think this is better as I think it is easier to get an overview of the design of the site, secondly it allows for more flexibility as the various classes can be altered. Just wondering if anyone else have given any thought to this and have any recommandations.

Cheers
Tore

Marco Zinn

Thursday 06 November 2003 1:26:17 pm

Yes, we thought about that, too.
For example, we have several news folders, which we want to sort my date and display the "modified" date, while we do not want to print date for all other folders.

Creating similar (or identycal) classes to override on class ID has some pro's and con's:
+ your authors can decide, which design they want, without having to temper the override.ini
+ you can introduce different fields as you need

- when you want to make changes to one folder class, that you need for all, you must change all classes, as there is no option to inherit classes
- when you want to change an existing object from one class to another (Folder Type 1 -> Folder Type 2), you will have some problems and probably must create a new object and move all children to the new object and then delete the old one.
The other option is fiddling with the Database ;)

Marco
http://www.hyperroad-design.com