﻿<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Patrick Renner</title>
    <description>An inconsistently frequent mind dump on the exploits of a project manager. Sounds sexy doesn't it?</description>
    <link>http://www.engagesoftware.com/Blog/BlogId/14.aspx</link>
    <language>en-US</language>
    <managingEditor>prenner@engagesoftware.com</managingEditor>
    <webMaster>dotnetnuke@engagesoftware.net</webMaster>
    <pubDate>Sat, 04 Jul 2009 09:22:25 GMT</pubDate>
    <lastBuildDate>Sat, 04 Jul 2009 09:22:25 GMT</lastBuildDate>
    <docs>http://backend.userland.com/rss</docs>
    <generator>Blog RSS Generator Version 3.5.1.19887</generator>
    <item>
      <title>The FCKEditor for Content Administrators</title>
      <description>&lt;p&gt;At Engage we do a lot of cool work with websites, and when we hand-off the projects there is always a pang in my heart that I’m sure parents feel when they see their child off to summer camp for the first time. “Will the website survive all the bullies? I hope they don’t learn curse words (bad markup).” One of the major benefits to working with a content management system like &lt;a href="http://www.dotnetnuke.com" target="_blank"&gt;DotNetNuke&lt;/a&gt; is that you can distribute content administration privileges to users who wouldn’t normally manage a website. The tools DNN provides help to make editing content easy. But this can also lead to a website that looks like it is managed by multiple people with various ideas on what looks good (font sizes, font styles…).&lt;/p&gt;  &lt;p&gt;At Engage we utilize a number of tactics to help ensure that websites can be properly maintained after the hand-off from our implementation services to our customers ownership and management of their site. On my personal blog, I outlined some tricks we use to make the FCKEditor (the Rich Text Editor in DNN) really easy and fool-proof for content administrators. &lt;a title="Optimizing the FCKEditor for DNN" href="http://www.patrickrenner.com/Home/articleType/ArticleView/articleId/53/Optimizing-the-FCKEditor-for-DNN.aspx" target="_blank"&gt;Check out how to optimize the FCKEditor for DNN&lt;/a&gt; on my personal site. If you’re interested in some of the other tactics (hints: advanced skinning tricks, &lt;a title="Engage software is the Official Training provider for DNN" href="http://www.engagesoftware.com/Training.aspx" target="_blank"&gt;custom training&lt;/a&gt;…) we use, please contact us about how to make your DNN site really hum.&lt;/p&gt;</description>
      <link>http://www.engagesoftware.com/Blog/EntryId/211/The-FCKEditor-for-Content-Administrators.aspx</link>
      <author>prenner@engagesoftware.com</author>
      <comments>http://www.engagesoftware.com/Blog/EntryId/211/The-FCKEditor-for-Content-Administrators.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.engagesoftware.com/Blog/EntryId/211/The-FCKEditor-for-Content-Administrators.aspx</guid>
      <pubDate>Fri, 26 Jun 2009 13:52:24 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.engagesoftware.com/DesktopModules/Blog/Trackback.aspx?id=211</trackback:ping>
    </item>
    <item>
      <title>Module Support Process</title>
      <description>&lt;p&gt;We take pride in trying to offer professional products and services to the DotNetNuke community. In providing commercial modules, two components of the module define professionalism - the quality of the product, and the quality of the support.&lt;/p&gt;
&lt;p&gt;Recently we have done two things which we hope will continue to add to the overall quality of our modules (both the product and support).&lt;/p&gt;
&lt;ol&gt;
    &lt;li&gt;We're making our issue tracking system more transparent. With each release going forward, our modules will have a public facing road map and issues list. We're also opening up the issue tracking system (Gemini) to our user community. By doing this, we hope to engage our user community more fully and communicate more clearly the direction of our product development cycle. Check out our issues tracking system at &lt;a href="http://support.engagemodules.com"&gt;support.engagemodules.com&lt;/a&gt;&lt;/li&gt;
    &lt;li&gt;The Support page on engagemodules.com has been revamped to better define our process and the tools available for support and feedback. By making  the &lt;a href="http://www.engagemodules.com/Support.aspx"&gt;support page&lt;/a&gt; a one-stop-shop, we hope to make prodcut support as painless as possible.&lt;/li&gt;
&lt;/ol&gt;</description>
      <link>http://www.engagesoftware.com/Blog/EntryId/155/Module-Support-Process.aspx</link>
      <author>prenner@engagesoftware.com</author>
      <comments>http://www.engagesoftware.com/Blog/EntryId/155/Module-Support-Process.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.engagesoftware.com/Blog/EntryId/155/Module-Support-Process.aspx</guid>
      <pubDate>Wed, 13 Aug 2008 13:11:26 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.engagesoftware.com/DesktopModules/Blog/Trackback.aspx?id=155</trackback:ping>
    </item>
  </channel>
</rss>