]> https://diaryproducts.net/taxonomy/term/8/0 en https://diaryproducts.net/about/cms/zope_plone/zope_plone_sso_single_sign_on_windows_domain <div style="float:right;margin:1em"><a href="/node/16"><img src="/img_assist/gen/16&thumb=1" width="100" height="71" alt="Single-Sign-On for Zope & Plone in Windows Domains: SSO" /></a> </div> <div style="float:right;margin:1em"><a href="/node/14"><img src="/img_assist/gen/14&thumb=1" width="100" height="78" alt="Single-Sign-On for Zope & Plone in Windows Domains: Remote User Folder" /></a> </div> <p>One of my clients runs his own intranet for his employees. The intranet currently consists of a bunch of static HTML pages which are written and maintained by a single editor. This approach might have been sufficient five years ago but as the intranet grew it became apparent that the static HTML would become unmanageable in the near future. I therefore suggested replacing the existing solution with a community-oriented CMS. Due to certain requirements the set of contestants was cut down to two: <a href="http://www.drupal.org/">Drupal</a> and <a href="http://www.plone.org/">Plone</a>. I favored Plone because a) I am slightly disappointed with the direction and pace that Drupal&rsquo;s development has recently taken and b) I wanted to learn <a href="http://www.zope.org/">Zope</a> and Plone anyway. </p> Zope/Plone Webmaster Sat, 18 Dec 2004 21:22:37 +0000