<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 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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">I like this idea, it would be a good way for those that never see the documentation to actually use the documentation.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As we are in the process of migration, we are looking at updating our docs, and what all hast to go into the docs.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This will also force the Documentation Group to be more proactive in adding documentation, this would also depend on the developers to add the necessary documentation to when a feature or Wishlist is added especially.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black;background:white">-----------------------------</span><br>
Lynn Floyd<br>
MIS Supervisor<o:p></o:p></p>
<p class="MsoNormal">Indiana State Library<br>
317-232-3290<br>
<a href="mailto:lfloyd1@library.in.gov"><span style="color:#0563C1">lfloyd1@library.in.gov</span></a><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Evergreen-dev <evergreen-dev-bounces@list.evergreen-ils.org>
<b>On Behalf Of </b>Blake Henderson<br>
<b>Sent:</b> Tuesday, September 8, 2020 12:59 PM<br>
<b>To:</b> evergreen-dev@list.evergreen-ils.org<br>
<b>Subject:</b> Re: [Evergreen-dev] Ship Evergreen with a prebuilt manual?<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:red">**** This is an EXTERNAL email. Exercise caution. DO NOT open attachments or click links from unknown senders or unexpected email. ****</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<div>
<p class="MsoNormal">Galen,<br>
<br>
I was thinking along those same lines: give our users (library staff) documentation references for each staff UI - making it eas(ier) for folks to resolve questions they may have about the Evergreen staff client. I think this would be a boon to the Evergreen
project as a whole and might* make users morph into DIG members!<br>
<br>
This statement couldn't be more true: "Any project is only as good as it's documentation."<br>
<br>
I believe you mentioned that Koha does this? Where there is a "consortium" level document for any given interface, and it can be overridden all the way down the org tree?<br>
<br>
So - I am for* the general idea. Exactly how* might require everyone's input.<br>
<br>
<o:p></o:p></p>
<pre>-Blake-<o:p></o:p></pre>
<pre>Conducting Magic<o:p></o:p></pre>
<pre>Can consume data in any format<o:p></o:p></pre>
<pre>MOBIUS<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<div>
<p class="MsoNormal">On 9/8/2020 11:27 AM, Galen Charlton wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">Hi,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">To propose an idea for discussion, the Antora work gives us an opportunity for us to (re)consider shipping a pre-built Antora site with each release of Evergreen. Pre-built documentation could be made available via (say)
<a href="https://the.evergreen.server/docs/">https://the.evergreen.server/docs/</a>.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Some pros I see are:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">* This would make it possible for the manual to be completely self-contained.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">* Being able to count on /docs/ being available could inspire the creation of more context-sensitive help.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">* /docs/ could more easily remain in sync with the version of Evergreen that's currently installed.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">* Sites that wish to customize their documentation but are not writing it from scratch (or rewriting it wholesale) would be able to do so. Admittedly, that was already possible, but having more of the documentation site-building scripts
in Evergreen itself makes a difference.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Some cons include:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">* This would add about 45M to the uncompressed size of the Evergreen tarball. Not huge, but not nothing.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">* Managing customized documentation that's built into an Antora site would have a learning curve.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">* Built-in documentation could make certain features that consortium administrators have intentionally turned off a bit more visible than may be desired.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If we do this, I imagine we'd need at least library settings to control whether built-in documentation or externally-managed documentation is linked to from the staff interface. I could also imagine wanting to make access to /docs/ controlled
by a staff permission.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thoughts? I should note that I'm _not_ proposing that we try to do this for 3.6.0.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Galen<br>
-- <o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">Galen Charlton<br>
Implementation and Services Manager<br>
Equinox Open Library Initiative<br>
phone: 1-877-OPEN-ILS (673-6457)<br>
email: <a href="mailto:gmc@equinoxInitiative.org">gmc@equinoxInitiative.org</a><br>
web: <a href="https://protect2.fireeye.com/v1/url?k=1c2e60c8-429efdd2-1c2a29c8-8697e44c76c2-cea0df9e1155c326&q=1&e=af492967-5bfe-4d0f-8bd8-c795745f68ff&u=https%3A%2F%2Fequinoxinitiative.org%2F" target="_blank">https://equinoxInitiative.org</a><br>
direct: +1 770-709-5581<br>
cell: +1 404-984-4366<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Evergreen-dev mailing list<o:p></o:p></pre>
<pre><a href="mailto:Evergreen-dev@list.evergreen-ils.org">Evergreen-dev@list.evergreen-ils.org</a><o:p></o:p></pre>
<pre><a href="https://protect2.fireeye.com/v1/url?k=66097302-38b9ee18-660d3a02-8697e44c76c2-6c4efe84f854794a&q=1&e=af492967-5bfe-4d0f-8bd8-c795745f68ff&u=http%3A%2F%2Flist.evergreen-ils.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fevergreen-dev">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>