Hi there,
I am really impressed by the way EE can be updated to the newest version. With other CMSs, it’s really a painful procedure, which I prefer not to go through…
And that is why I was wondering how this rigid separation of “back-end” machine (EE) and “content” (website) could be possibly adapted for a dynamic data portal web site. We’ve developed that site ( http://geodata.grid.unep.ch ) over the last years; it gives UN organizations (and in principal: everybody) access to a broad range of data, with possibilities to draw maps, graphs and tables and to download the data in various formats.
Now, we’re thinking of developing an “opensource” package, which interested bodies (especially Environmental Ministries with whom we’re working) could download, install and use to serve/distribute their data.
But how would then the updating of these portals been done, when a new release (with new functionality or/and fixed bugs) appears? As they will surely customize the interface with some local pictures etc., it’s difficult for me as a non-professional-developer to understand how this could be achieved.
We’re working with PHP templates… so layout and functions are somewhat separated. But I guess this has to go much further, transforming our existing functions into PEAR libraries for example or using webservices for some of the dynamic stuff…
If anyone has a moment to give us a hint or two, that would be great!
Thanks a lot,
Stef
(PS: We’re using Linux, PHP, Postgres, Minnesota Mapserver and JpGraph.)
