Main Page: Difference between revisions
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
If you look for an entry and can't find it, you can [[starting an entry|start one]], if you can't write the whole thing, you can [[stub|mark it a stub]]. | If you look for an entry and can't find it, you can [[starting an entry|start one]], if you can't write the whole thing, you can [[stub|mark it a stub]]. | ||
When you write anything for this wiki, keep it short and concise - this is for information, not entertainment. When you find an entry getting much longer than what fits onto one screen, consider if it can be split into sub-entries. There is no hard rule there, just think of usability as a reference. Sometimes point form (i.e. starting lines with a *) is OK. | |||
Revision as of 21:44, 2008 March 12
CCMDB now has a Wiki
A more organized front page will evolve in the future, and I will set up accounts for all CCMDB staff to edit the contents of this wiki. As a first real-use entry, I am adding the instructions to install the Real Time Update for the rx1950 PDAs.
These instructions are in the IT Instructions Category and I will move other instructions we have into that category as I go along.
Be Bold!
The main idea of using a wiki to put information like this is that any of us can add, update and improve it. If you see a typo, a run-on sentence or something that is not stated clearly, edit it by clicking the edit tab a the top. As per wikipedia, the one of the most important directions that come to mind is be bold. Make the changes, don't be too concerned that you may have misunderstood. The wiki keeps track of all changes, and if something goes really wrong, we can revert to an earlier one. To see what I mean, check out the history tab on any page.
If you look for an entry and can't find it, you can start one, if you can't write the whole thing, you can mark it a stub.
When you write anything for this wiki, keep it short and concise - this is for information, not entertainment. When you find an entry getting much longer than what fits onto one screen, consider if it can be split into sub-entries. There is no hard rule there, just think of usability as a reference. Sometimes point form (i.e. starting lines with a *) is OK.