I agree that the wiki needs more tutorial content. I'm not sure if it is possible, but a tutorial namespace could be useful, or at least a tutorial category.
vst_0201 describes a massive, structured tutorial covering OSDev with detailed examples, like a course. This would be AMAZING for those of us who want to learn how write an OS. There's a problem, though. Everyone who works through the course will learn how to write the
same OS. If you're here to write an OS, chances are you want it to be
your OS, not the same thing as everyone else.
I propose an alternative: We should continue adding tutorial and informative content to the wiki, but attempt to give it a backbone structure. We could do this by adding a multiple page guide. For example:
vst_0201 wrote:
Start Here
01. What is OS Development?
02. Setting up the Working Environment
03. Media Resources
Bootstrapping
01. Booting with GRUB
02. Rolling your Own
Kernel Development
01. Setting up the Environment
02. Memory Management
03. Writing Generic Drivers
Debugging
01. Dumping the Symbols
02. Debugging with Bochs
References
01. Opcodes
02. Scancodes
03. VGA Colors
04. Intel Manual
05. Ralph Brown's INT
The guide would have to be theoretical, but would link to more specific pages, which would probably link to tutorials or examples detailing exactly how to implement that method, should you choose it. If we link to multiple examples, then the user is given choices, which encourages thinking about the topic, and may even result in a different approach altogether. IMO, this will prove more useful and intuitive to the entire OSDev community.
In an attempt to avoid RTFM and STFW threads, how about including a short introduction on the main page - which links into said guide - followed by the index format we currently have, for quick reference.
Requesting opinions,
Matt