Again, it's not a lack of understanding.<div><br></div><div>I've previously pointed you to where a lot of work was going on with the user handbook.</div><div><br></div><div>Specifically you may wish to read this post:</div>
<div><a href="http://make.wordpress.org/support/2012/08/post-hoc-ergo-propter-hoc-approaching-and-defining/">http://make.wordpress.org/support/2012/08/post-hoc-ergo-propter-hoc-approaching-and-defining/</a></div><div><br>
</div><div>where we have been discussing this very thing. Indeed, the whole Support blog is full of posts awaiting your input.</div><div><br></div><div>There is now a core Support & Docs team, with Mika (Ipstenu), Esmi and myself as leads. We've been having ongoing discussions as to how to best approach documentation, while actually working on docs and support, and we also have a weekly IRC chat that you are more than welcome to attend and take part in, where there are a number of other professional documentation and support people involved. The chat is on Thursdays at 5pm Eastern.</div>
<div><br></div><div><div>You may have read before the WordPress is a meritocracy. We judge user contributions by a combination of the quality of someone’s contributions, and their level of interest/time commitment will determine how much influence they have over decisions. </div>
</div><div><br></div><div>Over the past few years that I have been involved, the topic of software for support docs has come up time and again, but the overriding immediate need is writing and editing the docs to begin with.</div>
<div><br></div><div>The USer Handbook is being written with WordPress - which we both can agree is easier to work with than the Codex and should not slow down contributions. We'd be happy to make you an Editor and you can get right to work as soon as you let me know which parts for the user handbook you'd like to edit.</div>
<div><br></div><div>Andrea</div><div><br><div class="gmail_quote">On Tue, Sep 25, 2012 at 9:26 AM, Marc Beneteau <span dir="ltr"><<a href="mailto:docs@manifesting.net" target="_blank">docs@manifesting.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p class="MsoNormal" style="margin-bottom:12.0pt">James, by "Winhelp
clone" i mean any system that provides the Winhelp / Javahelp
functionality. This is the way that virtually all professional software
is documented and there is a reason for that (which you know about since you
work in this area) - <br>
<br>
- Expanding/collapsing table of content (TOC) in left frame, any depth (helps
user understand where they are in the content hierarchy)<br>
- Search and Index tabs in left frame TOC<br>
- Hyperlinking to any topic in the main window opens up the left TOC for that topic
(again, helps user understand where they are in the content hierarchy and keeps
a trail) <br>
- Easily add rich content such as images, videos, and toggles (image thumbnails
that popup to larger size or else blocks of text that can get expanded)<br>
<br>
I have an idea for doing this via a WordPress theme / plugin combination.
It's a rather exciting idea to me. Once again if anyone else
likes this idea and wants to participate you can email me <a href="mailto:marc@wpacademy.tv" target="_blank">marc@wpacademy.tv</a><br>
<br>
To note that the usage or existence of a high-quality documentation platform
does not guarantee the generation of high-quality documentation, but in my
case, I can certainly say that it helps with motivation. I personally
find it very hard to work in Wiki (images and rich media are particularly
cumbersome, with the results that we see) and IMHO this is the main reason that
WordPress documentation lags way behind the WordPress code. I totally agree "find clear specific answers to specific problems", the answer to that problem is Winhelp, and particularly Winhelp in combination with "Tooltip help" or help topics that are linked from each relevant dashboard page (which is the next iteration of this, I think)<br>
</p><p class="MsoNormal" style="margin-bottom:12.0pt">I have to say I am a bit frustrated by lack of understanding / support of this idea in this forum. Perhaps (for sure), this conversation started on a different topic, and perhaps this is not the right forum for new development suggestions as y'all working really hard to support the current structure. What I am suggesting is that the current structure is not optimal and that we can do much better. I would argue also that I can speak authoritatevely about this since I make quite a good living providing Wordpress documentation, which I am willing to contribute to Codex (but not within a legacy platform as it would be too much work for me for insufficient result)<br>
</p><p class="MsoNormal" style="margin-bottom:12.0pt">
Thanks<br>
<br>
</p><div class="HOEnZb"><div class="h5">
<p class="MsoNormal">On Sun, Sep 23, 2012 at 1:31 PM, James <<a href="mailto:james@thinkhuman.com" target="_blank">james@thinkhuman.com</a>>
wrote:</p>
<span style="font-size:12.0pt;font-family:"Times New Roman","serif"">>"But I've been seriously thinking about
this, what needs<br>
> to happen (again IMHO) is an open-source Winhelp-clone system powered by<br>
> WordPress, that would be equivalent to my semi-proprietary system see for<br>
> instance:<br>
<br>
I'd recommend almost anything *but* a "winhelp clone". For me, a<br>
platform-specific format (especially Windows) both goes against the spirit<br>
of WordPress and is a cumbersome, anachronistic way of doing things.<br>
<br>
I've developed Windows help since--well, since there was a Windows. I've<br>
also created technical documentation for 20 years or so. Tool-wise, the<br>
answer is always "what creates something that helps the user be the most<br>
successful?" I think the answer can be provided with many tools, including<br>
WordPress or a wiki.<br>
<br>
If I were to pick one thing WordPress users likely want most, it's the<br>
ability to search and find clear, specific answers to specific questions.<br>
And, if I were to change only one thing about the Codex, for example, I'd<br>
add more visuals.<br>
<br>
-james</span>
</div></div><br>_______________________________________________<br>
wp-docs mailing list<br>
<a href="mailto:wp-docs@lists.automattic.com">wp-docs@lists.automattic.com</a><br>
<a href="http://lists.automattic.com/mailman/listinfo/wp-docs" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-docs</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>-- <br>Andrea Rennick, <a href="http://wpebooks.com" target="_blank">http://wpebooks.com</a> and <a href="http://ronandandrea.com" target="_blank">http://ronandandrea.com</a> <div>
Co-author of WordPress All-In-One For Dummies <a href="http://rml.me/aio" target="_blank">http://rml.me/aio</a></div><br>
</div>