<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Plone</title>	<link>http://tc.eserver.org/dir/Plone</link>
	<description>A listing of the most recently indexed works about Plone in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Plone</title>
		<link>http://tc.eserver.org/dir/Plone</link>
	</image>
	<item>
		<title>Plone vs. SharePoint, Round 2: A By-Platform Feature Comparison</title>
		<link>http://tc.eserver.org/35567.html</link>
		<guid>http://tc.eserver.org/35567.html</guid>
		<description>An organization we at Reflab work with recently re-evaluated Plone against Sharepoint 2007; their main requirements are related to document management, where Sharepoint is for sure quite strong. What’s interesting is that they made the comparison also considering the different platforms and browsers their organization uses. Here are the results of their analysis and tests, they where so kind to share them with us, I checked them and translated them. I hope you’ll find them useful.</description>
	</item>
	<item>
		<title>Sitting on the Fence: Why I Sometimes Choose not to use Plone in Favour of Drupal or Wordpress</title>
		<link>http://tc.eserver.org/34374.html</link>
		<guid>http://tc.eserver.org/34374.html</guid>
		<description>As an experienced Plone front end developer, people are often surprised when I often decide not to use Plone, in favour of something like Drupal or Wordpress. I thought it would be useful to explain why and how I make this decision. I know some of these points won’t be popular in the Plone community, but they are based on experience, and think this blog post will be  useful to people deciding whether to use it or not.</description>
	</item>
	<item>
		<title>Plone vs. Microsoft Office Sharepoint Server (MOSS)</title>
		<link>http://tc.eserver.org/33549.html</link>
		<guid>http://tc.eserver.org/33549.html</guid>
		<description>CMS software selection with Plone and Microsoft Office Sharepoint Server (MOSS) as finalists seems to have become a pretty common case. This is true especially for “intranet/extranet” projects in which the primary focus is on web publishing and collaboration features.&#xD;&#xD;I’ve been asked several times to work on comparing the two and I’d like to share some of this experience. Also note that this can’t be a “vendor neutral” comparison because of my involvement in Plone; but I’ll do my best to highlight differences and strenghths of the two solutions.</description>
	</item>
	<item>
		<title>The Content Management Dilemna: Good Time to Revisit the Open Source CMS</title>
		<link>http://tc.eserver.org/33374.html</link>
		<guid>http://tc.eserver.org/33374.html</guid>
		<description>Open source delivers on the basics. The move to Plone delivered on the basic value proposition of open source: we got a very sturdy platform that worked well for our editors and didn&apos;t have to pay a dime in license fees. </description>
	</item>
	<item>
		<title>Acclaimed Science Magazine &quot;Discovers&quot; Plone</title>
		<link>http://tc.eserver.org/33376.html</link>
		<guid>http://tc.eserver.org/33376.html</guid>
		<description>DISCOVER Magazine, the magazine of science, technology and the future, recently launched a newly designed website on the open source Plone content management system (CMS).</description>
	</item>
	<item>
		<title>The Business Case For Web Content Management...and Why Plone</title>
		<link>http://tc.eserver.org/33214.html</link>
		<guid>http://tc.eserver.org/33214.html</guid>
		<description>Each situation is unique based on specific organizational needs and issues. Although the benefits may be difficult to quantify at times, at some point,  your company will simply decide that, ROI or not, it can&apos;t live any longer  with the (likely growing) pain of not effectively managing your content.</description>
	</item>
	<item>
		<title>Improving Plone and Zope Market Acceptance</title>
		<link>http://tc.eserver.org/33216.html</link>
		<guid>http://tc.eserver.org/33216.html</guid>
		<description>The worldwide ecosystem of interested parties involved in website and web application development has become enormous. Accordingly, there are few unifying themes among the various parties other than the mutual goal of having a “good” website as the final product. However the definition of what is good is entirely subjective. Many other requirements such as the ability to leverage existing resources and a desire to integrate the new project with existing enterprise applications contend for attention in the decision process. To get a clear idea of how we might increase the buzz and attention for Plone and Zope, let&apos;s profile some of the interested parties.</description>
	</item>
	<item>
		<title>Case Study: Discovering Plone Content Management System (Part 1)</title>
		<link>http://tc.eserver.org/32118.html</link>
		<guid>http://tc.eserver.org/32118.html</guid>
		<description>DISCOVER Magazine, one of the most widely read science mags in the US, had out grown its dated Web Content Management infrastructure for www.discovermagazine.com. Times were changing, multi-media was big and in general Web and CMS technology had moved forward significantly.&#xD;&#xD;After analyzing current needs and taking stock of the Web CMS landscape DISCOVER ultimately selected the open source Plone platform. This is a two-part series where we look at the CMS features which convinced DISCOVER to chose Plone.</description>
	</item>
	<item>
		<title>Rich Web Text Editing with Kupu</title>
		<link>http://tc.eserver.org/25567.html</link>
		<guid>http://tc.eserver.org/25567.html</guid>
		<description>Kupu is an open source application, written in JavaScript, that implements a flexible, full-featured HTML editor that runs in a web page without any special plugins. Its primary use is as an embedded editor in content management systems (CMS), like Zope or Plone, where it allows users to create their own web pages. Its design is flexible enough so that you can embed it into pretty much any web application without too much difficulty.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Plone.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>