+1 with Pascal's approach. Use Midgard to provide CMS and templating services. And include two php files for every Midgard 'page' (one from code-init, one from content).If I were you, I would not store it in the Midgard DB.
If you approach the CMS+templating system as a module, and your client-specific product info DB as another module, you want to ensure 'low coupling', and this approach carries teh lowest interdependancies I can think of.
For a more detailed description of the approach we take @ CWA New Media, see the last MWS or the 'Mix and Match' section in http://www.midgard-project.org/news/case%2Dmidgard%2Dframework.html
regards,
m
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
