<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://blog.panmedia.com.jm" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>PanNotes - </title>
 <link>http://blog.panmedia.com.jm/node/50</link>
 <description></description>
 <language>en</language>
<item>
 <title>WYSIWYG or Not</title>
 <link>http://blog.panmedia.com.jm/wysiwyg-or-not</link>
 <description>&lt;p&gt;When delivering a &lt;acronym title=&quot;Content Management System&quot;&gt;CMS&lt;/acronym&gt; to a client a &lt;acronym title=&quot;What You See Is What You Get&quot;&gt;WYSIWYG&lt;/acronym&gt; editor can sometimes be the Achilles&amp;#8217; heel of the complete product. These editors were created as a means of allowing users to easily create HTML without actually &lt;em&gt;knowing&lt;/em&gt; HTML. While the intent is great they usually produce more problems than solutions. I actually agree with most of the sentiments in &lt;a href=&quot;http://www.mustardseedmedia.com/blog/2007/may/17/why_not_install_tinymce&quot;&gt;Why NOT to install TinyMCE&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;We do need to provide an easy way for users to update and create content on their website but the current breed of editors are not the solution. So what is? My thought on the matter has always been that users need to know at least a little bit about the system they are using. The CMS is not a word processor. It&amp;#8217;s a different paradigm and that needs to be communicated to the users.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://blog.panmedia.com.jm/wysiwyg-or-not&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <category domain="http://blog.panmedia.com.jm/node/48">Client-relations</category>
 <category domain="http://blog.panmedia.com.jm/node/50">CMS</category>
 <category domain="http://blog.panmedia.com.jm/node/51">Rich text</category>
 <comments>http://blog.panmedia.com.jm/wysiwyg-or-not#comment</comments>
 <pubDate>Fri, 25 May 2007 16:51:52 +0500</pubDate>
 <dc:creator>Nesta Campbell</dc:creator>
 <guid isPermaLink="false">49 at http://blog.panmedia.com.jm</guid>
</item>
</channel>
</rss>
