<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Hello Abuelo,</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">if you have suggestions and contributions that can help to improve the writer’s guide (or the writer’s experience) please let us know.</div> <div><br></div><div>Best regards,</div>Francesco<br> <div id="bloop_sign_1421192020922268928" class="bloop_sign"></div> <br><p style="color:#000;">On 14 Jan 2015 at 00:32:19, Abuelo S. B. Chdancer (<a href="mailto:playadance@gmail.com">playadance@gmail.com</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>
<title></title>
<div dir="ltr">
<div>Campbell Barton reminded...</div>
<div><br></div>
<div>"While this is subjective, we have had contributions submitted
via our<br>
project page:<br>
<br>
<a href="https://developer.blender.org/tag/documentation/" target="_blank">https://developer.blender.org/tag/documentation/</a> "<br>
</div>
<div><br></div>
<div> </div>
<div>Guys, someone who USES Blender may not know the first thing
about coding, someone who can write simple prose explaining to
another person in clear language how to DO something artistic may
be totally useless when it comes to installing software or plugging
in a USB plug.</div>
<div><br></div>
<div>I bet a lot of possible contributors give up when they read
this....</div>
<div><br></div>
<div>"We have migrated the content over to <tt>reST</tt> format, so
that the manual can be built with Sphinx. A good amount of work is
still required to complete the migration (learn more about the open
tasks in Phabricator).</div>
<p>If you want to start contributing or want to have a look at the
new manual, here we have some instructions.</p>
<h3>How to build the docs locally</h3>
<ul>
<li>Checkout the Subversion repository <tt>svn checkout <a href="https://svn.blender.org/svnroot/bf-manual/trunk">https://svn.blender.org/svnroot/bf-manual/trunk</a></tt></li>
<li>Move to the location where the repo was cloned</li>
<li>Run <tt>pip install -r requirements.txt</tt> (Windows user make
sure you are using Python 2.7, not 3.x)</li>
<li>Build a section of the manual (for example <tt>make
render</tt>)</li>
<li>Launch the <tt>contents_quicky.html</tt> inside of the html
folder and browse the freshly build render docs</li>
</ul>
<div><br></div>
<div>That is a hundred times worse than trying to use the
wiki manual. It is mindboggingly offputting and not just
incomprehensible but presents such a hurdle that most people will
stop at that point and forget being involved.</div>
<div><br></div>
<div>What it should say is.....</div>
<div><br></div>
<div>Read this (hopefully well written and elegantly presented)
webpage which explains how you register what you would like to
do.</div>
<div><br></div>
<div>If worried about 'no nothings' writing drivel, that is why we
invented human editors. Also it is technically possible to have
peer reviews of submitted entries prior to making the entry
official.</div>
<div><br></div>
<div>I was in the middle of working on my latest
animation.....</div>
<div><br></div>
<div><br></div>
<div><br></div>
</div>
_______________________________________________
<br>Bf-docboard mailing list
<br>Bf-docboard@blender.org
<br>http://lists.blender.org/mailman/listinfo/bf-docboard
<br></div></div></span></blockquote></body></html>