<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">If you go to structured FM, then the SMEs can write topics in their favorite XML/text editor.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">But getting structured is a major change that your organization might not be ready for.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I would ask the boss to refine the task. Is it for SMEs to publish to users without your attention? That’s tricky. But if you have to edit it to company standards
and do any wordsmithing at all, then they may as well just send you content in Word or in an email. In my experience, the reformatting part of it is quick compared to making sure the content is complete and accurate for the reader.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We are setting off into a project that will include your goal: Our Support crew needed a new knowledgebase that includes their Solutions and my product documentation.
I got involved and suggested MindTouch (which was recommended to me by Scott Abel and which you can see in action at the AutoDesk/AutoCad knowledgebase). <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">What we get: All my legacy content becomes nodes in the knowledgebase – each procedure, every Heading 1 and Heading 2, becomes a tagged article in the KB. All
the content is searchable by keyword and by product version. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">All new content can be published from FM. The published content is HTML with a familiar sort of interface, so Support can continue entering their own Solutions,
but now they can reference all the product documentation as well. Access is role-based, so Services can add their own articles, and make them readable internal-only. Articles are commentable, so a user (or a support or Services guy) can add comments to clarify
or support a procedure, and I can get an automatic email notification so I can update the article as needed.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">So SMEs can publish content directly, or they can submit it to me, and we get hugely-improved functionality as well.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’ll be happy to answer any questions about my experience as we go through it; feel free to contact me directly.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">John Sgammato
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Principal Technical Writer<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Imprivata, Inc<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> framers-bounces@lists.frameusers.com [mailto:framers-bounces@lists.frameusers.com]
<b>On Behalf Of </b>jackdeland@comcast.net<br>
<b>Sent:</b> Thursday, January 26, 2012 1:58 PM<br>
<b>To:</b> framers@lists.frameusers.com<br>
<b>Subject:</b> FM + CMS + SMEs w/o $$$?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">All,<br>
<br>
I have been tasked with finding a way to allow SME input directly into our publishing workflow. That is, the developers and managers would be able to edit text and add graphics to our source files. I want to keep FrameMaker as the publishing engine. I'm thinking
a CMS would be in order, but the company is aghast at the thought of spending more than 10K a year on "word processing". I basically need functionality something like Author-it that ties into Frame. I could do single-sourcing with RH (we have TCS3.5). I'm
thinking we would have 3 developers at a time who might be using the system, plus me. That's a budget of $2500 or less per year per user.<br>
<br>
Can anyone point me toward some current resources here? <br>
<br>
Thanks,<br>
<br>
Jack DeLand</span><span style="font-family:"Arial","sans-serif";color:black"><o:p></o:p></span></p>
</div>
</div>
</body>
</html>