[Zope-CMF] Multi-CMF-site development considerations

Ronald L Roeber rroeber1@unl.edu
Tue, 23 Apr 2002 09:38:22 -0500


This is a multipart message in MIME format.
--=_alternative 005060CE86256BA4_=
Content-Type: text/plain; charset="us-ascii"

All,

We are developing  a set of websites that will be used by 60 of our 
satellite offices. We are planning to use Zope-CMF.  Our first step will 
be to develop three or four sets of skins and add some portal_properties 
so that each of these satellite offices will be able to have their own 
(CMF) site. We will use a combination of  existing relational databases 
and Zope acquisition to provide institutional content. Each office CMF 
site will be used to store and manage local content that will be blended 
with relevant institutional content. Although the first version of this 
effort will be relatively modest, the first features will provide the 
local offices with the potential to produce much richer sites with much 
less effort. We would like to continue adding features in the future (CMF 
and those of our own development). So...

1. What should we be looking at as best practices to allow these sites to 
take advantage of future upgrades to CMF and Zope taking into account we 
will have 60 or more instances?
( we plan to place our custom skins on the file system)

2. Should we be looking at scripts or external methods to initialize new 
portal_properties? (office name, district affiliation, home-page 
preferences, skins, etc) are there considerations for future versions of 
CMF if we define our own properties.

I know this will work and work well. I've looked at a lot of information 
on the CMF site and mailing list. I would like to know how to approach 
this so that we have the best chance to grow with our user's expectations, 
CMF and Zope--not to mention minimizing our development time.

Thanks for any guidance.

--------------------------------------------------------------------
Ronald L. Roeber
CIT-IANR
University of Nebraska
Lincoln, NE 68583  Phone: (402) 472-5630
email: rroeber1@unl.edu 

--=_alternative 005060CE86256BA4_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">All,</font>
<br>
<br><font size=2 face="sans-serif">We are developing &nbsp;a set of websites that will be used by 60 of our satellite offices. We are planning to use Zope-CMF. &nbsp;Our first step will be to develop three or four sets of skins and add some portal_properties so that each of these satellite offices will be able to have their own (CMF) site. We will use a combination of &nbsp;existing relational databases and Zope acquisition to provide institutional content. Each office CMF site will be used to store and manage local content that will be blended with relevant institutional content. Although the first version of this effort will be relatively modest, the first features will provide the local offices with the potential to produce much richer sites with much less effort. We would like to continue adding features in the future (CMF and those of our own development). So...</font>
<br>
<br><font size=2 face="sans-serif">1. What should we be looking at as best practices to allow these sites to take advantage of future upgrades to CMF and Zope taking into account we will have 60 or more instances?</font>
<br><font size=2 face="sans-serif">( we plan to place our custom skins on the file system)</font>
<br>
<br><font size=2 face="sans-serif">2. Should we be looking at scripts or external methods to initialize new portal_properties? (office name, district affiliation, home-page preferences, skins, etc) are there considerations for future versions of CMF if we define our own properties.</font>
<br>
<br><font size=2 face="sans-serif">I know this will work and work well. I've looked at a lot of information on the CMF site and mailing list. I would like to know how to approach this so that we have the best chance to grow with our user's expectations, CMF and Zope--not to mention minimizing our development time.</font>
<br>
<br><font size=2 face="sans-serif">Thanks for any guidance.</font>
<br>
<br><font size=2 face="sans-serif">--------------------------------------------------------------------<br>
Ronald L. Roeber<br>
CIT-IANR<br>
University of Nebraska<br>
Lincoln, NE 68583 &nbsp;Phone: (402) 472-5630<br>
email: rroeber1@unl.edu <br>
</font>
--=_alternative 005060CE86256BA4_=--