Jig, you ask the exact kind of questions I'm looking for. For your first question, I'll give you two answers that should provide more understanding. The wikidot functions two-fold: first, it will be the place that we create the prototype of the Guide before it is posted on the Guild; second, I could have picked another forum or even just used PM's or Skype to make the prototype, but I picked a wikia for its symbolic nature. A wiki is a site with tons of pages and posted information that any member (in this case, you do have to apply, but that is just a minor formality) can edit and add to. I want that to be the embodiment of this endeavor. This is not "Prince's Royal Guide to Roleplay" nor will it be the "Prince and Brovo Project, feat. Jig" - it is going to be a community project made by the community for the community, and that is the very essence of a wiki. 

As to how the wiki will be structured, I intend on creating a 'portal' with an IRC, then a 'preface' page and then we go on through making page after page like chapters, adding on and editing in new content as we go over a new set of information and a new subgenre per chapter, then revise every former chapter as we see fit for the sake of consistency. However, and I stress this highly, even that system can be challenged and I will gladly let anyone take floor to either improve or present a better one. 

Now, on to the second half of this.

As per the way I would want this designed, there would be a preface that functions as a) a guideline for the editors (us) to design the site and its foundation and b) an instruction manual for all those wishing to read the guide. This is where we would explain how it works (and how we want it to work), our mission statement as a whole, the fact its a community effort, etc. After that would be Chapter One, the core. For instance: Chapter One: What is Roleplay? That is all we do. Answer that question. But, how do we do it? I would say that we try to address and define the fundamental principles found within most forms of roleplay: plot, setting, characters, roleplay itself, roleplayers, moderation, mediums, etc. We explain what roleplay is and we look at several different models created by experts, such as Ron Edwards, basically just to understand the bigger aspects of it. We create a fool-proof definition and core understand that in and of itself doesn't shed too much light on roleplay, but it provides universal understand for the later chapters. Essentially, we would tell you what roleplay is, in a general sense, and the aspects that are needed for it, but we would do so in a way that did not apply to only text. For example, LARP'ing would have a different set of rules, but somewhere in there would be still a core element. Same for table tops. Same for nations. Same for all forms of roleplay. 

Then, after we have the 'core definitions' set, we would design more. We would take these words we know and fabricate them in a formal sense to give them real definitions with a concrete level of understanding. Now, this might sound pointless, but here's where it goes on. Let's say we move on to chapter two. What would it be about? Well, I say that we change that up. Just like in a textbook, we should have "Units". Unit One: Chapter One: What is Roleplay? would lead into the Fundamentals of Roleplay which would lead into anything that any member would want to embellish on that would just apply to roleplay alone, but I'm sure that still doesn't make sense. It will as SOON as I bring forth the next Units.

Unit Two: Text-Based Roleplay. Unit Three: System-Based Roleplay. Unit Four: Other forms of roleplay like LARPING. Unit Two is obviously the big field of interest as the Guild is a forum and most of this is text-based. Here's the thing. It would ONLY and I do mean ONLY address text-based roleplay. System-Based roleplay would be meant for tabletops, RPG's, MMORPG's, whatever else you want. Essentially, you would not need to read all of Unit One to move to Unit Two. Why? Because, if you've picked up newer-age college-level textbooks, you realize that most of them don't have a chronology like that anymore. What we would do is at the beginning of each chapter simply state the suggested chapters to read from each unit to give a better understanding. All the information should be a) consistent b) integrated and c) flow smoothly. Why? Because as long as we build a core and we work off of it, every single chapter, unit and footnote should have trace elements that keep them on the same page. If we intelligently integrate the system so that a newbie wanting to learn about casual roleplay only needs to read two or three chapters and the preface, then he won't need to surf through 30 chapters to get his information. This would also allow us to create an end-of-text glossary where we can link the the words used to the chapter they were used in to fully understand the context. A word we might use in several subtypes of roleplay might have a different meaning in one kind, and why not design a system to clearly show that?

Each subtype would inevitably be its own chapter. We could even have two similar chapters in different units. Why? Character Sheets in System-based would be different than text-based. We could explain why we're using this system by looking at GNS theory by Ron Edwards which states the three core elements to roleplay are Gamism, Narrativism and Simulationism. If that's true, why not divide those elements up into units and address them as such? So many experts have done a lot of work for us and we can adapt it fairly easily, if we work together. 

And, lastly, as for how I would put this up on the Guild would actually be miraculously simple. Make the beginning post with the introduction and preface, then link every single chapter with its own reply so that we can permalink the thread within itself for convenience sake. Once it's done, just request it be locked. This would leave only one person to edit it, and in my head that was me, but I don't really care who: if we had a Mod cooperate, they could do it for us. 

I hope this covers all of your questions. Ask any more. Again, this is how I would personally see it done. I don't mind discussing other ways and I'm sure someone is going to dislike the method because it's a bit more work (even though I would probably end up doing a large part of the organizing) and that it's more complex than the simplistic method of putting one chapter after enough to be followed. That's fine. I have my reasons for wanting this system (I've been in college 3.5 years now and I've read plenty of textbooks, so I feel methods like this are superior in terms of usability and learning), but I do want people to give me input and ideas, now at the beginning and as we progress through design. I want this to be a community-based, collaborative effort with no real limit on people, although as of now I'm looking for the core group. The core, in my opinion, would be me, Aki, you (Jig), EvanCat (and his collaborators), Brovo if he hops aboard. Then there would be Rare and Vordak for their respective subtypes, as they requested. This is just the beginning.