<?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>Alan Porter&#039;s Weblog</title>
	<atom:link href="http://blogs.webworks.com/aporter/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.webworks.com/aporter</link>
	<description>being various posts about selected happenings at WebWorks</description>
	<lastBuildDate>Tue, 13 Jul 2010 19:57:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>New Look Videos</title>
		<link>http://blogs.webworks.com/aporter/2010/07/13/new-look-videos/</link>
		<comments>http://blogs.webworks.com/aporter/2010/07/13/new-look-videos/#comments</comments>
		<pubDate>Tue, 13 Jul 2010 19:57:35 +0000</pubDate>
		<dc:creator>aporter</dc:creator>
				<category><![CDATA[Video]]></category>

		<guid isPermaLink="false">http://blogs.webworks.com/aporter/?p=154</guid>
		<description><![CDATA[Back in early 2009 we experimented a bit with producing our own low-cost videos to provide answers for some of the most common questions we get asked at trade-shows and speaking engagements.
To be honest, the results weren&#8217;t quite what we had hoped for in terms of quality, after all we are a small software company, [...]]]></description>
			<content:encoded><![CDATA[<p>Back in early 2009 we experimented a bit with producing our own low-cost videos to provide answers for some of the most common questions we get asked at trade-shows and speaking engagements.</p>
<p>To be honest, the results weren&#8217;t quite what we had hoped for in terms of quality, after all we are a small software company, not video producers; but the four short videos proved to be fairly popular, and we still see them popping up on other sites and being linked to on a fairly frequent basis.</p>
<p><span id="more-154"></span></p>
<p>When one of the old videos was picked up by an online tutorial site a few weeks ago, we started discussing revisiting the idea of producing a new line of videos. The difference is that this time we decided to bring in a local video production team  - we still wanted to keep things informal, but knew there was things we could learn about staging, lighting, and even a little voice coaching.</p>
<p>The first two videos have now been done, and posted on our newly revamped and redesigned You Tube channel. &#8211; Click on over to <a href="http://www.youtube.com/user/WebWorks2009">http://www.youtube.com/user/WebWorks2009</a> to check out all our videos.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.webworks.com/aporter/2010/07/13/new-look-videos/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>&#8220;We&#8217;ve Got You Covered&#8221;</title>
		<link>http://blogs.webworks.com/aporter/2010/06/11/weve-go-you-covered/</link>
		<comments>http://blogs.webworks.com/aporter/2010/06/11/weve-go-you-covered/#comments</comments>
		<pubDate>Fri, 11 Jun 2010 17:23:38 +0000</pubDate>
		<dc:creator>aporter</dc:creator>
				<category><![CDATA[WebWorks]]></category>

		<guid isPermaLink="false">http://blogs.webworks.com/aporter/?p=149</guid>
		<description><![CDATA[&#8220;We&#8217;ve Got You Covered&#8221; is a phrase we&#8217;ve being using around the WebWorks offices a lot recently. It was first used as a way to talk about how ePublisher has more input and output options than any other publishing engine.
As we looked back at out history we realized that each time a new input format [...]]]></description>
			<content:encoded><![CDATA[<p><strong>&#8220;We&#8217;ve Got You Covered&#8221;</strong> is a phrase we&#8217;ve being using around the WebWorks offices a lot recently. It was first used as a way to talk about how ePublisher has more input and output options than any other publishing engine.</p>
<p>As we looked back at out history we realized that each time a new input format was needed, or if a new output format was becoming a significant player in the market place, we would just add it to the ePublisher platform. Throughout the product&#8217;s history, users and subscribers to ePublisher were automatically covered, and able to meet changing demands of publishing a variety of content online in a format that their customers were asking for.</p>
<p>But the more we used the phrase, we came to realize that it meant far more than a simple statement about formats&#8230;</p>
<p><span id="more-149"></span></p>
<p><strong>&#8220;We&#8217;ve Got You Covered&#8221; </strong>is a pledge from us to make sure that your relationship with WebWorks on all levels is one that positions you to be successful, not only today, but in the years to come.</p>
<p>Using WebWorks ePublisher is also about:</p>
<ul>
<li>Having access to everyone in the company, from support and development teams, as well as Sales, through to senior management, and the CEO &#8211; we are all available and ready to listen.</li>
<li>Full knowledge sharing through our open online documentation, to our regular Tips &amp; Tricks and Newsletters, White Papers and our three popular webinar series.</li>
<li>A stable well developed product that you can set up once to give you a highly efficient workflow and scalable publishing platform.</li>
<li>Included full support and maintenance.</li>
<li>and a lot more..</li>
</ul>
<p>Even if we are only just putting words to it, &#8220;We&#8217;ve Got You Covered&#8221;  has become the WebWorks philosophy, and it is one that we will continue to develop.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.webworks.com/aporter/2010/06/11/weve-go-you-covered/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Parcel Publishing in an Agile World &#8211; New white paper available.</title>
		<link>http://blogs.webworks.com/aporter/2010/05/21/parcel-publishing-in-an-agile-world-new-white-paper-available/</link>
		<comments>http://blogs.webworks.com/aporter/2010/05/21/parcel-publishing-in-an-agile-world-new-white-paper-available/#comments</comments>
		<pubDate>Fri, 21 May 2010 12:51:02 +0000</pubDate>
		<dc:creator>aporter</dc:creator>
				<category><![CDATA[White Paper]]></category>

		<guid isPermaLink="false">http://blogs.webworks.com/aporter/?p=146</guid>
		<description><![CDATA[Traditional publishing tools have a single pipeline that moves the source content to the deliverable format. In most cases this means that once a system has been defined, it becomes locked and can only be used for that specific route. Adding new output formats or making adjustments to meet new requirements means starting from scratch [...]]]></description>
			<content:encoded><![CDATA[<p>Traditional publishing tools have a single pipeline that moves the source content to the deliverable format. In most cases this means that once a system has been defined, it becomes locked and can only be used for that specific route. Adding new output formats or making adjustments to meet new requirements means starting from scratch and developing parallel processes. This effect is magnified in tools and processes that combine the content authoring and publishing in one environment.</p>
<p><span id="more-146"></span>While this approach may be the most efficient to meet one single defined need, or solve one single problem, it is not scalable and can soon lead to development dead ends and an inability to meet new customer requirements. In an agile development environment this can cause real problems.</p>
<p>ePublisher is unique in that it uses the concept of Parcel Publishing to deliver unmatched flexibility and scalability.</p>
<p>Parcel Publishing uses a series of pipelines with well-defined start and end points that break the publishing process down into a series of discrete segments.</p>
<p><strong>Want to know more about Parcel Publishing? Ask for a copy of the latest WebWorks White Paper, and we&#8217;ll be happy to send it to you.</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.webworks.com/aporter/2010/05/21/parcel-publishing-in-an-agile-world-new-white-paper-available/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Which Version Am I Using?</title>
		<link>http://blogs.webworks.com/aporter/2010/04/20/which-version-am-i-using/</link>
		<comments>http://blogs.webworks.com/aporter/2010/04/20/which-version-am-i-using/#comments</comments>
		<pubDate>Tue, 20 Apr 2010 22:37:04 +0000</pubDate>
		<dc:creator>aporter</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Customer Service]]></category>
		<category><![CDATA[ePublisher]]></category>

		<guid isPermaLink="false">http://blogs.webworks.com/aporter/?p=142</guid>
		<description><![CDATA[With the recent release of  2010.1 we now have 8 supported versions of  ePublisher in the market, plus there are still a few customers who have yet to upgrade from unsupported versions.
When you log a support call, or are chatting with either Customer Service or your Account Manager, it helps us help you if we [...]]]></description>
			<content:encoded><![CDATA[<p>With the recent release of  2010.1 we now have 8 supported versions of  ePublisher in the market, plus there are still a few customers who have yet to upgrade from unsupported versions.</p>
<p>When you log a support call, or are chatting with either Customer Service or your Account Manager, <strong>it helps us help you if we know what version of ePublisher you are running.</strong></p>
<p><span id="more-142"></span></p>
<p>If you aren&#8217;t sure which version you have installed and using, it&#8217;s very simple to find out.</p>
<p>(1). From the <strong>Help</strong> menu just select <strong>About WebWorks ePublisher.</strong></p>
<p><a href="http://blogs.webworks.com/aporter/files/2010/04/about_menu.jpg"><img class="aligncenter size-full wp-image-143" title="about_menu" src="http://blogs.webworks.com/aporter/files/2010/04/about_menu.jpg" alt="" width="415" height="268" /></a></p>
<p>(2). This will open a splash screen that displays both the version of ePublisher and the build number.</p>
<p><a href="http://blogs.webworks.com/aporter/files/2010/04/about_box.jpg"><img class="aligncenter size-full wp-image-144" title="about_box" src="http://blogs.webworks.com/aporter/files/2010/04/about_box.jpg" alt="" width="527" height="271" /></a></p>
<p>Once you have taken a note of these numbers, you can dismiss the splash screen by simply clicking on it.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.webworks.com/aporter/2010/04/20/which-version-am-i-using/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Good security is not about patching holes..</title>
		<link>http://blogs.webworks.com/aporter/2010/02/24/good-security-is-not-about-patching-holes/</link>
		<comments>http://blogs.webworks.com/aporter/2010/02/24/good-security-is-not-about-patching-holes/#comments</comments>
		<pubDate>Wed, 24 Feb 2010 21:11:53 +0000</pubDate>
		<dc:creator>aporter</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[White Paper]]></category>

		<guid isPermaLink="false">http://blogs.webworks.com/aporter/?p=140</guid>
		<description><![CDATA[Back in January, I posted a piece on this blog asking the question &#8220;Is Your Online Help A Security Risk?&#8221; The post was the result of our own recent experiences that lead to us issuing a security advisory for WebWorks Help 5. 
During the course of our investigations we came to believe that this was an [...]]]></description>
			<content:encoded><![CDATA[<p>Back in January, I posted <a href="http://blogs.webworks.com/aporter/2010/01/08/is-your-online-help-a-security-risk/">a piece on this blog</a> asking the question <strong>&#8220;Is Your Online Help A Security Risk?&#8221;</strong> The post was the result of our own recent experiences that lead to us issuing a security advisory for WebWorks Help 5. </p>
<p>During the course of our investigations we came to believe that this was <strong>an issue that should be discussed more openly</strong>. In particular we felt an obligation to help raise awareness of how and why you need to look at your Online Help as a potential security risk.<span id="more-140"></span></p>
<p>Following that original post we planned to host a webinar on the subject. It turned out to be one of the most popular webinars we have ever held and was oversubscribed &#8211; twice. That single webinar turned into a series of three.</p>
<p>For anyone who was unable to attend, we have now collected the information presented in those webinars in a new <strong>WebWorks White Paper.</strong></p>
<p>The white paper includes sections on:</p>
<ul>
<li>Background to our own interest in Online Help security issues.</li>
<li>Notes on industry trends.</li>
<li>Why Online Help is particularly vulnerable.</li>
<li>Security as process (the title of this post comes from that section).</li>
<li>Taking steps to ensure that you are protected.</li>
</ul>
<p>If you would like a copy of <strong>&#8220;Is Your Online Help A Security Risk?&#8221;</strong> either leave a comment with your email address below, or <a href="aporter@webworks.com">email me directly </a> with your request.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.webworks.com/aporter/2010/02/24/good-security-is-not-about-patching-holes/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Project Management with ePublisher? Sure, why not?</title>
		<link>http://blogs.webworks.com/aporter/2010/02/11/project-management-with-epublisher-sure-why-not/</link>
		<comments>http://blogs.webworks.com/aporter/2010/02/11/project-management-with-epublisher-sure-why-not/#comments</comments>
		<pubDate>Thu, 11 Feb 2010 21:40:28 +0000</pubDate>
		<dc:creator>aporter</dc:creator>
				<category><![CDATA[ePublisher]]></category>

		<guid isPermaLink="false">http://blogs.webworks.com/aporter/?p=137</guid>
		<description><![CDATA[We are used to ePublisher being used to generate online help, building technical websites and even developing eLearning content. Recently we have been talking to a number of customers who use ePublisher as part of their agile software development process as a way to ensure consistent and on-time deliverables.
All of these are great examples of [...]]]></description>
			<content:encoded><![CDATA[<p>We are used to ePublisher being used to generate online help, building technical websites and even developing eLearning content. Recently we have been talking to a number of customers who use ePublisher as part of their agile software development process as a way to ensure consistent and on-time deliverables.</p>
<p>All of these are great examples of just some of the potential uses of ePublisher. Another application that we don’t talk about too much, but has been a consistent part of many customer conversations is <strong>Project Management.</strong></p>
<p><strong><span id="more-137"></span><br />
</strong></p>
<p>Using ePublisher is a great way to collate and publish your project documentation into a variety of formats that can be used by every member of the team. As more and more project teams move to online collaboration tools such as wikis, then you can use the tools you are used to, such as Microsoft Word, FrameMaker or a DITA compliant XML editor to produce your Scope Documents, Resource &amp; Staffing, Communication, Security, Test and Training plans. Then simply use ePublisher to deliver them to the online platform of your choice, making it easier to gather feedback, control and manage your project specific content.</p>
<p>Check out the <a href="http://en.wikipedia.org/wiki/PMBOK">Project Management Body of Knowledge </a>wiki for guidelines on project documentation needs.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.webworks.com/aporter/2010/02/11/project-management-with-epublisher-sure-why-not/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The End of an Era</title>
		<link>http://blogs.webworks.com/aporter/2010/01/29/the-end-of-an-era/</link>
		<comments>http://blogs.webworks.com/aporter/2010/01/29/the-end-of-an-era/#comments</comments>
		<pubDate>Fri, 29 Jan 2010 22:05:48 +0000</pubDate>
		<dc:creator>aporter</dc:creator>
				<category><![CDATA[Customer Service]]></category>
		<category><![CDATA[ePublisher]]></category>

		<guid isPermaLink="false">http://blogs.webworks.com/aporter/?p=134</guid>
		<description><![CDATA[Yesterday we announced the release of ePublisher 2009.4, the culmination of what has been an exciting year of product development here at WebWorks.
 
In keeping with our standard policy of a two year rolling support window , this means that ePublisher 9.3 is no longer a supported version and is now officially classified as a Legacy [...]]]></description>
			<content:encoded><![CDATA[<p style="margin: 0.0px 0.0px 0.0px 0.0px;font: 12.0px Helvetica">Yesterday we announced the <a href="http://www.webworks.com/Support/ePublisher/2009/">release of </a><strong><a href="http://www.webworks.com/Support/ePublisher/2009/">ePublisher 2009.4</a></strong>, the culmination of what has been an exciting year of product development here at WebWorks.</p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px;font: 12.0px Helvetica"> </p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px;font: 12.0px Helvetica">In keeping with our standard policy of a two year rolling support window , this means that ePublisher 9.3 is no longer a supported version and is now officially classified as a <a href="http://www.webworks.com/Support/Legacy_Products/">Legacy Product.</a></p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px;font: 12.0px Helvetica"> </p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px;font: 12.0px Helvetica">This marks the passing of an era as we have now moved from products based on an incremental release number to supporting products based on a quarterly release cycle and easily identified by the date in which they shipped.</p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px;font: 12.0px Helvetica"> </p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px;font: 12.0px Helvetica"><span id="more-134"></span></p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px;font: 12.0px Helvetica"> </p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px;font: 12.0px Helvetica">For customers still running 2008.1, your new keys were sent out this month, if you didn&#8217;t receive and updated key, please contact <a href="http://www.webworks.com/Company/Contact/">customer service.</a></p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px;font: 12.0px Helvetica"> </p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px;font: 12.0px Helvetica">With the current release cycle, please note that 2008.1 will move to EOL (End of Life) status when 2010.1 ships.</p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px;font: 12.0px Helvetica"> </p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px;font: 12.0px Helvetica"><strong><a href="http://www.webworks.com/Support/FAQ/ePublisher_Versions.shtml">A table showing the support status of all versions of ePublisher can be found HERE.</a></strong></p>
<div><span style="font-family: Helvetica;line-height: normal"><br />
</span></div>
]]></content:encoded>
			<wfw:commentRss>http://blogs.webworks.com/aporter/2010/01/29/the-end-of-an-era/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Is Your Online Help A Security Risk?</title>
		<link>http://blogs.webworks.com/aporter/2010/01/08/is-your-online-help-a-security-risk/</link>
		<comments>http://blogs.webworks.com/aporter/2010/01/08/is-your-online-help-a-security-risk/#comments</comments>
		<pubDate>Fri, 08 Jan 2010 22:25:09 +0000</pubDate>
		<dc:creator>aporter</dc:creator>
				<category><![CDATA[OnlineHelp]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://blogs.webworks.com/aporter/?p=131</guid>
		<description><![CDATA[As you are probably aware, back on December 15th we issued a Security Advisory for our WebWorks Help online help product. The security advisory was the result of several weeks extensive investigation of a potential loophole that could possibly be exploited by malicious software.  This was a situation we took very seriously and ensured that [...]]]></description>
			<content:encoded><![CDATA[<p>As you are probably aware, back on December 15th we issued a <a href="http://www.webworks.com/Security/2009-0001/" target="_blank">Security Advisory</a> for our WebWorks Help online help product. The security advisory was the result of several weeks extensive investigation of a potential loophole that could possibly be exploited by malicious software.  This was a situation we took very seriously and ensured that our most recent product release (ePublisher 2009.3) included fixes and updates to remedy the situation and remove the vulnerability going forward.</p>
<p>During our investigations and research we quickly discovered that we were far from the first vendor of publishing software to be in this position. It appears that several other vendors have also been similarly affected in recent years.</p>
<p>But what really caught our attention was a comment from a member of the ePublisher community:</p>
<p style="text-align: center"><strong>&#8220;I never considered that my online help could be a potential attack vector!&#8221;</strong></p>
<p>Traditionally online help is something that gets generated once and is then delivered with a product, or pushed out to a website. In most cases it continues to just sit there as web technology changes around it, becoming more and more vulnerable to hackers and malicious software.</p>
<p>Over the next few weeks we are planning several events that will hopefully help you answer the question I posed in the title of this post.</p>
<p style="text-align: center"><strong>&#8220;Is your online help a security risk?&#8221;</strong></p>
<p>More information will be posted here and on our <a href="http://twitter.com/webworks_com" target="_blank">Twitter feed</a> in the next few days.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.webworks.com/aporter/2010/01/08/is-your-online-help-a-security-risk/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Publishing in an Agile World</title>
		<link>http://blogs.webworks.com/aporter/2010/01/04/publishing-in-an-agile-world/</link>
		<comments>http://blogs.webworks.com/aporter/2010/01/04/publishing-in-an-agile-world/#comments</comments>
		<pubDate>Mon, 04 Jan 2010 19:56:41 +0000</pubDate>
		<dc:creator>aporter</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[agile]]></category>

		<guid isPermaLink="false">http://blogs.webworks.com/aporter/2010/01/04/publishing-in-an-agile-world/</guid>
		<description><![CDATA[As I mentioned in my post on December 1st, here at WebWorks we are talking to more and more people who are adopting an Agile software development model and as a result wondering how they can adapt their content publishing model to suit.
To help answer that question I have put together a short white paper [...]]]></description>
			<content:encoded><![CDATA[<p>As I mentioned in my post on December 1st, here at WebWorks we are talking to more and more people who are adopting an Agile software development model and as a result wondering how they can adapt their content publishing model to suit.</p>
<p>To help answer that question I have put together a short white paper on &#8220;<strong>Publishing in an Agile World</strong>&#8221; that I hope will help answer some of those questions, and in particular show how using ePublisher three stage workflow, of <strong>DESIGN. CAPTURE </strong>and <strong>APPLY</strong>, can make the task even easier.</p>
<p>You can find a copy oif the white paper on SlideShare</p>
<div id="__ss_2807099" style="width: 477px;text-align: left"><a title="Publishing in an Agile World" href="http://www.slideshare.net/webworks/publishing-in-an-agile-world-2807099">Publishing in an Agile World</a></p>
<div style="font-size: 11px;font-family: tahoma,arial;height: 26px;padding-top: 2px">View more <a href="http://www.slideshare.net/">documents</a> from <a href="http://www.slideshare.net/webworks">WebWorks </a>.</div>
</div>
<p>Or if you prefer just sens me an email at <a href="aporter@webworks.com">aporter@alanjporter.com </a>and I&#8217;ll be happy to send you a copy.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.webworks.com/aporter/2010/01/04/publishing-in-an-agile-world/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>THE WORKS Gets a New Look</title>
		<link>http://blogs.webworks.com/aporter/2009/12/10/123/</link>
		<comments>http://blogs.webworks.com/aporter/2009/12/10/123/#comments</comments>
		<pubDate>Thu, 10 Dec 2009 23:10:05 +0000</pubDate>
		<dc:creator>aporter</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.webworks.com/aporter/?p=123</guid>
		<description><![CDATA[Yesterday the new look edition of  THE WORKS newsletter was sent out. Our intention with the new version of the newsletter is not only to keep you up to date with the latest happenings at WebWorks, but also to provide ePublisher hints and tips, plus information on industry trends and developments.
We are already getting great [...]]]></description>
			<content:encoded><![CDATA[<p>Yesterday the new look edition of  THE WORKS newsletter was sent out. Our intention with the new version of the newsletter is not only to keep you up to date with the latest happenings at WebWorks, but also to provide ePublisher hints and tips, plus information on industry trends and developments.</p>
<p>We are already getting great feedback, such as:</p>
<blockquote><p>It&#8217;s an excellent way of keeping your users aware of what&#8217;s  happening on the ePublisher front, and will help teams  like us leverage the ePublisher features to provide new capabilities.</p></blockquote>
<p>Newsletter subscribers also get access to special offers and discounts not available anywhere else, so if you don&#8217;t already receive THE WORKS, sign up now on the <a href="http://webworks.com/Resources/Newsletter/Subscribe/">Newsletter subscription page.</a></p>
<p><img class="aligncenter size-full wp-image-122" src="http://blogs.webworks.com/aporter/files/2009/12/works_newlook2.JPG" alt="works_newlook" width="336" height="368" /></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.webworks.com/aporter/2009/12/10/123/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
