[wp-docs] WP Docs, the wiki, and a goat

[Matt Mullenweg]

Podz wrote:

> I'd suggest that in the first instance, a page be made where topics are 
> listed, along with sub-topics (or is there one ?). Partly to ensure that 
> all gets covered, but also to ensure that if someone says they will do 
> something, they know the workload involved. As I have said before, I'll 
> do any docs at all, but I need to know where the boundaries are for what 
> I'm doing - keeps things focussed.

There are a few pages that sort of address this:

Linked pages that haven't been written:
http://codex.wordpress.org/Special:Wantedpages

Pages that aren't linked anywhere:
http://codex.wordpress.org/Special:Lonelypages

Pages that are marked as stubs:
http://codex.wordpress.org/Special:Search?search=stub&fulltext=Search

> Are there plans for an index ? Or is that part of the project in that as 
> pages are produced, they get linked from the front ?

http://codex.wordpress.org/Special:Allpages?from=5MinuteInstallation

> I assume that in the example above, Moose would have control of those 
> pages ?
> 
> It must have been discussed about using the sections of wp as the main 
> headings ?

Not yet, but I think that's a good starting point. How I envision the 
sections:

Application based:
* WordPress menu items: post, comments, links, drafts, etc
* Detailed explanation of every feature we brag about
Task based:
* Installing
* Customizing: changing colors, changing layout, switching CSS, problems
* Guides and tutorials: FTP, uploading images, etc (lots of links to 
application pages)

> Michael asked me to try and make a list of the 'vfaqs' and their 
> solutions from the forum, so this sort of thing would warrant a section 
> on it's own maybe ?

Absolutely.

> Is CSS staying out of the wiki ? I would say it should due to topic size 
> / complexity and the growing number of templates.

Yes and know. To some extent CSS (or HTML, or PHP) is too broad a topic 
for our wiki, however we should address CSS in the context of WP where 
possible and point to other more comprehensive resources.

> I'm not disagreeing with the wiki, just wondering whether for the 
> end-user it may be the best tool. That said, as it grows, it will evolve 
> and we'll see where we go from there.

If we do it right, the tool used should be completely transparant to the 
user. I'm not saying it will be easy, but it is possible.

-- 
Matt Mullenweg
  http://photomatt.net | http://wordpress.org
http://pingomatic.com | more soon...