History for ZopeAsAnOfflineCMS

??changed:
-
brief description of what we are trying to do:

**constraints**

* design constraints for our Zope CMS system is that it not be involved in the Staging/Production environment (ZOPE - is considered Z2.py) 

* that all data that we send to the development and production boxes be rendered in XML (to be transformed by an XSLT)

* an easily usable/flexible interface into creating content objects (mainly: FAQs, biographies, keeping track of dictionary entries, and Partner information)

* preferably something that can be reused to some degree.

**issues**

* using ZOPE and wget in conjunction

  - issues we have been faced with

    - renaming files

* using ZOPE to dump rendered files to a filesystem

    - using rsync to sync between machines 

    - using robocopy to sync between machines

**ideas**

* writing our own deployment system
    
    - not based on any OS specific programs + 

    - 100% manual drive, no automatic helpers - 

    - 


- I can be reached at <a href="mailto:[email protected]">runyaga</a>