CMS Architecture Ideas/Help
I'm using zope to build some sites and building a UI that sits on top of zope for a non-ZMI user to edit content. (These are for all intent purposes static sites >> and the UI is for content editing / deleting / and occasionllay adding new content) Currently my architecture is setup like so: Folders used to represent the natural sitemap (i.e. about us, contact, products...) -- Within the folders are zpt pages -- or some other type of document where I'm storing the content. -- For example for the index.html for the about us page > that is a zpt > with all the content stored as properties of the zpt. I -- I've created propertes such as title / subtitle / body / bodycallout. Thus I use zpt for design and then use zpt w/ properties to store the content. (That's my two layers of content & design) Then for the UI, I expose those properites in form elements so they can be editied. (make sense?) So overall this is my architecture - but I'm looking for pros/cons of this setup? Any advice or insight?
participants (1)
-
JBeard@porternovelli.com