charrington - thanks for the detailed reply.
I'll try and reply to your points one by one:
I think the archival / deletion should be determined by the user. For example - I could choose to keep headlines on my news page for a certain time period, or say, the most recent 5 headlines regardless of age. Some ebsites update daily and others on less consistent intervals - so some sort of flexibilty makes some sense. Any article should automatically go into the archive as soon as it's published.
Terms like SOAP, XLST, WebDAV... they're all over my head so I can't comment on the programming side of things. I think it needs to be kept as simple as possible and what little tweaking I have done with php leads me to believe that a php-based CMS would work quite nicely... or one built on ColdFusion since Macromedia has a WYSIWYG editor available to those who aren't "coders".
If you want a good example of how my site should "function" then DO check out www.nba.com
and skip from one team to another. You'll see that the basic structure for every team is pretty much identical and it's all built on one db with one CMS (or so it would appear). The navigation and links are the same for every team, except for the name (team directory) and the theme each team's site uses.
Another excellent example would be www.clutchcity.net
which was built little by little by a guy who knows his stuff (or learned as he went along). The one major difference would be that I want my forum to be fully integrated within the site and use the same theme. Is it possible to have a forum within for your CMS which isn't a "phpBB add-on" which still requires "integration"? That it could be a part of the CMS that can be turned "on" or "off" - or would that require it to use the same db?
I have never successfully installed a CMS (played with typo3 and php-nuke in the past) so maybe I am asking for things that can't be done. If I am on the main page and want to view the story archive I'd want the url to look like www.sitename.com/archive
rather than http://www.sitename.com/index.php/?m...e=archive.php.
Is that a result of the webmaster not doing something right or is that a function of the CMS?
I think the webmaster should be able to login after the install and make a site tree that includes all the possible pages (except for updated news content) and then go back and fill them in later. I think that any CMS should come with a choice of templates that the webmaster can later design images to fit into as need be (header, footer, navigation in different sizes etc...) or would it be easier for the php file to include multiple html files (templates) into the page to create the theme?
Am I making sense? Chris - feel free to email me firstname.lastname@example.org
or ICQ 27022757 if you'd like to discuss this further or pick my brain to try and figure out what a novice webdesigner would like out of your product.