<meta http-equiv="content-type" content="text/html; charset=utf-8"><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
<span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">Personally, I've struggled in working on docs which are targeted at<br></span><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">people using<br>
</span><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">.....<br></span><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">- a blog on a hosted WordPress network</span></blockquote>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">I would not be keen on having that specific documentation int he codex itself becasue </span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">a) we'd be supporting other people user's</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">b) <a href="http://wordpress.com">wordpress.com</a> already has the same docs, free to use</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">c) I'd argue the codex is not the place for it.</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">A.</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></font><div class="gmail_quote">On Mon, Aug 29, 2011 at 6:23 PM, m3shrom <span dir="ltr"><<a href="mailto:m3shrom@riseup.net">m3shrom@riseup.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 29/08/2011 21:40, Spencer Hill wrote:<br>
> m3shrom, can you explain what the flossmanuals is? And what the booki links are? Maybe I'm just a newby, but I don't know what you're talking about there.<br>
<br>
</div>Sure - There's more info here. <a href="http://blog.booki.cc/" target="_blank">http://blog.booki.cc/</a><br>
and here - <a href="http://en.flossmanuals.net/index.php?plugin=blog" target="_blank">http://en.flossmanuals.net/index.php?plugin=blog</a> - click on<br>
the on the about tab.<br>
<div class="im"><br>
> If we move forward with the task based approach, how can we ensure there isn't confusion like this?<br>
<br>
</div>I think that's a good question. If you are aiming to have step by step<br>
instructions getting this kind of clarity can be tricky.<br>
<br>
Personally, I've struggled in working on docs which are targeted at<br>
people using<br>
- their own install<br>
- Wordpress.com<br>
- a blog on a hosted WordPress network<br>
<br>
For Codex / Manual docs it should be easier, you just need to add in<br>
different possibilities for users with different levels of access. For<br>
the example you use it could be...<br>
<br>
"The first thing you need to log in is a Username and Password. If you<br>
set up your own WordPress site then you should have them to hand. If<br>
someone else set up the site, they may have added you as a user and<br>
notified you in an automatically generated email. It should have the<br>
title Your Username and Password."<br>
<br>
@Lorelle - I don't know that guy / site. I just forwarded it for info. I<br>
think that this is a very interesting comparing different kinds of docs,<br>
when it comes to user focused, task based guides, it seems like often<br>
the key skill is not completeness, it's the opposite, knowing what to<br>
leave out.<br>
<br>
That's guys guide was only 28 pages long including screenshots, which<br>
gives a quick look at what he thought was most useful.<br>
<div><div></div><div class="h5">_______________________________________________<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>
</div></div></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>