>> I think the benefits of using a dynamic CMS environment far outweigh the >> benefits of using a static html website.
>Though you make these two assertions, your e-mail contains no mention >of the benefits of a dynamic web site. Instead your e-mail contains >examples of by-passing known difficulties with dynamic web sites. Do I really need to list these benefits - even with the 100s of 1000s of websites out there - sites such as wikipedia, sourceforge, linux.com, linuxtoday.com etc all running off CMSs? Isn't Google Code itself a dynamic site? In anycase, I will take the bite. Here are list some of the benefits: Ability to include additional interactive components - example: conference slide shows, conference / event listings and calendar, community generated documentation, subject specific forums (besides the mailing lists), conference registration modules, podcasts registrations, single sign-on.... > As we are working on updating our web services at IMSc as well, I > would really like to know the benefits of dynamic web sites for a site > that is very infrequently edited by humans (some pages may be generated > by cron jobs). Having a dynamic CMS website does not in anyway prevent you from having portions of the website coming from other automated sources - cron jobs etc. To state what you will already know - there are some very capable CMSs out there - from large "enterprise-class" ones such as Liferay, Plone etc to the smaller ones such as Joomla. Some of these products content versioning, separate staging and production environments, workflow for managing content (including approvals) etc. Are we saying that not one of these environments is suitable for our use? I find that to be very bold and unsubstantiated claim. Thanks, Prem Kurian Philip _______________________________________________ To unsubscribe, email [email protected] with "unsubscribe <password> <address>" in the subject or body of the message. http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
