I'm going to quote AF from one of the previous threads (viewtopic.php?p=575990#p575983) since it seems wiki related and I doubt it's worth making a whole new thread about it (might split again if I'm wrong).
I agree on the premise (that it's hard to get around if you don't know what you're looking for to begin with), but I'm not sure about the proposed way where we'd start with what's basically an introductory tutorial. I don't want to do that (although other people are welcomed) as I'm worried such things tend to get obsolete pretty fast.AF wrote: Right now the top level pages of the Wiki are giant glossaries of sorts. Great if you know what you want and you're drilling your way down, but terrible if you're new. I'd create calls to action at the top of each page for the common new stuff, like "I want to make a new game", no more than 2 or 3 at most. These then link off to an article that in very brief terms describes the super high level structure then provides you with a list of must read items in a recommended order.
That and I'd add a note to the lua docs explaining what Lua_SyncedCtrl or Lua_System are. They're not self explanatory and are frustrating when you're trying to find something and you're not sure which page you'll find it on, the sub headings just aren't enough.
A while ago I built a test site that attempted to index all these things, that was searchable and could be tagged, that would let you view things all at once, or grouped, or see an individual API on its own so that you could comment with code examples and important notes from people who used it PHP style. I can look into setting something up again if that would be useful?
I'd be more interested in writing manual/reference pages that hardly exist here. For most cases all we have is a list of functions and we leave it to the user to figure out what they are and how they work. Some places are better than the others (e.g. callins vs callouts) but it's still usually pretty hard to understand the whole system by just reading at the wiki. Something like this would be nice to have I think. (Maybe we are talking about a similar thing?)
Also, if you can show that test site of yours that would be great, but the *ideal permanent solution* should be an extension (or an unlikely replacement) of the wiki.
PS: This is not an invitation to continue the main discussion of that thread which got locked. Keep it addressed to the wiki issue(s) only.