<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Ponderings and Wanderings &#187; Best Practice</title>
	<atom:link href="http://www.quis.com/category/business/best-practice/feed" rel="self" type="application/rss+xml" />
	<link>http://www.quis.com</link>
	<description>Dan Katz&#039;s thoughts on marketing, customer service, woodworking, his baby boy and other musings.</description>
	<lastBuildDate>Thu, 20 Oct 2011 13:02:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>How to go about selecting a CMS</title>
		<link>http://www.quis.com/2011/03/21/how-to-go-about-selecting-a-cms</link>
		<comments>http://www.quis.com/2011/03/21/how-to-go-about-selecting-a-cms#comments</comments>
		<pubDate>Mon, 21 Mar 2011 17:36:47 +0000</pubDate>
		<dc:creator>Dan Katz</dc:creator>
				<category><![CDATA[Best Practice]]></category>

		<guid isPermaLink="false">http://www.quis.com/?p=170</guid>
		<description><![CDATA[A client has come to us for analytics and other consulting.  We then found that they manage their rather large and complex site entirely via manual HTML edits. They know they need a better way and are considering content management systems.  Chatting with them I see they have not outlined in a formal manager the [...]]]></description>
			<content:encoded><![CDATA[<p>A client has come to us for analytics and other consulting.  We then found that they manage their rather large and complex site entirely via manual HTML edits. They know they need a better way and are considering content management systems.  Chatting with them I see they have not outlined in a formal manager the business requirements for the management of not just their website, but their entire digital framework. A good short list of needs that the team agrees upon should be the basis of evaluation and selection.  Here are some questions the business requirements should consider.</p>
<ul>
<li>What is the product road map of the CMS and how is it supported?  Does this match your corporate culture and comfort level.</li>
<li>How big is the site and what are particular feature and functional requirements?  Can the CMS package support these items that you currently utilize but also those that may be needed in the future?  For example, every site should expect to have a mobile and location-based requirement even if you do not have the current need.</li>
<li>What is the analytics package you will utilize?  Is this supported with tools to customize the metrics and settings within the CMS?</li>
<li>What technologies is your IT staff comfortable managing?  For that matter, do you have an IT staff or will this need to be managed by a partner?</li>
<li>How many people will need to manage the website?  Where will they be located?  Do you need a workflow for data entry, review and approval?</li>
<li>What tools that are in place will need to link to the CMS?  Email marketing, CRM, SEO, SEM, social media monitoring and engagement and others should all be able to integrate with the CMS. Existing partnerships, modules or other linkages will enable a more immediate and cost-effective hook up.</li>
<li>Will this be rolled out buy an internal team, external tam, partner or others and with what level of expertise?  This needs to be taken into consideration for the training and service options available?</li>
<li>What is the budget range for the initial phase and the eventual enterprise roll out? This is key as there is a wealth of options but many can be priced right out of the budget.</li>
</ul>
<p>Here are some other good reads regarding CMS Selection.</p>
<ul>
<li><a href="http://www.steptwo.com.au/papers/kmc_evaluate/index.html">http://www.steptwo.com.au/papers/kmc_evaluate/index.html</a> How to evaluate a content management system</li>
<li><a href="http://www.eimagazine.com/xq/asp/sid.0/articleid.2B3C1E09-EA4B-4281-B655-BBB4206C96EE/qx/display.htm">http://www.eimagazine.com/xq/asp/sid.0/articleid.2B3C1E09-EA4B-4281-B655-BBB4206C96EE/qx/display.htm</a> Recommended steps when outlining a CMS strategy</li>
<li><a href="http://www.techrepublic.com/article/defining-cms-content-requirements/1051942">http://www.techrepublic.com/article/defining-cms-content-requirements/1051942</a> Defining CMS content requirements</li>
</ul>
<p>This is just my short list of items?  What else should be added to this list of considerations?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.quis.com/2011/03/21/how-to-go-about-selecting-a-cms/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Best Practice: Website Ownership and Asset Control</title>
		<link>http://www.quis.com/2009/09/14/best-practice-website-ownership-and-asset-control</link>
		<comments>http://www.quis.com/2009/09/14/best-practice-website-ownership-and-asset-control#comments</comments>
		<pubDate>Mon, 14 Sep 2009 15:49:14 +0000</pubDate>
		<dc:creator>Dan Katz</dc:creator>
				<category><![CDATA[Best Practice]]></category>

		<guid isPermaLink="false">http://www.quis.com/?p=128</guid>
		<description><![CDATA[I am a big fan of The Bivings Report.  This is a great blog that demonstrates how an Interactive PR  agency can use a blog to create a useful collection of both thought leadership and down-and-dirty practical items.  A recent post, Buying a Website. The Seven Costly Questions That Are Often Overlooked,  directly addresses a lot [...]]]></description>
			<content:encoded><![CDATA[<p>I am a big fan of <a href="http://www.bivingsreport.com/">The Bivings Report</a>.  This is a great blog that demonstrates how an Interactive PR  agency can use a blog to create a useful collection of both thought leadership and down-and-dirty practical items.  A recent post, <a title="Site: The Bivings Report" href="http://feedproxy.google.com/~r/TheBivingsReport/~3/bzL5qXVHh2w/" target="_blank">Buying a Website. The Seven Costly Questions That Are Often Overlooked,<strong> </strong></a> directly addresses a lot of client hosting concerns that are often not voiced.</p>
<p>What Gary Bivings notes in his post matches to what I have frequently experienced.  <strong>Clients need to take a bit more ownership and responsibiltiy for the details behind campaign projects.</strong>  By all means I relish in being a trusted advisor.  However, clients must always think ahead as to the ownership of their materials. </p>
<p>Here are some additional items to the Bivings post to consider:</p>
<p><strong>Always keep it work for hire.</strong>  Be sure that you own 100% of the content, design, code and other materials.  Not just the end result.  If I am paying for materials, I believe the materials along the way have been paid for as well.  This means that the design files that make up the Web site should be delivered to me as well as the final Web site.</p>
<p>Example, I recommend any design contract call for the delivery of all Adobe Flash and Adobe Photoshop source files be delivered as part o the site launch.</p>
<p><strong>Know the permitted uses of image and media files.</strong>  We almost always purchase royalty free or restricted rights images for design efforts.  These are purchased for use in the Web site and then are usually not permitted for reuse in other projects.  Be sure that if you plan to adapt your Web imagery to other online or offline projects that you obtain the details on the permitted uses of these images.  And, that you obtain the images themselves and the details of where they were purchased.  By obtaining these details you can edit the image if needed and purchase the additional rights as well.</p>
<p><strong>Have hosting under your control.</strong>  Almost every agency provides some sort of level of hosting.  I recommend against this as a packaged service.  Instead I feel clients should contract with the hosting vendor (via the agency is fine) or provide the hosting.  The agency can then be provided the appropriate access and contracted for support as needed.  The key is that you retain administrative access to and control over the home for your materials. You then will never have to migrate the materials should you sever your relationship with the agency.</p>
<p><strong>Own the domain names.</strong>  Be sure that when your agency registers domain names that your company is listed as the administrator.  The agency can be the technical and even billing contact.  However, if you are not the administrator then you are tied to the agency to turn the domain over to you.  Eliminate future transfer hassles by owning the domain and the agency acting as your technical contact.  </p>
<p><strong>Manage your content.</strong>  When working with agencies it is still best if you take the lead to manage the content.  It is almost never cost-effective for your agency to enter, adjust and tweak content.  You are best off in the long run to learn at least the basics of the CMS and perform content entry and edits yourself.  It is also advisable that you learn how to perform general maintenance tasks such as user management.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.quis.com/2009/09/14/best-practice-website-ownership-and-asset-control/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Share presentations for visibility on SlideShare</title>
		<link>http://www.quis.com/2009/06/02/share-presentations-for-visibility-on-slideshare</link>
		<comments>http://www.quis.com/2009/06/02/share-presentations-for-visibility-on-slideshare#comments</comments>
		<pubDate>Tue, 02 Jun 2009 14:03:20 +0000</pubDate>
		<dc:creator>Dan Katz</dc:creator>
				<category><![CDATA[Best Practice]]></category>
		<category><![CDATA[Marketing]]></category>

		<guid isPermaLink="false">http://www.quis.com/?p=95</guid>
		<description><![CDATA[YouTube is certainly well known for the success it has shown with marketers. Another effective tool is SlideShare. SlideShare offers the ability to post a presentation that others can view, share and comment upon just as you would a video on YouTube. There are a number of similar services, but SlideShare appears to have a [...]]]></description>
			<content:encoded><![CDATA[<p>YouTube is certainly well known for the success it has shown with marketers. Another effective tool is SlideShare. SlideShare offers the ability to post a presentation that others can view, share and comment upon just as you would a video on YouTube. There are a number of similar services, but SlideShare appears to have a solid user base.</p>
<p>Easy to use and requiring nothing more than a PowerPoint deck, SlideShare is easy to test out for marketing and communications campaigns.</p>
<p>What makes this really easy is a nice Microsoft PowerPoint plug-in. This allows you to work with the SlideShare features and post to the site right from within PowerPoint. <a href="http://www.slideshare.net/developers/apps/pptribbon">Get it here</a>. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.quis.com/2009/06/02/share-presentations-for-visibility-on-slideshare/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Drupal CMS Alignment with Best Practices</title>
		<link>http://www.quis.com/2009/05/26/drupal-cms-alignment-with-best-practices</link>
		<comments>http://www.quis.com/2009/05/26/drupal-cms-alignment-with-best-practices#comments</comments>
		<pubDate>Tue, 26 May 2009 13:42:50 +0000</pubDate>
		<dc:creator>Dan Katz</dc:creator>
				<category><![CDATA[Best Practice]]></category>
		<category><![CDATA[Drupal]]></category>

		<guid isPermaLink="false">http://www.quis.com/2009/05/26/drupal-cms-alignment-with-best-practices</guid>
		<description><![CDATA[One of the things I fear when working with a developer is that they will claim to be as someone around here did to be a “code monkey.” Good Web site development and campaign delivery is not about creating code. It is about utilizing best practices to provide the best user experience. Those who solely [...]]]></description>
			<content:encoded><![CDATA[<p>One of the things I fear when working with a developer is that they will claim to be as someone around here did to be a “code monkey.” Good Web site development and campaign delivery is not about creating code. It is about utilizing best practices to provide the best user experience. Those who solely want to work on the code level often miss the forest through the trees</p>
<p>Each CMS must be configured to align with marketing, user interface and other best practices. The following provides for common best practices that should be noted for attention with the Drupal CMS configuration. These items are included in this document to confirm the configuration as the technical defaults are often focused on specific functionality rather than such general best practices</p>
<h1>Start Here</h1>
<p>A great list of best practices in an easy to read format is available here: <a href="http://zzolo.org/thoughts/drupal-basics-and-best-practices">http://zzolo.org/thoughts/drupal-basics-and-best-practices</a> Rather than recreate those items, just start and there and then come back to this document for more.</p>
<h2>Installation Package</h2>
<p>The Drupal core package for download from <a href="http://www.drupal.org">www.drupal.org</a> has the most basic set of core files and modules. This is always supplemented with additional modules. Use of the Acquia Drupal package distribution from <a href="http://www.acquia.com">acquia.com</a> can provide a simplified install with a large number of the modules that would have to otherwise be individually installed. This provides the entire core Drupal functions with added services from Acquia. The services from Acquia may not be desired and can be easily disabled.</p>
<h2>Module Configurations</h2>
<p>The following settings, configurations and modules should be installed and activated.</p>
<h3>Configuration Options</h3>
<p>The following basic configurations options should be set:</p>
<ul>
<li>PING – Activate ping with a long list of ping servers.. </li>
<li>User Administration – Any agency account management team Role should have the ability to add and configure users to be authors. </li>
<li>File Quota – Set the file size and upload quotas to at least 50 MB or unlimited for all users. The default of around 8 MB is almost always inadequate. </li>
<li>Full HTML – Set FULL HTML as the default input format. </li>
<li>File attachments – Activate file attachment capability for all users. </li>
<li>Video – Activate the video module for the easy inclusion of YouTube and other videos. </li>
</ul>
<h2>Modules</h2>
<p>Modules provide functionality beyond the Drupal “Core.” It is the underlying philosophy of the Drupal CMS that any installation will contain a variety of these modules to provide services beyond the basic items built-into the CMS. The main issue when selecting these modules is that they are maintained by individuals often with no real development plan. They may break, be withdrawn or be incompatible with future versions of the Drupal core.</p>
<p>Even so, be sure to check the Drupal module availability prior to developing custom code.</p>
<p>The following are a variety of helpful modules that appear to be well maintained and respected by the Drupal community. This list has been determined based upon Drupal community recommendations and other base level best practice requirements.</p>
<h3>Basic Modules</h3>
<p>The following modules should e downloaded and installed for all sites. They provide base level functions that should be expected for delivery on all sites.</p>
<ul>
<li>Content Construction Kit (CCK) <a href="http://drupal.org/project/cck">http://drupal.org/project/cck</a> </li>
<li>Views <a href="http://drupal.org/project/views">http://drupal.org/project/views</a> </li>
<li>TinyMCE <a href="http://drupal.org/project/tinymce">http://drupal.org/project/tinymce</a> </li>
<li>Image <a href="http://drupal.org/project/image">http://drupal.org/project/image</a> </li>
<li>Image Assist <a href="http://drupal.org/project/img_assist">http://drupal.org/project/img_assist</a> </li>
<li>CustomError <a href="http://drupal.org/project/customerror">http://drupal.org/project/customerror</a> </li>
<li>Draft <a href="http://drupal.org/project/draft">http://drupal.org/project/draft</a> </li>
<li>Google Analytics <a href="http://drupal.org/project/google_analytics">http://drupal.org/project/google_analytics</a> </li>
<li>Image FUpload <a href="http://drupal.org/project/image_fupload">http://drupal.org/project/image_fupload</a> </li>
<li>Page Title <a href="http://drupal.org/project/page_title">http://drupal.org/project/page_title</a> </li>
<li><a href="http://drupal.org/project/path_redirect">Pathauto</a> <a href="http://drupal.org/project/pathauto">http://drupal.org/project/pathauto</a> </li>
<li>Search Engine Referrers <a href="http://drupal.org/project/search_engine_referers">http://drupal.org/project/search_engine_referers</a> </li>
<li>Search Files <a href="http://drupal.org/project/search_files">http://drupal.org/project/search_files</a> </li>
</ul>
<h3>Basic Drupal Module Configuration</h3>
<h4>Draft</h4>
<p><a href="http://redesign.pparx.org/admin/settings/draft">http://redesign.pparx.org/admin/settings/draft</a></p>
<p>This provides a method for an editing review with a draft of content. This way someone can make changes and hold then for review or come back later and complete edits and then publish.</p>
<p>To turn this on:</p>
<p>Place a check box in the “Allow drafts when editing” box</p>
<h4>CustomError</h4>
<p><a href="http://redesign.pparx.org/admin/settings/customerror">http://redesign.pparx.org/admin/settings/customerror</a></p>
<p>This provides for a custom page to be displayed when Web server or browser error occurs. This is important otherwise a blank page is displayed with very little wrapper display.</p>
<p>To turn this on:</p>
<p>Design page nodes or HTML files to display for 403 and 404 errors and place these details in the settings.</p>
<h4>Page Title</h4>
<p>On content creation pages, gives you the chance to specify the page title rather than defaulting to the content&#8217;s title.</p>
<p>To turn this on:</p>
<p>Active – simply use area in form to set the page title.</p>
<h3>Additional Modules</h3>
<p>The following are common modules that provide some frequently required functionality.</p>
<ul>
<li><a href="http://drupal.org/project/accessibility">http://drupal.org/project/accessibility</a></li>
<li><a href="http://drupal.org/project/addthis">http://drupal.org/project/addthis</a></li>
<li><a href="http://drupal.org/project/custom_breadcrumbs">http://drupal.org/project/custom_breadcrumbs</a></li>
<li><a href="http://drupal.org/project/download_count">http://drupal.org/project/download_count</a></li>
<li><a href="http://drupal.org/project/easylink">http://drupal.org/project/easylink</a></li>
<li><a href="http://drupal.org/project/faq">http://drupal.org/project/faq</a></li>
<li><a href="http://drupal.org/project/fast_gallery">http://drupal.org/project/fast_gallery</a></li>
<li><a href="http://drupal.org/project/fb">http://drupal.org/project/fb</a></li>
<li><a href="http://drupal.org/project/fckeditor">http://drupal.org/project/fckeditor</a></li>
<li><a href="http://drupal.org/project/feed_path_publisher">http://drupal.org/project/feed_path_publisher</a></li>
<li><a href="http://drupal.org/project/feedburner">http://drupal.org/project/feedburner</a></li>
<li><a href="http://drupal.org/project/feedbuttons">http://drupal.org/project/feedbuttons</a></li>
<li><a href="http://drupal.org/project/filebrowser">http://drupal.org/project/filebrowser</a></li>
<li><a href="http://drupal.org/project/flickr">http://drupal.org/project/flickr</a></li>
<li><a href="http://drupal.org/project/flickrstickr">http://drupal.org/project/flickrstickr</a></li>
<li><a href="http://drupal.org/project/globalredirect">http://drupal.org/project/globalredirect</a></li>
<li><a href="http://drupal.org/project/gmaplocation">http://drupal.org/project/gmaplocation</a></li>
<li><a href="http://drupal.org/project/google_appliance">http://drupal.org/project/google_appliance</a></li>
<li><a href="http://drupal.org/project/google_cse">http://drupal.org/project/google_cse</a></li>
<li><a href="http://drupal.org/project/google_keyhaviour">http://drupal.org/project/google_keyhaviour</a></li>
<li><a href="http://drupal.org/project/googtube">http://drupal.org/project/googtube</a></li>
<li><a href="http://drupal.org/project/headerimage">http://drupal.org/project/headerimage</a> &#8211; for custom banners for an area of the site.</li>
<li><a href="http://drupal.org/project/html_export">http://drupal.org/project/html_export</a></li>
<li><a href="http://drupal.org/project/httpauth">http://drupal.org/project/httpauth</a></li>
<li><a href="http://drupal.org/project/imagebrowser">http://drupal.org/project/imagebrowser</a></li>
<li><a href="http://drupal.org/project/letters">http://drupal.org/project/letters</a></li>
<li><a href="http://drupal.org/project/mobile_theme">http://drupal.org/project/mobile_theme</a></li>
<li><a href="http://drupal.org/project/mobit">http://drupal.org/project/mobit</a></li>
<li><a href="http://drupal.org/project/multiblock">http://drupal.org/project/multiblock</a></li>
<li><a href="http://drupal.org/project/seo_checklist">http://drupal.org/project/seo_checklist</a></li>
<li><a href="http://drupal.org/project/shadowbox">http://drupal.org/project/shadowbox</a></li>
<li><a href="http://drupal.org/project/sharethis">http://drupal.org/project/sharethis</a></li>
<li><a href="http://drupal.org/project/tinytinymce">http://drupal.org/project/tinytinymce</a></li>
<li><a href="http://leapon.net/en/drupal-gets-pingback">http://leapon.net/en/drupal-gets-pingback</a></li>
</ul>
<h1>Accounts/Roles</h1>
<p>User1 should not be used for development, maintenance or other tasks. Set it aside for very restrictive use.</p>
<h1>Layout and Development</h1>
<p><b><u>Never alter the Drupal core.</u></b> Instead adapt an existing module or create required customizations as a module. These methods will isolate customizations from the core and other modules so that the core may be updated without impact on custom development’</p>
<p>Use the Content Construction Kit and the Views module. You can bypass this kit and module, but future development and adjustments are easier if they are utilized.<a href="#_ftn1_5499" name="_ftnref1_5499">[1]</a></p>
<p>Use the From API. Define the forms in php syntax and let Drupal create the html. This will let other modules adapt the form and enables programmatic submission.<a href="#_ftn2_5499" name="_ftnref2_5499">[2]</a></p>
<p>With the Form API make sure to check text only fields with check_plain(). This will check the fields for malicious content such as scripts, HTML and so on.<a href="#_ftn3_5499" name="_ftnref3_5499">[3]</a></p>
<p>To tackle Drupal development is strong in HTML, CSS, JavaScript and jQuery<a href="#_ftn4_5499" name="_ftnref4_5499">[4]</a></p>
<p>For a normal (single site) installation, you should put all non-core modules or themes in the sites/all/modules or sites/all/themes folders. For a multi-site installation, put modules or themes in sites/all that you wish to have available for all sites.</p>
<h1>Scalability</h1>
<p>The following is a good resource for Drupal scalability &#8211; <a href="http://www.optaros.com/blogs/drupal-scalability">http://www.optaros.com/blogs/drupal-scalability</a>. Most of these tips come from this page.</p>
<p>Choose modules carefully and deactivate them when they are not required. This would apply mainly to modules that assist in development. Deactivate these following the development cycle and reactivate when adjustments are required.<a href="#_ftn5_5499" name="_ftnref5_5499">[5]</a></p>
<p>CCK is a critical module but can slow down high-traffic sites. Consider its impact on such models. <a href="#_ftn6_5499" name="_ftnref6_5499">[6]</a></p>
<p>A theme is not just the look and feel. It is the data architecture and should be created with performance as a key concern,<a href="#_ftn7_5499" name="_ftnref7_5499">[7]</a></p>
<p>MySQL should be tuned for performance for any size site. See this page for four tips to follow : http://www.optaros.com/blogs/drupal-scalability.<a href="#_ftn8_5499" name="_ftnref8_5499">[8]</a></p>
<p>Use database, member and caching systems for files. The Cache Router module at <a href="http://drupal.org/project/cacherouter">http://drupal.org/project/cacherouter</a> is recommended.<a href="#_ftn9_5499" name="_ftnref9_5499">[9]</a></p>
<p>Follow at least the basic guidelines for shared server and mySQL optimization as found on <a href="http://drupal.org/node/36628">http://drupal.org/node/36628</a></p>
<h1>Drupal Site for Best Practices</h1>
<p>The Drupal site itself has a whole section on best practices. This is of course a great resource and no one should start developing in Drupal without reading these areas targeted to the deep developer audience. </p>
<p>· <a href="http://drupal.org/node/287350">http://drupal.org/node/287350</a></p>
<p>· <a href="http://drupal.org/node/244642">http://drupal.org/node/244642</a></p>
<p>· <a href="http://drupal.org/node/36628">http://drupal.org/node/36628</a></p>
<p>· <a href="http://drupal.org/node/22283">http://drupal.org/node/22283</a></p>
<p>· <a href="http://drupal.org/node/224921">http://drupal.org/node/224921</a></p>
<h1>Other Best Practices Sources</h1>
<p>The following are some of the solid best practices locations I have found for Drupal. The information in this document is heavily drawn from these sites.</p>
<p>· <a href="http://www.slideshare.net/manugoel2003/drupal-best-practices">http://www.slideshare.net/manugoel2003/drupal-best-practices</a></p>
<p>· <a href="http://zzolo.org/thoughts/drupal-basics-and-best-practices">http://zzolo.org/thoughts/drupal-basics-and-best-practices</a> &#8211; Great great easy to read bullet list – start here.</p>
<p>· <a href="http://acquia.com/community/resources/webinars/seo-best-practices-your-drupal-site-0">http://acquia.com/community/resources/webinars/seo-best-practices-your-drupal-site-0</a></p>
<hr align="left" width="33%" size="1" />
<p><a href="#_ftnref1_5499" name="_ftn1_5499">[1]</a> <a href="http://www.slideshare.net/manugoel2003/drupal-best-practices">http://www.slideshare.net/manugoel2003/drupal-best-practices</a></p>
<p><a href="#_ftnref2_5499" name="_ftn2_5499">[2]</a> <a href="http://www.slideshare.net/manugoel2003/drupal-best-practices">http://www.slideshare.net/manugoel2003/drupal-best-practices</a></p>
<p><a href="#_ftnref3_5499" name="_ftn3_5499">[3]</a> <a href="http://www.slideshare.net/manugoel2003/drupal-best-practices">http://www.slideshare.net/manugoel2003/drupal-best-practices</a></p>
<p><a href="#_ftnref4_5499" name="_ftn4_5499">[4]</a> <a href="http://www.slideshare.net/manugoel2003/drupal-best-practices">http://www.slideshare.net/manugoel2003/drupal-best-practices</a></p>
<p><a href="#_ftnref5_5499" name="_ftn5_5499">[5]</a> <a href="http://www.optaros.com/blogs/drupal-scalability">http://www.optaros.com/blogs/drupal-scalability</a></p>
<p><a href="#_ftnref6_5499" name="_ftn6_5499">[6]</a> <a href="http://www.optaros.com/blogs/drupal-scalability">http://www.optaros.com/blogs/drupal-scalability</a></p>
<p><a href="#_ftnref7_5499" name="_ftn7_5499">[7]</a> <a href="http://www.optaros.com/blogs/drupal-scalability">http://www.optaros.com/blogs/drupal-scalability</a></p>
<p><a href="#_ftnref8_5499" name="_ftn8_5499">[8]</a> <a href="http://www.optaros.com/blogs/drupal-scalability">http://www.optaros.com/blogs/drupal-scalability</a></p>
<p><a href="#_ftnref9_5499" name="_ftn9_5499">[9]</a> <a href="http://www.optaros.com/blogs/drupal-scalability">http://www.optaros.com/blogs/drupal-scalability</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.quis.com/2009/05/26/drupal-cms-alignment-with-best-practices/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Best Practice: Constant Contact List Segmentation</title>
		<link>http://www.quis.com/2009/05/04/best-practice-constant-contact-list-segmentation</link>
		<comments>http://www.quis.com/2009/05/04/best-practice-constant-contact-list-segmentation#comments</comments>
		<pubDate>Mon, 04 May 2009 16:47:00 +0000</pubDate>
		<dc:creator>Dan Katz</dc:creator>
				<category><![CDATA[Best Practice]]></category>

		<guid isPermaLink="false">http://www.quis.com/2009/05/04/best-practice-constant-contact-list-segmentation</guid>
		<description><![CDATA[Constant Contact provides methods to segment lists when they are collected from different data collection forms. This is conducted by using a different list name for each data collection form. The following practices can help with this segmentation Import any external lists to a new list for each. Do not import these to lists used [...]]]></description>
			<content:encoded><![CDATA[<p>Constant Contact provides methods to segment lists when they are collected from different data collection forms. This is conducted by using a different list name for each data collection form. The following practices can help with this segmentation</p>
<ul>
<li>Import any external lists to a new list for each. Do not import these to lists used with data collection forms. If this import contains data from multiple external lists then use a column (custom data filed) for details on the original source list. </li>
<li>Create a general list for use with the main subscription form on the Web site. Something like – “General Web Contact” is a good name. </li>
<li>Use a different list for each form used with an advertisement, microsite or other campaign. Yes, you will have a large number of lists. This is absolutely fine. </li>
<li>You could use one list and have a custom field populated with a source name that is unique to each form. This is not the preferred method since this will have a single list that may become prohibitively large. </li>
<li>Where possible use the Constant Contact forms that are provided for inclusion as this can be a very easy and direct method to include the forms with minimal programming. </li>
<li>Use a plug-in/module for WordPress (<a href="http://wordpress.org/extend/plugins/constant-contact-signup-form-widget/">http://wordpress.org/extend/plugins/constant-contact-signup-form-widget/</a>) or Drupal (<a href="http://drupal.org/project/constant_contact">http://drupal.org/project/constant_contact</a>) as these can help shorten programming cycles and make it easier to create the forms. </li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.quis.com/2009/05/04/best-practice-constant-contact-list-segmentation/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Best Practice: Set redirects for a redesign launch</title>
		<link>http://www.quis.com/2008/10/27/best-practice-set-redirects-for-a-redesign-launch</link>
		<comments>http://www.quis.com/2008/10/27/best-practice-set-redirects-for-a-redesign-launch#comments</comments>
		<pubDate>Mon, 27 Oct 2008 15:29:57 +0000</pubDate>
		<dc:creator>Dan Katz</dc:creator>
				<category><![CDATA[Best Practice]]></category>
		<category><![CDATA[Online Marketing Best Practices]]></category>

		<guid isPermaLink="false">http://www.quis.com/?p=80</guid>
		<description><![CDATA[When we redesign and relaunch a Web site we change the URL for every page, image and other asset. Other sites that reference the base domain such as www.sitename.org will see no difference.&#160; However, many sites code in an links to either internal pages or other assets.&#160; It is then a good idea to utilize [...]]]></description>
			<content:encoded><![CDATA[<p>When we redesign and relaunch a Web site we change the URL for every page, image and other asset. Other sites that reference the base domain such as www.sitename.org will see no difference.&#160; However, many sites code in an links to either internal pages or other assets.&#160; It is then a good idea to utilize the built in functions in the Web server (and sometimes CMS) to redirect key URLs from the old site directly to new pages.</p>
<p>For example, a redirect statement make be placed in the Apache confirmation to direct traffic to <a href="https://www.simename.org/Intro.php">https://www.simename.org/Intro.php</a> to the new home page. </p>
<p>Besides these redirects, it is also important to have a custom 404 (file not found) error page.&#160; This error page should have the regular site wrapper with a statement that the content has moved.&#160; Be sure to have WebTrends, Hitbox or Google Analytics tracking code on this page to capture these errors.</p>
<p>The combination of these items can help reduce disruptions with the relaunch. </p>
<p><u>Further Tips</u></p>
<p>1. Before the site is launched, register for Google Webmaster Tools.&#160; Then when the site is launched place in the proper verification code from Google.&#160; Then you will be able to push Google to index the site faster and have it you will be able to more easily set Google to remove references to old pages.</p>
<p>2. Once the new site is launched, have a look at the error logs to see which pages generate 404 (page not found) errors.&#160; Such a function is built into Drupal and other CMS&#8217;.&#160; Otherwise you may need access to a log file analyzer as HitBox, WebTrends and Google Analytics do an okay job, but not a great job on trapping these errors. Once you do find these errors, set the redirects in Apache to push the requests to the pages that have replaced the old content.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.quis.com/2008/10/27/best-practice-set-redirects-for-a-redesign-launch/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Social and New Media Specialty Practice Strategy: An Outline for Communications and Public Relations Firms</title>
		<link>http://www.quis.com/2008/08/26/a-social-and-new-media-specialty-practice-strategy-an-outline-for-communications-and-public-relations-firms</link>
		<comments>http://www.quis.com/2008/08/26/a-social-and-new-media-specialty-practice-strategy-an-outline-for-communications-and-public-relations-firms#comments</comments>
		<pubDate>Tue, 26 Aug 2008 13:32:23 +0000</pubDate>
		<dc:creator>Dan Katz</dc:creator>
				<category><![CDATA[Best Practice]]></category>
		<category><![CDATA[Marketing]]></category>

		<guid isPermaLink="false">http://www.quis.com/?p=78</guid>
		<description><![CDATA[While the major advertising, communications and public relations agencies have all created digital specialty practices, the medium and small agency still struggles to adapt to the digital age. Competition from these specialty practices as well as that faced from interactive and social media agencies combines with the tight client budgets and lack of comfort with [...]]]></description>
			<content:encoded><![CDATA[<p>While the major advertising, communications and public relations agencies have all created digital specialty practices, the medium and small agency still struggles to adapt to the digital age. Competition from these specialty practices as well as that faced from interactive and social media agencies combines with the tight client budgets and lack of comfort with the new medium form traditional practitioners. This combination leaves many agencies still unprepared for the impacts the industry is facing from social media. </p>
<p>These are some thoughts of how a small to medium sized agency can integrated social media practice into their agency. Please by all means comment and let me know your thoughts.</p>
<h4>The Success of Social Media</h4>
<p>Social media is a success because of the confluence of three factors: </p>
<ul>
<li>inexpensive, high-speed Internet access; </li>
<li>easy to use technologies; </li>
<li>and the inherent human desire to participate in like minded communities. </li>
</ul>
<p>Social networking in and of itself is not new and has been studied by academics for decades. Social networking is now exciting as it has been invigorated via the Internet to apply its concepts on massive scales across geographies, demographics and other barriers. </p>
<p>In the long term all agencies will adopt the variety of new communications strategies currently being pioneered by leading-edge agencies and boutique interactive firms. Along this path, PR teams need guidance from specialists to bring the services into the routine operations.</p>
<p>Social media as the focus of a dedicated practice is justified through the market demand for the specialty services of strategic planning and tactical implementation fulfilled via knowledgeable experts. Based upon requests from clients large scale firms such as Fleishman Hillard<a href="#_edn1" name="_ednref1">[i]</a>, Edelman<a href="#_edn2" name="_ednref2">[ii]</a>, Weber Shandwick<a href="#_edn3" name="_ednref3">[iii]</a> and others have already established such practices to deliver such services to new and existing clients. Many boutiques have sprung up to address requests for services as most traditional communications agencies have not begun to integrate and fulfill these services. These factors demonstrate that the demand exists and models can be adopted to support a social media practice. </p>
<h4>Practice Definition </h4>
<p>Social media is the current major impact point for online to marketing. In a little while there will be something new in the limelight. Edelman has named their practice &#8220;Interactive, Social and Emerging Media&#8221; to match this constant state of change. An agency digital practice can have a similar growth pattern. The initial service set can target social media. Over time, these services can be adopted by the account teams as they become routine public relations tactics. Meanwhile, the practice can be profitably pioneering and delivering the &#8220;next big thing&#8221; such as the importance of high speed mobile and online interactions via a plethora of other devices such as your car dashboard to clients. This adoption timeframe may vary from a few months to a few years. The key factor is that the practice can maintain a leadership position to deliver high performance award winning efforts. </p>
<h4>Balance of Practice Business Volume </h4>
<p>It should be expected that forty percent of the practice volume would be from add-on sales to clients of the other agency practices. This can establish a set of immediate success stories. At the start of the practice the day-to-day execution of selected routine service delivery would be through the existing account teams. This delivery by existing teams should be expected to be needed until the volume of the practice&#8217;s new clients warrants additional specialty service staff. At that time the delivery method should be examined and responsibilities may switch to the practice team. </p>
<p>It should be expected that sixty percent of the practice volume can be for engagements from new clients where delivery is provided via the specialty staff. These efforts should be expected to entail larger scale strategy and implementation efforts or very rapid campaigns for new or exiting clients that require the skills of the practice staff. It can be expected that the breakdown of practice staff would be heavily weighted towards strategy and communications experts with design and technology being routinely implemented through freelancers or agencies. </p>
<h4>Services </h4>
<p>The following is a list of expected services that can be further developed as the core deliverables from the practice: </p>
<ul>
<li>Strategic Guidance and Planning
<ul>
<li>Social media </li>
<li>Social networks </li>
<li>CGM monitoring </li>
<li>Blogging
<ul>
<li>Branded, Corporate, Executive, product, Crisis, Issue </li>
</ul>
</li>
<li>Videos, vodcasts, podcasts </li>
<li>Maps, widgets, dashboards and other features </li>
<li>Mobile marketing and outreach </li>
</ul>
</li>
<li>Blogger Training
<ul>
<li>Executives, communications team members </li>
</ul>
</li>
<li>CGM/Blogger Relations </li>
<li>CGM Monitoring and Measurement </li>
<li>Social network and community activation, monitoring and management
<ul>
<li>Creation of dedicated and participation in existing networks </li>
</ul>
</li>
<li>SEO/SEM
<ul>
<li>Blog, social network </li>
</ul>
</li>
<li>Wiki/Blog establishment and management
<ul>
<li>Strategy </li>
<li>Setup/establishment </li>
<li>Audience development and promotions </li>
<li>Content/authoring </li>
<li>Monitoring </li>
<li>Measurement </li>
</ul>
</li>
<li>Activity awareness
<ul>
<li>i.e. Twitter, Social bookmarking (Digg, etc.) </li>
</ul>
</li>
<li>Media center and press release optimization </li>
<li>Vodcasts/podcasts </li>
<li>Campaign Web sites and micro-sites </li>
</ul>
<h4>Baseline Services for Existing Clients </h4>
<p>Initial sales should be targeted through the development of a base package of services codified and presented to existing clients to be adapted to their needs to deliver immediate social media impact to their programs. These would include: </p>
<ul>
<li>RSS feed(s) for outbound news -press releases and a new outlet for news not considered suitable for a press release </li>
<li>Improved linking practices in press releases to related product and service pages on their Web site </li>
<li>Interactive press release distribution over wire services for online indexing </li>
<li>LinkedIn&#174; and Plaxo&#174; accounts for key communications personnel </li>
<li>Facebook and MySpace pages for the company and key products, services, alumni (employee or customer) supplemented with brand and business driving social networking applications </li>
<li>Social networking and blog strategies </li>
<li>CGM (Consumer Generated Media) monitoring </li>
<li>Twitter&#174;/Friendfeed&#174; feed setup and preparation for use in campaigns and crisis communications </li>
<li>Interactive maps and related application strategies </li>
<li>Mobile strategy and Web site and email optimization for mobile devises </li>
<li>Email newsletter optimization for inclusion of social networking tie-ins and improvements. </li>
<li>Media center improvements for inclusion of social networking </li>
<li>General campaign input for all projects cycled through the agency </li>
</ul>
<h4>Sales and Marketing </h4>
<p>The expectation should be for this unit to be self supporting in six to eight months. This would require an aggressive new business development approach with matching marketing focus to demonstrate leadership, approach and expertise. The first few months would focus on immediate wins with existing clients. These early success stories would then be matched with a marketing campaign to illustrate to prospects the agencies capabilities and track record. These new business efforts could include: </p>
<ul>
<li>Aggressive outbound prospecting and meeting schedules </li>
<li>White papers to demonstrate leadership, approach and expertise </li>
<li>Speaking engagements at target market industry events </li>
<li>Demonstrate strategies through the agency&#8217;s own marketing efforts </li>
<li>Case studies built upon initial delivery to existing clients and new client engagements. </li>
<li>By-lined article placement in advertising, marketing and public relations industry publications and blogs </li>
<li>Guest authoring and commenting on respected communications blogs </li>
<li>PR Practitioners Guide to Social Media &#8211; An agency branded practical guide to getting started building and growing communities for communications professionals. </li>
</ul>
<h4>Staff </h4>
<p>The initial staffing solution would include a director and two existing staff members. One or both of these staff members should be expected to leave the agency in the first few months of the plan. For the director to drive marketing and new business efforts as well while also conducting the initial service delivery it is important that at least one junior staff member be available as a dedicate practice resource. The skills should match those currently exhibited by staff to complete such tasks as: </p>
<ul>
<li>CGM Monitoring and reporting </li>
<li>Editorial &#8211; blog post authoring </li>
<li>Blogger relations &#8211; media relations with specialty on techniques to form relationships with non-traditional journalists and individuals </li>
<li>Social network participation (i.e. Facebook, MySpace, Twitter, Digg) </li>
</ul>
<h4>Partners </h4>
<p>Most efforts would be expected to be executed via an in-house design team&#8217;s efforts applied to technology by individual freelancers or very small shops of animators and technologists. Larger scale efforts such as micro-sites and dedicated communicates would be delivered via execution contracts with boutique agencies that could be called upon for their specialties. It should be expected that a formal partnership with an interactive agency would be required in year two. </p>
<hr align="left" width="33%" size="1" />
<p><a href="#_ednref1" name="_edn1">[i]</a> Fleishman Hillard has been reinvigorating its Digital practice with an emphasis on social media with recent hires in DC and New York. Read more about this practice on their Web site at <a href="http://www.fleishman.com/client-solutions/digital.html">http://www.fleishman.com/client-solutions/digital.html</a>.</p>
<p><a href="#_ednref2" name="_edn2">[ii]</a> Edelman established its practice in early 2006. This practice is run by Steve Rubel whose Micro Persuasion blog is one of the most popular covering Web 2.0 and its interface with communications. Good summaries of the Edelman practice goals and strategies may be found at http://www.micropersuasion.com/2006/04/accelerating_th.html and <a href="http://www.edelman.com/speak_up/blog/archives/2006/01/the_mea_revolut.html">http://www.edelman.com/speak_up/blog/archives/2006/01/the_mea_revolut.html</a></p>
<p><a href="#_ednref3" name="_edn3">[iii]</a> Weber Shandwick has expanded its online special service under the name of the name &#8220;Interactive, Social and Emerging Media. See the following URL for the description from their Web site: <a href="http://www.webershandwick.com/Default.aspx/Capabilities/SpecialtyServices/InteractiveSocialandEmergingMedia">http://www.webershandwick.com/Default.aspx/Capabilities/SpecialtyServices/InteractiveSocialandEmergingMedia</a>. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.quis.com/2008/08/26/a-social-and-new-media-specialty-practice-strategy-an-outline-for-communications-and-public-relations-firms/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>YouTube Best Practices</title>
		<link>http://www.quis.com/2008/08/25/youtube-best-practices</link>
		<comments>http://www.quis.com/2008/08/25/youtube-best-practices#comments</comments>
		<pubDate>Mon, 25 Aug 2008 15:44:22 +0000</pubDate>
		<dc:creator>Dan Katz</dc:creator>
				<category><![CDATA[Best Practice]]></category>

		<guid isPermaLink="false">http://www.quis.com/2008/08/25/youtube-best-practices</guid>
		<description><![CDATA[Here are some thoughts regarding best practices for posting and promoting videos on YouTube.&#160; These best practices would also apply to Google Video, Flickr or any other content sharing network. Establish a YouTube, Google video and other accounts under the organization name. Complete account details utilizing SEO (search engine optimization best practices). Title and describe [...]]]></description>
			<content:encoded><![CDATA[<p>Here are some thoughts regarding best practices for posting and promoting videos on YouTube.&#160; These best practices would also apply to Google Video, Flickr or any other content sharing network.</p>
<ul>
<li>Establish a YouTube, Google video and other accounts under the organization name.</li>
<li>Complete account details utilizing SEO (search engine optimization best practices).</li>
<li>Title and describe videos utilize SEO best practices.</li>
<li>When embedding videos, turn off the display of related videos at the end of the video play.</li>
<li>Add annotations to provide commentary utilizing SEO best practices.</li>
<li>Make the videos highly interesting, unique and engaging to your target audiences.</li>
<li>Keep videos short (under 45 seconds) unless longer content is clearly expected by the subject matter.</li>
<li>Have the last frame of the video contain the organization brand, message and URL.</li>
<li>Have the first frame contain a title, brand and URL.</li>
<li>Select a very good image as the still frame image to attractive viewers.</li>
<li>Promote video replies and comments.</li>
<li>Embed the videos in MySpace, Facebook and as many other social networks as possible to provide access to as wide an audience as possible.</li>
</ul>
<p>Any more?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.quis.com/2008/08/25/youtube-best-practices/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

