<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Colin,<br>
this is great stuff, so happy to see this plan coming together. <br>
<br>
I want to add that once the documentation is back online and as we
move with the website redesign plan, we should make sure to have on
our 'wish list' how we can improve the usability of this
documentation. <br>
<br>
I remember when sponsorO was ending, we were talking about ways to
display documentations to the user that can be smarter about popular
articles and easier to navegate / find articles, like
support.twitter.com does.<br>
<br>
thanks for working on this!<br>
Isabela<br>
<br>
On 03/08/2016 04:32 AM, Colin Childs wrote:<br>
<blockquote type="cite">Hi everyone,<br>
<br>
I hope you all had a great time in Valencia! As I mentioned in my<br>
previous status report, here is my current plan for updating the
Tor<br>
Browser user manual. The idea behind doing this, is that a large
portion<br>
of the tickets that come into the help-desk could be directly
resolved<br>
by this document, if it were maintained and available in<br>
a way that users could easily access. I believe spending the time
to<br>
finish up the manual and make it available would be more helpful
to the<br>
help-desk, and the users than answering the hundreds of individual<br>
questions posed by the users that are already answered in this
manual.<br>
<br>
When the help-desk initially started, the "short user manual"
existed,<br>
which was where the majority of answers for users came from. This
was<br>
extremely handy, as we were able to link them that document and
the<br>
majority of users could work through it themselves, saving the
help-desk<br>
for when they ran into issues. I'd like it if this could be the
state of<br>
affairs again, as it made the lives of help-desk staff a lot
easier at<br>
the time.<br>
<br>
Please let me know what you think of the plan below:<br>
<br>
- Update certain outdated screenshots<br>
<br>
- Do a complete pass of content review, and update / clean up any<br>
outdated or missing sections<br>
<br>
- Write out an update plan for the manual, as described in<br>
<a class="moz-txt-link-freetext" href="https://gitweb.torproject.org/tor-browser/user-manual.git/tree/TODO">https://gitweb.torproject.org/tor-browser/user-manual.git/tree/TODO</a><br>
<br>
- Find a home for the document on torproject.org, hopefully in a<br>
mirrored location<br>
<br>
- Contact trusted translators to work on localizing the user
manual, or<br>
updating the parts that were already localized but updated.<br>
<br>
- Upload manual to Transifex, and let translators begin working on
the<br>
strings.<br>
<br>
- Discuss ways the manual could be added to the Tor Browser (Only
after<br>
it exists on the website)<br>
<br>
- Begin pulling in new translations from language teams with
trusted<br>
reviewers, and are at 100% completion<br>
<br>
<br>
Thanks for looking this over!<br>
<br>
</blockquote>
<span style="white-space: pre;">>
_______________________________________________<br>
> tor-project mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:tor-project@lists.torproject.org">tor-project@lists.torproject.org</a><br>
>
<a class="moz-txt-link-freetext" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project</a></span><br>
<br>
-- <br>
PM at TorProject.org<br>
gpg fingerprint = 8F2A F9B6 D4A1 4D03 FDF1 B298 3224 4994 1506 4C7B<br>
@isa<br>
<br>
</body>
</html>