One of the downsides to wikis (or parts of wikis) is, what if you wanted to read them? Is there a good order? Usually*, no.
You are conflating multiple different issues here, which must be examined separately or else any conclusions you reach will make no sense.
The first issue is that of content type. Many pages on Wikipedia, and on many other wikis, are simply not the kind of thing that you would “read”. They might be lists, or disambiguation pages, or category pages, or reference pages, or summaries of other pages, or meta pages, or media galleries, or blog-type updates, or “latest [whatever]” pages that communicate the status of something, or pages designed to be transcluded as components into other pages, or pages designed to be disassembled by transclusion and viewed elsewhere, or pages that implement some dynamic functionality, or data pages, or logs, or “Talk” pages, or profile pages, etc., etc., etc. Asking “what order should I read these pages in” is completely nonsensical when it comes to pages of any of these types.
The second issue is that of grouping. In what order should you read the following set of Wikipedia pages:
This, too, is a nonsense question. You could read them in any order you like, because they’re on completely disparate, unrelated topics. There just is not any kind of ordering that you can impose on them and say “there, now these three pages form a natural progression; certainly you shouldn’t read the last one first…”.
And this problem isn’t unique to Wikipedia. Even topical wikis often have pages that span a far wider range of subjects than would make sense to arrange into any kind of ordering.
And the third issue is that of views on information. Let us suppose that Wikipedia contains some subset of pages which, together, constitute the contents of a good cookbook (a bunch of recipe pages, some pages about cooking techniques, etc.). But these pages aren’t arranged in any kind of order…
… but what is stopping you from putting them in order? You could create a list of pages, which, if read in order, would make up the cookbook (or whatever). You could even make such a list… as a wiki page. Via transclusion, or such tools as wiki trails, you can assemble the list of pages into a single page, or into a structure which behaves just like an ebook would (or a web book, like ReadTheSequences.com or Butterick’s Practical Typography). And—importantly—each of those pages would still be a wiki page; it would still be browsable in the usual way, could be included in other “books”, etc.!
So, you see, to ask “in what order should I read this wiki” is simply to fundamentally misunderstand the nature of wikis—as well as their tremendous power…
Content type: I can read a book by skipping the introduction, table of contents, and go straight to the index/indices.
Grouping: This is a fair point, though most Wikis seem to have a narrower purpose than “encyclopedia”. They’re usually the encyclopedia of something (and these days Wikipedia supposedly has some limits, though they seem kind of vague).
But if someone separated parts of Wikipedia out into groups, and say identified a subset of pages to be ‘Math Wikipedia’ or ‘Wikipedia Math’, or the ‘Math Project on Wikipedia’ then they might start by identifying all ‘Math’ pages, putting together a list of ‘Math pages’, and deciding how important different pages are, and how much work needs to be done on them.
Views on information: Yes. What I see as missing are 2 things: clear groupings*, a reading order within groupings, and flow. Some articles are contradictory because there were fights and so the top of the page has something opposite the middle. Yes some groupings contain others. But when all the organization happens on (topic) articles, then it’s a rather messy graph instead of an list which says ‘all these things go together’.
*One way of doing this is to have a set of groupings which covers everything (level 1), then, within each of those top level groups, a set of groups which covers everything (level 2), and so on.
Basically, my point (which, I think, you have now understood, so I am stating it explicitly for the public benefit) is this:
The problems you outline are not downsides of wikis, the technology—they are downsides of Wikipedia, the project (and some, but not all, other wikis that are run in a similar manner). In fact wikis, the technology, are not uniquely bad, but uniquely good at solving these problems (since they so easily enable the creation of arbitrarily many different views on any given set of information-chunks, or any subset thereof)!
While they may make it easy to create different views of information chunks, what’s the benefit of such pages if no other users can find them? Having an official, well put together* page hierarchy which starts at the homepage and includes all pages is pretty valuable.
*If the organization system doesn’t “cleave reality at the joints” then it’s probably not doing it’s job.
While they may make it easy to create different views of information chunks, what’s the benefit of such pages if no other users can find them? Having an official, well put together* page hierarchy which starts at the homepage and includes all pages is pretty valuable.
I concur, but again, this is not a problem with wiki technology any more than it would be a problem with book technology if I were to publish a textbook without a table of contents or an index.
An analogy: suppose I say that a knife is uniquely good at cutting things (compared to other tools like hammers, chisels, etc.), and you protest that you have only ever seen knives used to smash things, whereas it’s hammers that you’ve seen used to cut things (with the claw side of a claw hammer, say). That would hardly be a sensible reply, yes? It’s simply that you’re not using knives (or seeing them used) correctly!
In short, you’re saying that if the power of a tool isn’t actually used, then it doesn’t do any good. I agree entirely! The answer is to go ahead and use it, not to discard the tool; knives, books, and wikis are, in fact, quite powerful, even if some foolish people use them to smash things, publish ones without indexes, or fail to create publicly visible index pages.
We ought to learn from the folly of others—not be discouraged by it.
We ought to learn from the folly of others—not be discouraged by it.
I agree.
I would note that while past examples of failure are something to improve upon, function should determine form, and past examples where form determined functionality to it’s detriment are important. While TVTropes may be fun to read, because I value LessWrong, and the ability to read LW, among other ways, via time, so I can read the latest posts (like how this site is going to change with the addition of new features), I don’t want LW to become exactly like the TVTropes wiki.
For some explicit examples:
If someone wrote a book without indentations or paragraphs, or ends to sentences it would be hard to read.
Likewise, a book with the binding broken and the pages out of order would be hard to read, but fairly simple to put in the right order—if there were page numbers. If there weren’t page numbers, and some pages were missing, it’d be hard.
An example of a problem, and a possible solution:
A) Suppose someone writes a new wiki page (on Batman (Franchise)). Then (maybe) they remember to add it to to Comics or Fiction.
(If new wiki pages show up on the frontpage, and are by default tagged “not categorized yet” (and categorized if the author categorized them) then maybe someone else can see that it needs to get slotted into the appropriate list and fixes it. This way of operating might work—unless there’s too many new articles all at once and the “categorization checkers” are flooded, and end up backlogged.)
B) Someone goes to the Fiction page (which is a list of pages) and adds a link to a “Batman (Franchise)” page (which turns red because it hasn’t been made yet). And then they go to the Batman page and write the article.
TL:DR; (Main point)
My point is that if organization is something that maybe happens after content creation as an afterthought there will be unorganized pages. But if organization work goes in beforehand then there aren’t unorganized pages. Yes sometimes things change as they’re worked out, and the pre-organization needs revision. But pre-organization is better than no organization.
You are conflating multiple different issues here, which must be examined separately or else any conclusions you reach will make no sense.
The first issue is that of content type. Many pages on Wikipedia, and on many other wikis, are simply not the kind of thing that you would “read”. They might be lists, or disambiguation pages, or category pages, or reference pages, or summaries of other pages, or meta pages, or media galleries, or blog-type updates, or “latest [whatever]” pages that communicate the status of something, or pages designed to be transcluded as components into other pages, or pages designed to be disassembled by transclusion and viewed elsewhere, or pages that implement some dynamic functionality, or data pages, or logs, or “Talk” pages, or profile pages, etc., etc., etc. Asking “what order should I read these pages in” is completely nonsensical when it comes to pages of any of these types.
The second issue is that of grouping. In what order should you read the following set of Wikipedia pages:
Batman
Myelin
Potato
This, too, is a nonsense question. You could read them in any order you like, because they’re on completely disparate, unrelated topics. There just is not any kind of ordering that you can impose on them and say “there, now these three pages form a natural progression; certainly you shouldn’t read the last one first…”.
And this problem isn’t unique to Wikipedia. Even topical wikis often have pages that span a far wider range of subjects than would make sense to arrange into any kind of ordering.
And the third issue is that of views on information. Let us suppose that Wikipedia contains some subset of pages which, together, constitute the contents of a good cookbook (a bunch of recipe pages, some pages about cooking techniques, etc.). But these pages aren’t arranged in any kind of order…
… but what is stopping you from putting them in order? You could create a list of pages, which, if read in order, would make up the cookbook (or whatever). You could even make such a list… as a wiki page. Via transclusion, or such tools as wiki trails, you can assemble the list of pages into a single page, or into a structure which behaves just like an ebook would (or a web book, like ReadTheSequences.com or Butterick’s Practical Typography). And—importantly—each of those pages would still be a wiki page; it would still be browsable in the usual way, could be included in other “books”, etc.!
So, you see, to ask “in what order should I read this wiki” is simply to fundamentally misunderstand the nature of wikis—as well as their tremendous power…
Content type: I can read a book by skipping the introduction, table of contents, and go straight to the index/indices.
Grouping: This is a fair point, though most Wikis seem to have a narrower purpose than “encyclopedia”. They’re usually the encyclopedia of something (and these days Wikipedia supposedly has some limits, though they seem kind of vague).
But if someone separated parts of Wikipedia out into groups, and say identified a subset of pages to be ‘Math Wikipedia’ or ‘Wikipedia Math’, or the ‘Math Project on Wikipedia’ then they might start by identifying all ‘Math’ pages, putting together a list of ‘Math pages’, and deciding how important different pages are, and how much work needs to be done on them.
Views on information: Yes. What I see as missing are 2 things: clear groupings*, a reading order within groupings, and flow. Some articles are contradictory because there were fights and so the top of the page has something opposite the middle. Yes some groupings contain others. But when all the organization happens on (topic) articles, then it’s a rather messy graph instead of an list which says ‘all these things go together’.
*One way of doing this is to have a set of groupings which covers everything (level 1), then, within each of those top level groups, a set of groups which covers everything (level 2), and so on.
Yes, there may be multiple reasonable such sets.
Basically, my point (which, I think, you have now understood, so I am stating it explicitly for the public benefit) is this:
The problems you outline are not downsides of wikis, the technology—they are downsides of Wikipedia, the project (and some, but not all, other wikis that are run in a similar manner). In fact wikis, the technology, are not uniquely bad, but uniquely good at solving these problems (since they so easily enable the creation of arbitrarily many different views on any given set of information-chunks, or any subset thereof)!
While they may make it easy to create different views of information chunks, what’s the benefit of such pages if no other users can find them? Having an official, well put together* page hierarchy which starts at the homepage and includes all pages is pretty valuable.
*If the organization system doesn’t “cleave reality at the joints” then it’s probably not doing it’s job.
I concur, but again, this is not a problem with wiki technology any more than it would be a problem with book technology if I were to publish a textbook without a table of contents or an index.
An analogy: suppose I say that a knife is uniquely good at cutting things (compared to other tools like hammers, chisels, etc.), and you protest that you have only ever seen knives used to smash things, whereas it’s hammers that you’ve seen used to cut things (with the claw side of a claw hammer, say). That would hardly be a sensible reply, yes? It’s simply that you’re not using knives (or seeing them used) correctly!
In short, you’re saying that if the power of a tool isn’t actually used, then it doesn’t do any good. I agree entirely! The answer is to go ahead and use it, not to discard the tool; knives, books, and wikis are, in fact, quite powerful, even if some foolish people use them to smash things, publish ones without indexes, or fail to create publicly visible index pages.
We ought to learn from the folly of others—not be discouraged by it.
I agree.
I would note that while past examples of failure are something to improve upon, function should determine form, and past examples where form determined functionality to it’s detriment are important. While TVTropes may be fun to read, because I value LessWrong, and the ability to read LW, among other ways, via time, so I can read the latest posts (like how this site is going to change with the addition of new features), I don’t want LW to become exactly like the TVTropes wiki.
For some explicit examples:
If someone wrote a book without indentations or paragraphs, or ends to sentences it would be hard to read.
Likewise, a book with the binding broken and the pages out of order would be hard to read, but fairly simple to put in the right order—if there were page numbers. If there weren’t page numbers, and some pages were missing, it’d be hard.
An example of a problem, and a possible solution:
A) Suppose someone writes a new wiki page (on Batman (Franchise)). Then (maybe) they remember to add it to to Comics or Fiction.
(If new wiki pages show up on the frontpage, and are by default tagged “not categorized yet” (and categorized if the author categorized them) then maybe someone else can see that it needs to get slotted into the appropriate list and fixes it. This way of operating might work—unless there’s too many new articles all at once and the “categorization checkers” are flooded, and end up backlogged.)
B) Someone goes to the Fiction page (which is a list of pages) and adds a link to a “Batman (Franchise)” page (which turns red because it hasn’t been made yet). And then they go to the Batman page and write the article.
TL:DR; (Main point)
My point is that if organization is something that maybe happens after content creation as an afterthought there will be unorganized pages. But if organization work goes in beforehand then there aren’t unorganized pages. Yes sometimes things change as they’re worked out, and the pre-organization needs revision. But pre-organization is better than no organization.