Rules and guidelines: Difference between revisions

From MozillaZine Knowledge Base
Jump to navigationJump to search
No edit summary
(Firebird --> Firefox)
Line 5: Line 5:
* I've tried to create categories.  When possible, follow the existing categorical structure for new categories.
* I've tried to create categories.  When possible, follow the existing categorical structure for new categories.
** Subcategories are shown off by using "space colon space" ( : )
** Subcategories are shown off by using "space colon space" ( : )
** Good: [[Firebird : Tips : Profile | Firebird : Tips : Profile]]
** Good: [[Firefox : Tips : Profile | Firefox : Tips : Profile]]
** Bad: Firebird:Tips :profile
** Bad: Firefox:Tips :profile
* Application Name links should only use the App Name, not "Mozilla App Name" except the Suite, which should be linked to and called "Mozilla Suite", not "Mozilla", "Suite", "Seamonkey", or any other name.
* Application Name links should only use the App Name, not "Mozilla App Name" except the Suite, which should be linked to and called "Mozilla Suite", not "Mozilla", "Suite", "Seamonkey", or any other name.
* Layout issues or other things should use Gecko as the App Name.  We need to work out what to use when something affects more than one app, or if we should just split them apart or use redirects.
* Layout issues or other things should use Gecko as the App Name.  We need to work out what to use when something affects more than one app, or if we should just split them apart or use redirects.

Revision as of 20:00, 9 February 2004

I've done a major cleanup of the front page and the links. A few new rules for editing:

Naming Conventions

  • All link words should start with a capital letter.
  • I've tried to create categories. When possible, follow the existing categorical structure for new categories.
  • Application Name links should only use the App Name, not "Mozilla App Name" except the Suite, which should be linked to and called "Mozilla Suite", not "Mozilla", "Suite", "Seamonkey", or any other name.
  • Layout issues or other things should use Gecko as the App Name. We need to work out what to use when something affects more than one app, or if we should just split them apart or use redirects.

Specificity

  • For the Suite, we have to decide how granular to get, and if we want to futher break things down by component (Browser/Mail and News/Editor/Chatzilla).

Editing Courtesy

  • If you find yourself wanting to change an entry back to an earlier revision, ask yourself if the current version had a useful purpose, and whether it really is necessary to change it back.
  • Document reasons for potentially controversial changes on the Talk pages.
  • Accept changes to your entries in a spirit of helpfulness.
  • We should have a protocol for when someone consistently makes certain types of mistakes or formatting quirks. Place a message in their User page? Email directly?

Miscellaneous