<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Designing the Design Documentation using InDesign and EightShapes Unify</title>
	<atom:link href="http://blog.savogroup.com/2009/11/designing-the-design-documentation-using-indesign-and-eightshapes-unify/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.savogroup.com/2009/11/designing-the-design-documentation-using-indesign-and-eightshapes-unify/</link>
	<description>The SAVO Group Corporate Blog</description>
	<lastBuildDate>Tue, 02 Mar 2010 14:04:26 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mike Niebling</title>
		<link>http://blog.savogroup.com/2009/11/designing-the-design-documentation-using-indesign-and-eightshapes-unify/comment-page-1/#comment-858</link>
		<dc:creator>Mike Niebling</dc:creator>
		<pubDate>Tue, 10 Nov 2009 16:29:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.savogroup.com/?p=381#comment-858</guid>
		<description>&lt;p&gt;Hey Nathan - thanks for the feedback, and thanks for your team&#039;s time and effort in creating a great template set!&lt;/p&gt;

Maybe I didn&#039;t do enough research, but when I was looking online I really didn&#039;t find any templates in the class of Unify. So we had Word-by-hand (old method) vs. Axure automated Word vs. ID-by-hand vs. ID/Unify. The &quot;by-hand&quot; methods got thrown out because we wanted our work to look uniform, no matter who on the team was primarily writing it (and we all have slightly different conventions no matter how hard we try to eliminate them!)

So then when we had narrowed the decision to Axure automatic generation vs ID/Unify, we went through the documentation process, trying out each method on a small feature. I think what really won us over was: 

a) the workflow of keeping screenshots linked into the document, so when we update a design in Axure, all we have to do is quickly re-take the screen cap and save it over the old one. With Axure, we had to do a full regen of the documentation each time, and then re-apply our Word tweaks.

b) the library of styles/pages/objects in Unify is really nice. It&#039;s been fairly easy to customize, even for we relative InDesign novices, and we now find ourselves saying &quot;hey, I think we can use the templates for that&quot; when we&#039;re making random one-off documents.

The main challenge I think has been the learning curve of ID paired with learning which Unify styles we want to use and how they inherit... autonumbering and tables were the pain points out of the box, but I think we got the kinks ironed out as we learned more about InDesign.</description>
		<content:encoded><![CDATA[<p>Hey Nathan &#8211; thanks for the feedback, and thanks for your team&#8217;s time and effort in creating a great template set!</p>
<p>Maybe I didn&#8217;t do enough research, but when I was looking online I really didn&#8217;t find any templates in the class of Unify. So we had Word-by-hand (old method) vs. Axure automated Word vs. ID-by-hand vs. ID/Unify. The &#8220;by-hand&#8221; methods got thrown out because we wanted our work to look uniform, no matter who on the team was primarily writing it (and we all have slightly different conventions no matter how hard we try to eliminate them!)</p>
<p>So then when we had narrowed the decision to Axure automatic generation vs ID/Unify, we went through the documentation process, trying out each method on a small feature. I think what really won us over was: </p>
<p>a) the workflow of keeping screenshots linked into the document, so when we update a design in Axure, all we have to do is quickly re-take the screen cap and save it over the old one. With Axure, we had to do a full regen of the documentation each time, and then re-apply our Word tweaks.</p>
<p>b) the library of styles/pages/objects in Unify is really nice. It&#8217;s been fairly easy to customize, even for we relative InDesign novices, and we now find ourselves saying &#8220;hey, I think we can use the templates for that&#8221; when we&#8217;re making random one-off documents.</p>
<p>The main challenge I think has been the learning curve of ID paired with learning which Unify styles we want to use and how they inherit&#8230; autonumbering and tables were the pain points out of the box, but I think we got the kinks ironed out as we learned more about InDesign.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Curtis</title>
		<link>http://blog.savogroup.com/2009/11/designing-the-design-documentation-using-indesign-and-eightshapes-unify/comment-page-1/#comment-840</link>
		<dc:creator>Nathan Curtis</dc:creator>
		<pubDate>Tue, 10 Nov 2009 01:54:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.savogroup.com/?p=381#comment-840</guid>
		<description>Well done! Imagine that – audience-specific documentation design considerations. Can you talk more about some of your challenges and/or delightful surprises in using the system? And how did this tool &amp; template set stack up against others that you considered?</description>
		<content:encoded><![CDATA[<p>Well done! Imagine that – audience-specific documentation design considerations. Can you talk more about some of your challenges and/or delightful surprises in using the system? And how did this tool &amp; template set stack up against others that you considered?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

