| BeBitsWikiSuggestions |
 |
|
Here are a few suggestions that might help to improve the BeBits wiki in the near future:
- Use menaingful names for wiki names. An example might be a journal, say,
GlassElevatorJournal
which is sectioned up by month. Now, if the monthly sections were to be named, say,
March2002
June2002
etc
it would soon create mayhem across the whole wikiverse once someone else wanted to create a journal with the same naming system. A solution might be to name all pages with the following schema
[Main topic][Subtopic][Section (if needed)]
In our example, the main topic would be
GlassElevator
the subtopic would be
Journal
and the section would be
March2002
resulting in a wikipage named
GlassElevatorJournalMarch2002
This is a lenghty format, but it will prevent a LOT of headaches in the future once the wiki kicks off. I'm telling this from personal experience. A solution to the lenghty names would be to modify the wiki structure so that the main topic were to be listed in their own folder, for example instead of having
http://wiki.bebits.com/page/BeBitsWikiSuggestions
you'd have
http://wiki.bebits.com/page/BeBits/WikiSuggestions,
and instead of
http://wiki.bebits.com/page/GlassElevatorJournalMarch2002
you'd have
http://wiki.bebits.com/page/GlassElevator/JournalMarch2002
To link between pages within the main group you'd use the traditional method (in our case, we could use
JournalMarch2002
to link to it from anothe page within the
GlassElevator
group. To link to a wiki page in a different main group, you'd have to first specify the main group, then the wiki page within that group. In our example, we'd have to use
BeBits.WikiSuggestions
to link to this particular page. This is not an impossible thing, it has already been implemented in a different wiki, but it is not indispensable either. I believe however that, if groups are not implemented and no other type of naming solution comes up, then we should start using teh aforementioned long naming format. One actual example (and this is nothing against its author, I did the same mistake in my early wikidays) is MultiUser - It is not clear what the page is about until you actually see it. Just like you should aptly name your variables in any programming language, so should you(we, I, he, she, or any other thing you can think of) name the pages well as to avoid confusion. -F|B
-
One thing I would very much appreciate to have is to have the "recent changes" links actually tell me what was changed. Right now, to see what changes were applied, I have to click on the page, hit [edit], and then go through a maze of previous versions and compare their contents. This will prove annoying when changes are subtle (and they mostly are). Of course, this would be more of a topic for the mantainers of the current wiki than for the people at BeBits, and I will not try to force anyone to change to another wiki flavor (IF I ever do it, however, then please put me out of misery by clubbing me with the next heavy blunt object that you come across until I'm inconscious) -F|B
-
Sometimes it is useful to put your initials on your comments, especially when it comes to hearty discussions -F|B
|
|
|
