Quote:
1) Discussion / style how-to is still all over the place
Agreed. We need [wiki]OSDevWiki:Manual_of_style[/wiki], preferrably in the toolbox.
Quote:
2) new Wiki is strongly over-structured, without any way for a newbie to navigate the contents in a meaningful way
IMO the old wiki was understructured. I sometimes had to crawl around a lot to find pages like AGP Information. The categories are meant to clean that up, and i dont have any problems finding what i want atm (but maybe that is because i contributed quite a bit myself
)
Quote:
4) "educational" cross-links are being taken out in the process of transferring content from the old Wiki.
You have the permission to kick me in the (...) if i made such omissions. Its just plain wrong.
If you find such crimes, plz use the talkpage (which will make my rss reader go off so i'll be around to fix it within the next 24 hours) or fix it yourself.
Quote:
3) it is next to impossible to "quick reference" contents, in parts due to "category abuse", in parts due to poor naming of pages
(...)
Elaboration on 3): Usually you want to reference the Wiki from a forum thread. But a short list should make clear why it is next to impossible to quote a Wiki link from memory:
* Category:Babystep
* Tutorial:Babystep1
* Category:Bare_bones_tutorials
* Tutorial:Bare_bones
* Category:Languages
* Languages
* Category:Assembly
* Assembly
Categories are not meant to contain useful contents. Its one of the reasons why I pulled half the category tree into dispute recently. Category: pages should not be linked. they serve as automatic indexing.
Tutorial: pages contain all tutorials/walkthroughs, all other pages are in the default namespace. It should however be obvious wether a page is tutorial: or not
Quote:
Forget about extending the new Wiki before all content from the old Wiki has been migrated and the old Wiki has been disabled.
The conversion process has indeed slowed to a crawl.
/kick self However putting a hold on new pages is IMO bad - I think it'll suffice if we prioritize on the merge.
Quote:
Restart the Wiki. Now. Forget all about Category: and Tutorial: until all contents from the old Wiki has been migrated. (Unfortunately, this will now include merging new content with the old one, which is why this should be done now instead of later when we have two full-blown Wikis to merge.)
Cant we just complete/fix the merge and get it over with? Restarting from scratch sounds too much like a veteran osdever
Quote:
Keep discussion on structure etc. in one place, preferrably where people see it. I would suggest removing this whole subforum, and creating a sticky thread "Wiki" in the OS Dev forum. Keep the content of "Discussion" pages strictly on the page in question.
IMO this is "one" place, and being a separate forum, new posts dont go unnoticed.
Quote:
Create a suggested sequence of reading, either by arranging links on the main page, or by providing a "link chain" across introductionary pages.
[wiki]Introduction[/wiki] page, anyone?
---------------------
There's one thing to be aware of however: This is osdevWIKI, not the osFAQ. For that reason merging the pages while maintaining consistency is difficult. We solved it partly using the Tutorial: namespace, but that doesnt include the FAQ pages. Any suggestions on how to tackle this are still welcome.
In the meantime, a list of type 3/type 4 pages is welcomed.
P.S.: added
new template; feel free to poke articles with {{NeedsReview|Topic:13061}} tags