<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/atom10full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/itemcontent.css" type="text/css" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">
    <title>Web Content Management Blog</title>
    <link rel="alternate" type="text/html" href="http://gilbane.com/web_content_management_blog/" />
    
    <id>tag:gilbane.com,2008-07-24:/web_content_management_blog//22</id>
    <updated>2008-08-11T16:22:30Z</updated>
    <subtitle>Web content management technologies and strategies.</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.1</generator>

<link rel="self" href="http://feeds.feedburner.com/WebContentManagementBlog" type="application/atom+xml" /><entry>
    <title>Communities, Engagement, and Web Experience Management</title>
    <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/WebContentManagementBlog/~3/362027846/changing-the-rules-of-web-enga.html" />
    <id>tag:gilbane.com,2008:/web_content_management_blog//22.4700</id>

    <published>2008-08-05T13:14:04Z</published>
    <updated>2008-08-11T16:22:30Z</updated>

    <summary>We came across a study entitled "The 2008 Tribalization of Business" while preparing to publish a new Gilbane white paper on web experience management. The "Tribalization" research looks at communities and online marketing: how they deliver value, obstacles to making...</summary>
    <author>
        <name>Mary Laplante</name>
        
    </author>
    
        <category term="Web Content Management - WCM" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="communities" label="communities" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="engagement" label="engagement" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="wcm" label="WCM" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="webexperiencemanagement" label="web experience management" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="webinar" label="webinar" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="whitepaper" label="white paper" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/web_content_management_blog/">
        &lt;p&gt;We came across a study entitled "The 2008 Tribalization of Business" while preparing to publish a new Gilbane white paper on &lt;a href="http://gilbane.com/blog/2008/06/dont_forget_todays_webinar.html"&gt;web experience management&lt;/a&gt;. The "Tribalization" research looks at communities and online marketing: how they deliver value, obstacles to making them work, what contributes to success, and how marketers measure effectiveness. Highlights of the research (co-sponsored by Beeline Labs, Deloitte, and the Society for New Communications Research) are &lt;a href="http://www.marketingcharts.com/interactive/word-of-mouth-insights-customer-loyalty-big-benefits-of-online-communities-5434/"&gt;reported on marketingcharts.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;This datapoint caught our eye: &lt;/p&gt;

&lt;blockquote&gt;"The greatest obstacles to making a community work are not related to technology or funding, the study found; rather, getting people [to engage] in the community (51%)."&lt;/blockquote&gt;

&lt;p&gt;Community is one of four components of engagement strategy discussed in the new Gilbane white paper (the others are personalization, user-generated content, and collaboration). In the paper, we provide some guidance about making communities work not just at start-up but throughout their lifecycle.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Engage Me! Web Experience Management as the New Business &lt;/em&gt;Imperative is the companion white paper to a webinar in which we participated with Linksys and the Colorado Department of Transportion. The webinar and paper are sponsored by FatWire. An &lt;a href="http://www.fatwire.com/cs/Satellite/WebinarsPage_US/Document_C/GilbaneWhitepaperwebinar.html"&gt;archive of the webinar&lt;/a&gt; is available for viewing, and the &lt;a href="http://www.fatwire.com/cs/Satellite/WhitepaperPage_US.html#"&gt;paper&lt;/a&gt; is now available for download on the FatWire site. It will be posted on the Gilbane site later this month.&lt;br /&gt;
&lt;/p&gt;
        
    &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=syHP7K"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=syHP7K" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=GCNkwK"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=GCNkwK" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=JMPnjk"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=JMPnjk" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=YSOg9k"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=YSOg9k" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=vxp2hK"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=vxp2hK" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=BjNElK"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=BjNElK" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=HyF0vK"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=HyF0vK" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=sa2uyK"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=sa2uyK" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WebContentManagementBlog/~4/362027846" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/web_content_management_blog/2008/08/changing-the-rules-of-web-enga.html</feedburner:origLink></entry>

<entry>
    <title>Webinar: The Keys to a Targeted Online Experience</title>
    <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/WebContentManagementBlog/~3/345957746/webinar-the-keys-to-a-targeted.html" />
    <id>tag:gilbane.com,2008:/web_content_management_blog//22.4682</id>

    <published>2008-07-25T20:35:09Z</published>
    <updated>2008-07-25T20:41:46Z</updated>

    <summary>Join the Gilbane Group and Vignette on July 30, 2008, at 2:00 p.m. (Eastern) for a webinar entitled “The Keys to a Targeted Online Experience.” The primary topic will be the synergies derived from the tight integration of Web Content...</summary>
    <author>
        <name>Tony White</name>
        <uri>http://gilbane.com/web_content_management_blog/</uri>
    </author>
    
        <category term="Web Content Management - WCM" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/web_content_management_blog/">
        &lt;p&gt;Join the Gilbane Group and Vignette on July 30, 2008, at 2:00 p.m. (Eastern) for a webinar entitled &amp;#8220;The Keys to a Targeted Online Experience.&amp;#8221;  The primary topic will be the synergies derived from the tight integration of Web Content Management-Portal-Collaboration suites versus stand-alone applications.&lt;/p&gt;

&lt;p&gt;Click &lt;a href="http://www.vignette.com/portal/site/us/menuitem.8080ac1c7e6c94f911f9ccb1180141a0/?vgnextoid=42b91e7d9d63b110VgnVCM1000005610140aRCRD&amp;amp;vgnext-selected-menuitem=569ca7a2f98202e8fb3d8010180141a0&amp;amp;gbl-vcmactguid=42b91e7d9d63b110VgnVCM1000005610140aRCRD"&gt;here&lt;/a&gt; to register.&lt;/p&gt;

        

    &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=mJGxeJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=mJGxeJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=6QJmJJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=6QJmJJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=PWJHdj"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=PWJHdj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=37IwCj"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=37IwCj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=HSvxMJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=HSvxMJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=7irShJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=7irShJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=acPEbJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=acPEbJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=idTHMJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=idTHMJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WebContentManagementBlog/~4/345957746" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/web_content_management_blog/2008/07/webinar-the-keys-to-a-targeted.html</feedburner:origLink></entry>

<entry>
    <title>"Who Are Vignette's Products Really Best Suited For?"</title>
    <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/WebContentManagementBlog/~3/344498933/when-to-consider-vignette.html" />
    <id>tag:gilbane.com,2008:/web_content_management_blog//22.4609</id>

    <published>2008-06-15T23:30:00Z</published>
    <updated>2008-06-15T22:41:44Z</updated>

    <summary>Who are Vignette's products really best suited for?  Medium-sized and large enterprises with collaborative intranets, extranets, or public-facing internet sites - especially those with demanding requirements for dynamic content and personalization.</summary>
    <author>
        <name>Tony White</name>
        <uri>http://gilbane.com/web_content_management_blog/</uri>
    </author>
    
        <category term="Web Content Management - WCM" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/web_content_management_blog/">
        &lt;p&gt;An attendee at an industry conference recently asked me, &amp;#8220;Who are Vignette&amp;#8217;s products really best suited for?&amp;#8221;  While the full answer to this broad question would require a consulting engagement to deliver, the short version is &amp;#8220;medium-sized and large enterprises that have needs for a unified WCM, collaboration, and portal solution.&amp;#8221;  While each of these Vignette applications is fully functional on its own, the real value proposition of Vignette&amp;#8217;s products stems from the synergies of tightly integrating all three modules.  In support of this statement, one client several months ago bluntly stated that for the kind of static Web publishing it had in mind, the Vignette Content Management product was &amp;#8220;too complicated and too expensive.&amp;#8221;  I agreed.  But for larger enterprises with collaborative intranets, extranets, or public-facing internet sites - especially those with demanding requirements for dynamic content and personalization - less sophisticated Web publishing solutions would certainly fail, regardless of price.&lt;/p&gt;

        

    &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=K0TiCJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=K0TiCJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=LrjnrJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=LrjnrJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=UMPmUj"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=UMPmUj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=SvCM2j"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=SvCM2j" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=idOL9J"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=idOL9J" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=LRNhWJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=LRNhWJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=uNYgAJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=uNYgAJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=E2pjyJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=E2pjyJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WebContentManagementBlog/~4/344498933" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/web_content_management_blog/2008/06/when-to-consider-vignette.html</feedburner:origLink></entry>

<entry>
    <title>Clickability Platform: Improved Marketing Campaign Management</title>
    <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/WebContentManagementBlog/~3/344498934/clickabilitys-cmpublish-platfo.html" />
    <id>tag:gilbane.com,2008:/web_content_management_blog//22.4608</id>

    <published>2008-06-13T21:00:00Z</published>
    <updated>2008-06-17T04:48:05Z</updated>

    <summary>For at least one of Clickability's target audiences - online retail marketing managers - cmPublish warrants careful, hands-on consideration.</summary>
    <author>
        <name>Tony White</name>
        <uri>http://gilbane.com/web_content_management_blog/</uri>
    </author>
    
        <category term="Hosted Applications / Software as a Service" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Industry-Specific Tools &amp; Practices" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web 2.0" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Content Management - WCM" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/web_content_management_blog/">
        &lt;p&gt;In a recent consulting project, the Gilbane Group had the opportunity to get a hands-on look at the current version of the Clickability Platform.  Several marketing-oriented product enhancements over the past year will be of particular interest to our clients.  While the product maintains its strengths in traditional online publishing (due in part to its origins in the publishing industry), there have been major improvements in areas such as analytics and reporting, social computing, and user interface design.  In fact, Clickability has re-oriented its Platform to align specifically with the usage and campaign requirements of non-technical online marketing managers.  Although product features such as in-context editing, workflow, library services, and user management, remain important and robust parts of the product, the new social computing functionality for online visitor collaboration have done much to bring Clickability to the forefront of Web 2.0-oriented content management offerings.  This functionality includes out-of-the-box support for visitor loyalty profiles, discussion boards, visitor ratings, blogs, wikis, and podcasts.&lt;/p&gt;

&lt;p&gt;Combining these new social computing components with improvements to Clickability&amp;#8217;s analytics and reporting capabilities makes the product a natural fit for companies looking for a Web content platform to support online marketing initiatives.  Areas of improvement within analytics and reporting include visitor analysis, profile targeting and reporting, campaign management, A/B split testing, reporting dashboards, ad weighting, and embedded in-context statistics.  While organizations looking for a Web content management application to support traditional online publishing can still successfully use the product, they may find the marketing-orientation of the product unnecessary or awkward.  And because good analytics and reporting in the service of online campaign management delivers high value for online retailers (in the form of higher average sales prices and better conversation rates among online shoppers), the product may demand a higher price than those publishing static HTML sites can justify.  But for at least one of Clickability&amp;#8217;s target audiences - online retail marketing managers - the new version of this platform warrants careful, hands-on consideration.&lt;/p&gt;

        

    &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=fLGKoJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=fLGKoJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=tBjrQJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=tBjrQJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=NzP05j"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=NzP05j" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=c3R1sj"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=c3R1sj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=IFYsjJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=IFYsjJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=EtEjBJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=EtEjBJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=ypF4bJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=ypF4bJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=FAc3EJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=FAc3EJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WebContentManagementBlog/~4/344498934" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/web_content_management_blog/2008/06/clickabilitys-cmpublish-platfo.html</feedburner:origLink></entry>

<entry>
    <title>Market Update on Day Software's Communiqué</title>
    <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/WebContentManagementBlog/~3/344498935/market-update-on-day-softwares.html" />
    <id>tag:gilbane.com,2008:/web_content_management_blog//22.4554</id>

    <published>2008-06-02T13:00:00Z</published>
    <updated>2008-06-02T16:53:59Z</updated>

    <summary>Several clients have recently asked about Day Software and whether its Communiqué is still being actively developed.  The answer is a resounding "yes."  In fact, the product remains one of the most technically sophisticated and flexible content management applications on the market.</summary>
    <author>
        <name>Tony White</name>
        <uri>http://gilbane.com/web_content_management_blog/</uri>
    </author>
    
        <category term="Usability &amp; User Experience" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Content Management - WCM" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/web_content_management_blog/">
        &lt;p&gt;Several clients have recently asked about Day Software and whether its Communiqué is still being actively developed.  The answer is a resounding &amp;#8220;yes.&amp;#8221;  In fact, the product remains one of the most technically sophisticated and flexible content management applications on the market.  Because Day continues to be highly involved in Java development communities, information technology departments are usually its strongest supporters.  Communiqué&amp;#8217;s technical flexibility affords IT rich integration and product-extension capabilities and an overall standards-based architecture that often aligns well with services-oriented design methodologies.&lt;/p&gt;

&lt;p&gt;Unfortunately for Day, its focus on the technical side of the product has been at the expense of simplicity and elegance in the user interface, producing at times a product too complex for non-technical business managers.  To its credit, the vendor has recent made improvements in user interface design.  Its longstanding reputation for UI complexity, however, still sometimes causes enterprises to eliminate Day from serious consideration.&lt;/p&gt;

&lt;p&gt;Given Day&amp;#8217;s past marketing foibles in the U.S. (including a near withdrawal in 2002-2003), there still lingers in the minds of prospective customers some question about the vendor&amp;#8217;s commitment to the U.S. market.  We feel comfortable saying that Day has demonstrated a strong commitment to this market over the past three to four years; and we see this trend continuing with its recent UI improvements, ongoing leadership in Java development, and a nascent but well-deserved increase in interest from enterprises trying to combine integrated multi-module solutions (Web content management, digital asset management, document management, portal, and collaboration) with technically strategic services-oriented architectures.  &lt;/p&gt;

        

    &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=uJ9OMJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=uJ9OMJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=yINI0J"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=yINI0J" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=ajimEj"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=ajimEj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=A2LQ1j"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=A2LQ1j" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=Xn6PuJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=Xn6PuJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=IhGiyJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=IhGiyJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=XYPYDJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=XYPYDJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=2v4l1J"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=2v4l1J" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WebContentManagementBlog/~4/344498935" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/web_content_management_blog/2008/06/market-update-on-day-softwares.html</feedburner:origLink></entry>

<entry>
    <title>Marketing Trends: Enabling Intelligent, Analytics-Driven Content</title>
    <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/WebContentManagementBlog/~3/344498936/trends-enabling-intelligent-an.html" />
    <id>tag:gilbane.com,2008:/web_content_management_blog//16.2678</id>

    <published>2008-05-03T11:52:00Z</published>
    <updated>2008-05-04T21:27:29Z</updated>

    <summary>While many of our clients use analytics applications to support their WCM projects and e-commerce initiatives, other clients not yet using analytics often ask what value can be derived from doing so. The answer depends on the purpose of the...</summary>
    <author>
        <name>Tony White</name>
        <uri>http://gilbane.com/web_content_management_blog/</uri>
    </author>
    
        <category term="Web Content Management - WCM" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="analytics" label="analytics" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="bridgelinesoftware" label="Bridgeline Software" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="wcm" label="WCM" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/web_content_management_blog/">
        &lt;p&gt;While many of our clients use analytics applications to support their WCM projects and e-commerce initiatives, other clients not yet using analytics often ask what value can be derived from doing so. The answer depends on the purpose of the client&amp;#8217;s website.&lt;/p&gt;

&lt;p&gt;For online commerce sites, analytics functionality can be invaluable in that it allows companies to track user behavior on the site and to correlate user behavior with conversion rates, average sales prices, and other useful sales metrics.  The bottom line is that analytics almost always increase online revenues.  Analytics can also be of great value to non e-commerce clients by enabling them to monitor content consumption rates and to gauge the relevance and effectiveness of content through the analysis of consumption patterns. This naturally makes analytics (sometimes built into &amp;#8220;campaign management&amp;#8221; modules) indispensable to marketing professionals interested either in optimizing content dissemination on information-based sites (&amp;#8220;content portals&amp;#8221;) or in maximizing profitability on retail sites.&lt;/p&gt;

&lt;p&gt;Please join us on May 8, 2008, at 1:00 p.m. (Eastern), for a webinar sponsored by Bridgeline Software entitled: &lt;a href="http://w.on24.com/r.htm?e=108098&amp;amp;s=1&amp;amp;k=8D20F20C050C7CA023AF1B372FBD2B5F&amp;amp;partnerref=gilbaneblog"&gt;&amp;#8220;Marketing Trends: Enabling Intelligent, Analytics-Driven Content.&amp;#8221;&lt;/a&gt;&lt;/p&gt;

        

    &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=0hQ1sJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=0hQ1sJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=WrXjzJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=WrXjzJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=LXybVj"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=LXybVj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=iTsxMj"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=iTsxMj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=ojN9CJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=ojN9CJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=VGLnEJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=VGLnEJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=w6V2uJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=w6V2uJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=zYMZwJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=zYMZwJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WebContentManagementBlog/~4/344498936" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/web_content_management_blog/2008/05/trends-enabling-intelligent-an.html</feedburner:origLink></entry>

<entry>
    <title>"WCM and Portal" by Any Other Name, Still "WCM and Portal"</title>
    <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/WebContentManagementBlog/~3/344498937/wcm-and-portal-by-any-other-na.html" />
    <id>tag:gilbane.com,2007:/web_content_management_blog//16.2291</id>

    <published>2007-11-08T16:17:45Z</published>
    <updated>2007-11-08T16:35:10Z</updated>

    <summary>On a recent phone call with a Gilbane Group client, we were asked about the defining differences between WCM applications and portal applications.  This question has two answers – a theoretical one and a practical one.</summary>
    <author>
        <name>Tony White</name>
        <uri>http://gilbane.com/web_content_management_blog/</uri>
    </author>
    
        <category term="Web Content Management - WCM" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/web_content_management_blog/">
        &lt;p&gt;On a recent phone call with a Gilbane Group client, we were asked about the defining differences between WCM applications and portal applications.  This question has two answers – a theoretical one and a practical one.  In theory, portals provide a doorway (portal &lt; Latin &lt;em&gt;porta&lt;/em&gt;, gate) that, when opened, allows content consumers to view a particular set of content.  The exact set of content to which consumers are exposed is (a) dynamic, and (b) controllable either by the application administrator or by the consumers themselves.  Because the function of the portal essentially rests in this “doorway” or “frame” function, some customers see portal software as an empty shell or framework, with a set of underlying services, to which content-connected portlets can be added.  WCM applications, on the other hand, theoretically provide all of the features and functions required to create, manage, expire, and archive content.  This feature set typically includes authoring and editing tools for multiple content types, automated workflow, versioning, audit control, channel management, metadata management, library services, templating, access controls, personalization etc.&lt;/p&gt;

&lt;p&gt;In practice, however, the feature sets of WCM and portal applications often overlap.  One vendor’s portal product might provide the same feature as another vendor’s WCM application.  Because portals are composite applications that expose component applications, this phenomenon also extends to products or modules such as ERP, CRM, search, collaboration, campaign management, etc.  For this reason, depending on how vendors group features and functions in their product offerings, any given set of WCM or portal requirements may be satisfied by a variety of product combinations.  One vendor’s WCM application may suffice.  Another vendor’s portal product may also be a good fit.  And a third vendor’s solution may include WCM, portal, and collaboration modules.&lt;/p&gt;

&lt;p&gt;Because of this variation in vendors’ grouping and naming conventions, Gilbane clients should, during the technology selection process, seek solutions to their set of content management problems without becoming distracted by the exact names or number of modules or products required to provide the solution.  Let vendors include whatever products they wish in their RFP responses, but hold them responsible for (a) satisfying every requirement, (b) identifying the modules that satisfy each requirement, and (c) giving a total price for all of the modules included in the response.  In the end, “WCM and portal” by any other name is still “WCM and portal.”&lt;br /&gt;
 &lt;br /&gt;
&lt;/p&gt;
        
    &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=XmrdlJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=XmrdlJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=GGJsQJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=GGJsQJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=n2RF4j"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=n2RF4j" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=uvh10j"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=uvh10j" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=tFez6J"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=tFez6J" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=UgbJqJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=UgbJqJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=7pANSJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=7pANSJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=zc6dZJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=zc6dZJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WebContentManagementBlog/~4/344498937" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/web_content_management_blog/2007/11/wcm-and-portal-by-any-other-na.html</feedburner:origLink></entry>

<entry>
    <title>Submitting Proposal Requests to Vendors</title>
    <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/WebContentManagementBlog/~3/344498938/submitting-proposal-requests-t.html" />
    <id>tag:gilbane.com,2007:/web_content_management_blog//16.2216</id>

    <published>2007-10-05T21:18:23Z</published>
    <updated>2007-10-08T17:31:29Z</updated>

    <summary>While WCM needs analysis and generation of a master requirements document (MRD) usually prove to be quite in-depth undertakings for most clients, the RFP submitted to vendors should aim to be as simple and concise as possible.  Here’s why.</summary>
    <author>
        <name>Tony White</name>
        <uri>http://gilbane.com/web_content_management_blog/</uri>
    </author>
    
        <category term="Feature-Functionality" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Product Comparisons &amp; Evaluations" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Vendor claims" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Content Management - WCM" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="mrd" label="MRD" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="needsanalysis" label="needs analysis" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="proposal" label="proposal" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="rfp" label="RFP" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="vendors" label="vendors" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/web_content_management_blog/">
        &lt;p&gt;While WCM needs-analysis and generation of a master requirements document (MRD) usually prove to be quite in-depth undertakings for most clients, the RFP submitted to vendors should aim to be as simple and concise as possible.  Here’s why.&lt;/p&gt;

&lt;p&gt;When vendors receive a very long, nuanced description of a functional requirement, it becomes easier for them to craft a response that technically satisfies the requirement and simultaneously to withhold other relevant and more meaningful detail.  On the other hand, when vendors receive a brief description of a functional requirement or category, along with specific instructions to provide as much detail as possible (at risk of not receiving credit if enough detail is not provided), they often feel compelled to write as much they can.  The abundance of information found in such responses usually allows the customer to discern just how well a vendor’s products or solutions match line items in the MRD.&lt;/p&gt;

&lt;p&gt;Recommendation to Gilbane clients:  After detailed needs analysis and creation of an MRD, pare the language for each functional criterion in the RFP to a somewhat general level.  For example, rather than inquiring specifically about content locking models (along with the other 20-30 minute components within library services) ask instead for a complete description of what the vendor’s solution provides in the library services category.  It is essential to state that more detail in the response is better than less, and that if a vendor omits relevant information, they may not receive full marks for that category.  Following this suggestion, you will be surprised at how much more insight you gain from vendors RFP responses.&lt;br /&gt;
&lt;/p&gt;
        
    &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=soZlzJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=soZlzJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=RVvSIJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=RVvSIJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=rsds6j"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=rsds6j" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=A8dtij"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=A8dtij" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=FhoKiJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=FhoKiJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=NzMxrJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=NzMxrJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=NYo7pJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=NYo7pJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=Cp46GJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=Cp46GJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WebContentManagementBlog/~4/344498938" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/web_content_management_blog/2007/10/submitting-proposal-requests-t.html</feedburner:origLink></entry>

<entry>
    <title>WCM Usability Best Practice #1:  In-Context Authoring</title>
    <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/WebContentManagementBlog/~3/344498939/wcm-usability-best-practice-1.html" />
    <id>tag:gilbane.com,2007:/web_content_management_blog//16.2198</id>

    <published>2007-09-28T14:59:37Z</published>
    <updated>2007-10-05T02:01:51Z</updated>

    <summary>Over the next few months, I will post a series of 6-8 best practices for ensuring a high degree of usability in WCM implementations. This first entry in the series focuses on the ability for users to author content in...</summary>
    <author>
        <name>Tony White</name>
        <uri>http://gilbane.com/web_content_management_blog/</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/web_content_management_blog/">
        &lt;p&gt;Over the next few months, I will post a series of 6-8 best practices for ensuring a high degree of usability in WCM implementations.  This first entry in the series focuses on the ability for users to author content in the context of actual web pages.&lt;/p&gt;

&lt;p&gt;While many vendors claim to support in-context editing, there is a lot of variation in how this feature is presented to users.  In some cases, content authors fill in HTML forms and then click a preview button, which renders a virtualized copy of the web page.  In other cases, authors double click on a staged version of a web page, which launches a WYSIWYG editor.  Upon saving content in this editor, the author refreshes the web page and sees the updates.  In the best cases, authors can simply edit content directly on web pages without having to fill in separate web forms or to launch an external editor.  Content on web pages can be edited just as though it were in MS Word.&lt;/p&gt;

&lt;p&gt;These differences may at first seem trivial, but it quickly becomes apparent to those who spend much time authoring content or creating web pages that eliminating unnecessary steps and reducing the number of applications in these highly iterative processes produces dramatic time savings throughout the organization.  For example, if an enterprise has 25 content authors who each maintain 10 web pages daily, and each page update takes just 10 extra minutes because of redundancies, the time wasted over one year totals more than 10,000 hours.  This represents about $500,000 of unnecessary labor costs.&lt;/p&gt;

&lt;p&gt;Recommendation to enterprises:  Be sure to analyze carefully during vendor demonstrations exactly how content can be edited directly from a web page.  The most highly usable WCM systems will allow you to treat the web page like word processor.&lt;/p&gt;
        
    &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=AFpNqJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=AFpNqJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=48EhwJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=48EhwJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=xdAYmj"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=xdAYmj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=PHS6ej"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=PHS6ej" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=C42kMJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=C42kMJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=vLSJlJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=vLSJlJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=9yKaaJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=9yKaaJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=WvTIiJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=WvTIiJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WebContentManagementBlog/~4/344498939" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/web_content_management_blog/2007/09/wcm-usability-best-practice-1.html</feedburner:origLink></entry>

<entry>
    <title>2007 Gilbane Survey on the WCM User Experience</title>
    <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/WebContentManagementBlog/~3/344498940/2007-gilbane-survey-on-the-wcm.html" />
    <id>tag:gilbane.com,2007:/web_content_management_blog//16.2129</id>

    <published>2007-08-14T15:46:04Z</published>
    <updated>2007-08-14T16:11:48Z</updated>

    <summary>This is just a quick reminder to our Analyst on Demand subscribers that the results of our survey on the usability of commercially available content management solutions will be available in early September. The data will come directly from the...</summary>
    <author>
        <name>Tony White</name>
        <uri>http://gilbane.com/web_content_management_blog/</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/web_content_management_blog/">
        &lt;p&gt;This is just a quick reminder to our &lt;em&gt;&lt;a href="http://gilbane.com/analyst_inquiry_service.html"&gt;Analyst on Demand&lt;/a&gt;&lt;/em&gt; subscribers that the results of our survey on the usability of commercially available content management solutions will be available in early September.  The data will come directly from the feedback of the solution providers' customers.  Vendors covered will include Interwoven, Tridion, Vignette, FatWire, Percussion, RedDot, EMC/Documentum, CrownPeak, Mediasurface, PaperThin, Oracle, Day, Hot Banana, Clickability, Acumium, and others.&lt;/p&gt;
        
    &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=ZSQnxJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=ZSQnxJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=sXw3WJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=sXw3WJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=BTpDPj"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=BTpDPj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=J4qkBj"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=J4qkBj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=e0LjDJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=e0LjDJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=z947QJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=z947QJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=GMfDEJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=GMfDEJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=e9X3jJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=e9X3jJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WebContentManagementBlog/~4/344498940" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/web_content_management_blog/2007/08/2007-gilbane-survey-on-the-wcm.html</feedburner:origLink></entry>

<entry>
    <title>Recommendation to IT Directors:  Constantly Track WCM Applications and Their Feature Sets</title>
    <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/WebContentManagementBlog/~3/344498941/recommendation-to-it-directors.html" />
    <id>tag:gilbane.com,2007:/web_content_management_blog//16.2123</id>

    <published>2007-08-08T20:10:36Z</published>
    <updated>2007-08-09T05:36:15Z</updated>

    <summary>In recent conversations with several of Gilbane's Analyst On Demand and Technology Consulting clients, I have observed two careless practices that have prevented enterprises from being able to assess both the feature-functionality of their existing WCM applications and their requirements for selecting solution(s) to replace those applications.  Both relate to a lack of documentation.</summary>
    <author>
        <name>Tony White</name>
        <uri>http://gilbane.com/web_content_management_blog/</uri>
    </author>
    
        <category term="Cost of Ownership / Return on Investment" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Feature-Functionality" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Product Comparisons &amp; Evaluations" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Content Management - WCM" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/web_content_management_blog/">
        &lt;p&gt;In recent conversations with several of Gilbane's &lt;em&gt;&lt;a href="http://gilbane.com/analyst_inquiry_service.html"&gt;Analyst On Demand&lt;/a&gt;&lt;/em&gt; and &lt;em&gt;&lt;a href="http://www.gilbane.com/consulting_acquisition.html"&gt;Technology Acquisition Advisory&lt;/a&gt; &lt;/em&gt; clients, I have observed two careless practices that have prevented enterprises from being able to assess both the feature-functionality of their existing WCM applications and their requirements for selecting solutions to replace those applications.  Both relate to a lack of documentation.&lt;/p&gt;

&lt;p&gt;In the first case, it's the absence of a master list of the WCM-related applications that have been developed in-house over the years.  One company has "about 50" such applications, and geographically-dispersed individuals throughout the enterprise can tell me what some of them are, but no one can refer me to anyone or any system that has the complete listing.  Discrete ongoing development projects exist for many of these applications, a few of which live buried deep in departmental silos.  Needless to say, the functionality of applications within these silos is known only to a few people, is never re-used in other initiatives, and in fact often gets duplicated by newer siloed projects.&lt;/p&gt;

&lt;p&gt;The second shortcoming is the non-documentation of feature-functions within the applications themselves.  Even when applications are well known throughout the organization, their complete functionality sets are known to no one.  This results in duplicate development, redundant purchases, and negative ROI –– although no one knows just &lt;em&gt;how&lt;/em&gt; negative.&lt;/p&gt;

&lt;p&gt;At a minimum, enterprises should maintain master lists of both their WCM-related applications and the functionality within each one.  To make effective use of such documentation, companies should establish effective dissemination processes.  Examples range from the inclusion of key individuals in change control board meetings (for companies with predictive-style development methods) to informal cross-functional communication, especially between disparate technology groups, but also between IT and the business units whose requirements drive application development. &lt;/p&gt;
        
    &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=0SwldJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=0SwldJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=8CkfwJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=8CkfwJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=wYChNj"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=wYChNj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=Wl1rOj"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=Wl1rOj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=f9ZPmJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=f9ZPmJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=U34HWJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=U34HWJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=4I0TPJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=4I0TPJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=CPYlNJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=CPYlNJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WebContentManagementBlog/~4/344498941" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/web_content_management_blog/2007/08/recommendation-to-it-directors.html</feedburner:origLink></entry>

<entry>
    <title>Web Services and Service-Oriented Architecture for Business Managers</title>
    <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/WebContentManagementBlog/~3/344498943/web-services-and-serviceorient.html" />
    <id>tag:gilbane.com,2007:/web_content_management_blog//16.1991</id>

    <published>2007-06-09T04:17:50Z</published>
    <updated>2007-06-09T04:39:23Z</updated>

    <summary>Business managers serving on WCM product-selection teams or attending technology conferences sometimes ask for definitions of “Web services” and “service-oriented architecture (SOA).”   They say they are confused by their IT teams’ usage of the terms as though they were synonymous, and that when the managers themselves use the terms interchangeably, they get corrected.  Why does this happen?</summary>
    <author>
        <name>Tony White</name>
        <uri>http://gilbane.com/web_content_management_blog/</uri>
    </author>
    
        <category term="Emerging Technologies" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Content Management - WCM" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Services" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/web_content_management_blog/">
        &lt;p&gt;Business managers serving on WCM product-selection teams or attending technology conferences sometimes ask for definitions of “Web services” and “service-oriented architecture (SOA).”   They say they are confused by their IT teams’ usage of the terms as though they were synonymous, and that when the managers themselves use the terms interchangeably, they get corrected.  Why does this happen?&lt;/p&gt;

&lt;p&gt;Web services, a technology standard, and SOA, an architectural design methodology, are highly complementary.  Yet they are distinct.  “Web services” refers to technologies that allow enterprise applications of all kinds (WCM, CRM ERP, BI, etc.) to communicate with each other.  Common forms of Web services include application programming interfaces (APIs), which are connectors written by software vendors that allow for a standard way of communicating with their applications.  Vendors often publish or sell these APIs as a straightforward means of connecting.  Another common – and more generic – example of a Web service is any message, often in XML format, exchanged between a client (a Web browser, for example) and a server (your bank’s database) using the SOAP protocol.  There are variations on these two themes, but the important concept to remember about Web services is that, simply put, they allow for a standard means of communication between software applications which may or may not rely upon transmission over the Web.  Web services very frequently communicate only over corporate networks.&lt;/p&gt;

&lt;p&gt;SOA, on the other hand, is not a technology.  Rather, it is a way of designing connections between objects (application code components), applications, and other technology infrastructure.  Like the frame of a building with respect to its windows and floors, SOA only defines the relationships between technology components, not their composition.  SOA’s goals are to achieve self-sufficiency for each component – i.e. that each component will perform one complete task or “service” – and for each component to offer its “service” to all of the others.  It stands to reason then, that Web services and SOA often fit together well because SOA provides a framework within which discrete components can interact with each other, and Web services provide a standard way of building the components.&lt;/p&gt;
        
    &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=rPtIaJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=rPtIaJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=nO4igJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=nO4igJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=ohmD7j"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=ohmD7j" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=vtIFxj"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=vtIFxj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=cqpYwJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=cqpYwJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=7OIHUJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=7OIHUJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=YLNTAJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=YLNTAJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=Wfyb0J"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=Wfyb0J" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WebContentManagementBlog/~4/344498943" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/web_content_management_blog/2007/06/web-services-and-serviceorient.html</feedburner:origLink></entry>

<entry>
    <title>The User Experience and the Importance of Rich Media</title>
    <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/WebContentManagementBlog/~3/344498945/the-user-experience-and-the-im.html" />
    <id>tag:gilbane.com,2007:/web_content_management_blog//16.1884</id>

    <published>2007-04-18T21:22:23Z</published>
    <updated>2007-04-18T21:25:42Z</updated>

    <summary>As the consumption of Web content becomes more highly scrutinized by business managers measuring the effectiveness of corporate information portals and online retailers analyzing conversion rates for their marketing campaigns, the importance of rich media as a fundamental enabler of the ideal user experience has reached the critical point both for enterprises choosing WCM solutions and vendors selling them.</summary>
    <author>
        <name>Tony White</name>
        <uri>http://gilbane.com/web_content_management_blog/</uri>
    </author>
    
        <category term="Cost of Ownership / Return on Investment" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Feature-Functionality" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Rich Internet Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Usability &amp; User Experience" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/web_content_management_blog/">
        &lt;p&gt;As the consumption of Web content becomes more highly scrutinized by business managers measuring the effectiveness of corporate information portals and online retailers analyzing conversion rates for their marketing campaigns, the importance of rich media as a fundamental enabler of the ideal user experience has reached the critical point both for enterprises choosing WCM solutions and vendors selling them.  Over the past year, companies have begun prioritizing in their selection criteria the ease with which business users can create highly-usable Web sites containing multiple rich content types.  Because design agencies are repositories of expertise in site usability, it is not surprising that the market has seen a dramatic rise in their influence on enterprise selection processes.  Web design firms now influence 15-20% of all enterprise-wide WCM solution purchases in the U.S. and 25-30% in Europe (including systems integrators with usability domain expertise).&lt;/p&gt;

&lt;p&gt;What does this mean for enterprises?  First, it means that they can use design agencies as leverage points to ensure that vendors with the most usable solutions win their business.  Secondly, it means that WCM solutions themselves are improving rapidly in terms of usability.  Software vendors know that no longer can corporate IT departments prioritize low-level feature-functionality over interface design, and therefore enhancements to user interfaces are far outstripping those to extended feature-function lists.  Lastly, the increased use of analytics packages to measure the performance of WCM systems against pre-defined goals means that the ROI for these systems is becoming both more quantifiable and – very likely – more positive.&lt;/p&gt;
        
    &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=bMuSUJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=bMuSUJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=XTEOjJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=XTEOjJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=B1WfOj"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=B1WfOj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=YAWgmj"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=YAWgmj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=Ibv2yJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=Ibv2yJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=n7pHrJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=n7pHrJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=LrJwwJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=LrJwwJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=2gf8KJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=2gf8KJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WebContentManagementBlog/~4/344498945" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/web_content_management_blog/2007/04/the-user-experience-and-the-im.html</feedburner:origLink></entry>

<entry>
    <title>What does Web 2.0 Mean for WCM?</title>
    <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/WebContentManagementBlog/~3/344498946/what-does-web-20-mean-for-wcm.html" />
    <id>tag:gilbane.com,2007:/web_content_management_blog//16.1849</id>

    <published>2007-04-04T19:01:35Z</published>
    <updated>2007-04-04T19:06:44Z</updated>

    <summary>Web 2.0 refers to multi-directional interactivity between one or more humans and one or more Web applications (with their associated back-ends) -- period.</summary>
    <author>
        <name>Tony White</name>
        <uri>http://gilbane.com/web_content_management_blog/</uri>
    </author>
    
        <category term="Emerging Technologies" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Rich Internet Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Usability &amp; User Experience" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web 2.0" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Content Management - WCM" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Services" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/web_content_management_blog/">
        &lt;p&gt;“Web 2.0” is a term that gets bandied about far too often with far too little associated meaning.  Essentially, Web 2.0 refers to multi-directional interactivity between one or more humans and one or more Web applications (with their associated back-ends) -- period.  The term often pops up in descriptions of any of the following: social computing, blogs, wikis, folksonomies, Web services, RSS feeds, online applications, collaboration, mash-ups and the Web as a platform.  Don’t let the diversity of topics given as examples of Web 2.0 distract you from the fact that the key operative term is multi-directional communication.  What does this mean for WCM?&lt;/p&gt;

&lt;p&gt;For the end user, it means that Web applications such as online banking, which now rely heavily on technologies like Flash and AJAX, provide better customer service by building-in higher levels of interactivity between the user and the data within a browser session and by encouraging more efficient communication between the browser and the host.  Whereas before, every user request meant a round-trip to the server, now far more data is sent at once to the browser, often in the form of an object with which the browser can interact.  The user then manipulates the data multiple times – transferring funds between accounts, paying a bill, and updating an address, for example – and upon logging out, transactions are sent to the server all at once for processing.  Because technologies like Flash and AJAX provide for easier inclusion of rich media in the user interface, the combined effect of these Web 2.0 technologies is reduced development time for programmers, a more satisfying user experience for consumers, server processing efficiency for the host, and bandwidth savings for everyone.  Another significant advantage of Web 2.0 technologies for WCM is the tendency to be so highly based on well-defined standards that functional components of Web applications are often interchangeable.  When built on Web 2.0 technologies, the “address update” function in the Web banking example above would likely be usable by the bank’s credit card Web application as well.  This component swapability is the underlying principle behind enterprise mash-ups, a developer-oriented topic for an upcoming blog entry. &lt;br /&gt;
&lt;/p&gt;
        
    &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=mLC6yJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=mLC6yJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=CNWksJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=CNWksJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=w3uGmj"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=w3uGmj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=nWEmXj"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=nWEmXj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=m6RTvJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=m6RTvJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=UhSJkJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=UhSJkJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=TNZn3J"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=TNZn3J" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=r76JCJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=r76JCJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WebContentManagementBlog/~4/344498946" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/web_content_management_blog/2007/04/what-does-web-20-mean-for-wcm.html</feedburner:origLink></entry>

<entry>
    <title>WCM Trends for 2007:  Monetization of Content</title>
    <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/WebContentManagementBlog/~3/344498948/wcm-trends-for-2007-monetizati.html" />
    <id>tag:gilbane.com,2007:/web_content_management_blog//16.1779</id>

    <published>2007-03-11T22:50:41Z</published>
    <updated>2007-03-12T15:47:15Z</updated>

    <summary>As consumer behavioral patterns across verticals (including retail, media and entertainment, and financial services) increasingly shift toward online channels, Web content must become increasingly monetizable.</summary>
    <author>
        <name>Tony White</name>
        <uri>http://gilbane.com/web_content_management_blog/</uri>
    </author>
    
        <category term="Emerging Technologies" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Feature-Functionality" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Industry-Specific Tools &amp; Practices" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Rich Internet Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Usability &amp; User Experience" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Content Management - WCM" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Services" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://gilbane.com/web_content_management_blog/">
        &lt;p&gt;As consumer behavioral patterns across verticals (including retail, media and entertainment, and financial services) increasingly shift toward online channels, Web content must become increasingly monetizable.  Factors which improve the monetizability of content relate primarily to rich user experiences, which require Web applications to combine behavioral analytics with the cross-platform, targeted delivery of digital media of all types (audio, video, streaming content, Flash, myriad image types), all available customer data, and content from Web services-based sources (maps, shipping information, weather reports, stock quotes, news).  Not only must successful Web applications seamlessly wrap these components together behind the scenes, they must supply an interactive presentation layer that is aesthetically pleasing and easy-to-use.  The primacy of the trend toward monetizable content will fuel other trends in the WCM space, among them, the heightened importance of:&lt;/p&gt;

&lt;p&gt;* Design agencies as WCM solution providers.  Vendors to watch:  Blast Radius, Avenue A |  Razorfish, Molecular.&lt;br /&gt;
 &lt;br /&gt;
* Analytics functionality within the WCM application to support multi-channel marketing campaigns.  Vendors to watch:  Interwoven, CrownPeak.&lt;/p&gt;

&lt;p&gt;* The ability to incorporate rich media at the content creation stage.  Vendors to watch: Adobe, ClearStory Systems, EMC/Documentum.&lt;/p&gt;

&lt;p&gt;* Support for integrated search and advertising/merchandising.  Vendors to watch: Endeca, FAST, Google.&lt;/p&gt;

&lt;p&gt;* The emergence of WCM applications as primary brand managers.  This is a channel strategy decision and is not vendor-oriented in nature.&lt;/p&gt;
        
    &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=TGNpFJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=TGNpFJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=48IuTJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=48IuTJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=pWPL8j"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=pWPL8j" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=NXevsj"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=NXevsj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=7HAflJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=7HAflJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=vDa2AJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=vDa2AJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=bz21JJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=bz21JJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/WebContentManagementBlog?a=Jh2hVJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/WebContentManagementBlog?i=Jh2hVJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WebContentManagementBlog/~4/344498948" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/web_content_management_blog/2007/03/wcm-trends-for-2007-monetizati.html</feedburner:origLink></entry>

</feed>
