Journal #4997
Posted 16 years ago2008-04-10 06:33:46 UTC
TWHL3 Development Diary Thingie #5
The subject this time is the Wiki. I've discussed the functionality of the Wiki in Diary #2, but basically it'll be similar to the current entity guide and glossary, except editable. You'll be able to add links and lists and possibly tables, and so on.
The reason I'm not making it like a full Wiki (every page editable) is because it isn't needed. You can only edit the content pages for each entity, error or definition. You'll be able to add new entries, but only admins can add whole new categories.
The job of a Wiki moderator is to look over changes and approve or revert them. Users who spam and/or make stupid changes will eventually have their editing privileges removed, and possibly a ban from the site. Each entry will also have its own comments, which are only reserved for helpful additions to the entry. Comments will be screened before being added.
An example of a useful comment is a specific case for the use of say, an entity - "This entity can be used for Specific Case x, set parameter y to setting z, etc etc etc", or maybe a different solution than stated to a compile error - "This error can sometimes be fixed by using function x on entity y etc", and so on.
Some examples of useless comments:
In error guide: "hlp i got ths error an i duno wut 2 do plz help"
In entity guide: "how do i use this to do blah blah"
In Glossary: "o i get it now thx"
etc etc. I think you get the point.
Too many of these useless comments will mean you will have your editing privileges removed (includes commenting privileges). Users who contribute lots of helpful information in the wiki (tutorials too!) will be rewarded.
Anyway, that concludes this diary for today. Next time will be about user control and the strike system that is being implemented.
The subject this time is the Wiki. I've discussed the functionality of the Wiki in Diary #2, but basically it'll be similar to the current entity guide and glossary, except editable. You'll be able to add links and lists and possibly tables, and so on.
The reason I'm not making it like a full Wiki (every page editable) is because it isn't needed. You can only edit the content pages for each entity, error or definition. You'll be able to add new entries, but only admins can add whole new categories.
The job of a Wiki moderator is to look over changes and approve or revert them. Users who spam and/or make stupid changes will eventually have their editing privileges removed, and possibly a ban from the site. Each entry will also have its own comments, which are only reserved for helpful additions to the entry. Comments will be screened before being added.
An example of a useful comment is a specific case for the use of say, an entity - "This entity can be used for Specific Case x, set parameter y to setting z, etc etc etc", or maybe a different solution than stated to a compile error - "This error can sometimes be fixed by using function x on entity y etc", and so on.
Some examples of useless comments:
In error guide: "hlp i got ths error an i duno wut 2 do plz help"
In entity guide: "how do i use this to do blah blah"
In Glossary: "o i get it now thx"
etc etc. I think you get the point.
Too many of these useless comments will mean you will have your editing privileges removed (includes commenting privileges). Users who contribute lots of helpful information in the wiki (tutorials too!) will be rewarded.
Anyway, that concludes this diary for today. Next time will be about user control and the strike system that is being implemented.
2 Comments
You must log in to post a comment. You can login or register a new account.
It's simply awesome.