Editing rules: Difference between revisions
Jump to navigation
Jump to search
(added formatting hint for <code>) |
|||
| Line 7: | Line 7: | ||
* if you created a opage that you know is not completed, add a horizontal rule (with ---- at the beginning of a line) at the end, and put TODO: <TASK TO DO> lines below that | * if you created a opage that you know is not completed, add a horizontal rule (with ---- at the beginning of a line) at the end, and put TODO: <TASK TO DO> lines below that | ||
* maybe it's a good idea if people can contact the author of a page they want contribute to - which is possible if everybody has contact data on their [[Special:Listusers| user page]] (no it's not arule that you should, but often it might help make the result better | * maybe it's a good idea if people can contact the author of a page they want contribute to - which is possible if everybody has contact data on their [[Special:Listusers| user page]] (no it's not arule that you should, but often it might help make the result better | ||
* You can make Your text more readable by using the <code> </code> tag for, say, filenames or shellcommands The result will look something like this <code>/path/to/my/file/here</code> or this: | * You can make Your text more readable by using the <code> </code> tag for, say, filenames or shellcommands The result will look something like this <code>/path/to/my/file/here</code> or this: <code> # apt-get remove --purge login</code> | ||
<code> # apt-get remove --purge login</code> | |||
---- | ---- | ||
* TODO: maybe we should have a naming scheme for some special page types, like pages describeing user-contributed classes, success stories, and stuff | * TODO: maybe we should have a naming scheme for some special page types, like pages describeing user-contributed classes, success stories, and stuff | ||
Revision as of 11:45, 11 August 2005
What would we be without rules?
some editing rules/hints
- please enter a summary of your edit before you save
- check the preview before you save
- please make sure that you put your content in the right context, browse through the wiki and use the search function to check that
- if you created a opage that you know is not completed, add a horizontal rule (with ---- at the beginning of a line) at the end, and put TODO: <TASK TO DO> lines below that
- maybe it's a good idea if people can contact the author of a page they want contribute to - which is possible if everybody has contact data on their user page (no it's not arule that you should, but often it might help make the result better
- You can make Your text more readable by using the <code> </code> tag for, say, filenames or shellcommands The result will look something like this
/path/to/my/file/hereor this:# apt-get remove --purge login
- TODO: maybe we should have a naming scheme for some special page types, like pages describeing user-contributed classes, success stories, and stuff