|
Friday 15 October 2004 3:12:27 pm
What's the commonly accepted way for eZ publish to handle site settings? By this, I mean fairly static content. For instance: -- In the footer, the company needs to have their address displayed. I don't want to hardcode this into the template, in case they want to change it. So, were do I...put it? Where should this content get stored? -- If I make a standard site, it would be nice to let the user change the colors of the site from the admin interface. Just pick a color "scheme" from a drop down list. Etc. These things are content, but not like news articles, etc. They're "behind the scenes" content. I'm tempted to create a "Settings" object in the content root and just instantiate that by NodeID then read the attributes off it. It wouldhave attributes for "Footer Text" and "Color Scheme." To edit global site settings, the user could just edit that object and change what he/she wants to change. This object wouldn't be visible anywhere other than the admin side of the site. Any thoughts from anyone else? Deane
|