[wp-docs] WordPress Guide in Codex

[Lorelle on WordPress]

Glad you are excited about this and see the need. Whether we do something
really solid with this or just use this as an exercise to find gaps in the
documentation, I know it will help everyone. I really want to help beef up
all documentation across WordPress this year. It's THE year. :D And yes,
I'm supposed to be out of Internet touch for the next few days but I wanted
to get some thoughts bubbling on this.

http://codex.wordpress.org/User:Lorelle/WordPress_Guide_Project

http://codex.wordpress.org/User:Lorelle/WordPress_Guide_Project_TOC

These are the starts to this project. I've just put in some babble to get
it off the ground. I took another look at wiki tables and fled immediately
to Google Docs for the research list. :D

Some of this is old stuff, but I really want to see what we can offer to
help people use WordPress with less stress and give them the guides they
need.

I'm starting to see three distinct guides with overlaps for WP, WPC, and
MS, so we need some creative brainstorming on how we want to handle that
"flow chart" and not be redundant.

Thanks!

Lorelle


On Mon, Dec 19, 2011 at 3:37 PM, Andrea Rennick <andrea at ronandandrea.com>wrote:

> I'm in!
>
> Not only that, at StudioPress we really like to send people to official
> resources first. there's just no good singular spot to send a new user who
> just heard of WP. Sometimes I send people to wp.com resources, but that
> confuses them as well. We do get a fair amount of general WordPress related
> questions.
>
> And I can spend some work time on this. ;) I've already got a short list
> of basic tutorials needed, including ones that could be easier to find.
>
> One basic tutorial missing, and yes needed by a totally new user, is how
> to create a home link using the custom nav menu. Yes, you just use the
> custom link option and fill in your URL. But this is non-obvious to
> someone learning. :)
>
> I'll see if I can get my list typed up soonish. Hey, aren't you going away
> for a few days? :P
>
> a.
>
> On Mon, Dec 19, 2011 at 7:29 PM, Lorelle on WordPress <
> lorelleonwordpress at gmail.com> wrote:
>
>> One of my goals this year with the Codex is to address the issue of too
>> many businesses, schools, associations, and groups writing their own
>> "WordPress Guides" for using WordPress. We now have excellent connections
>> with support within WordPress core, Learn WordPress, and WordPress Lessons
>> to help with a lot of the basics for using WordPress and I'd like to take
>> this a step further in the Codex. I want people to NOT have to write
>> inhouse guides except for guidelines specific to their special needs. NASA
>> even has one. SIGH.
>>
>> 1. Create a review list of the public guides online (good and bad) with
>> comments.
>>
>> 2. Create a layout of the steps needed and linked to Codex and Learn
>> articles/videos already available.
>>
>> 3. Proposals on how to fill in the gaps and create a TOC guide or
>> step-by-step process to help those needing such guides within the Codex and
>> help the Learn team find gaps.
>>
>> 4. Create a "form" on the Codex for groups to build upon for creating
>> their own inhouse guide.
>>
>> This should help us really identify the gaps we have in documentation. It
>> will also help all the documentation projects around WordPress without
>> stepping on toes, I hope.
>>
>> Want to join the process?
>>
>> Thanks!
>>
>> Lorelle
>>
>> _______________________________________________
>> wp-docs mailing list
>> wp-docs at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-docs
>>
>>
>
>
> --
> --
> Andrea Rennick, http://wpebooks.com and http://ronandandrea.com
> Co-author of WordPress All-In-One For Dummies http://rml.me/aio
>
>
> _______________________________________________
> wp-docs mailing list
> wp-docs at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.automattic.com/pipermail/wp-docs/attachments/20111219/166a5280/attachment-0001.htm>