Openembedded.org:Help - Revision history

Laibsch: /* Categorization */

2009-02-25T08:57:47Z

Categorization

← Older revision		Revision as of 08:57, 25 February 2009
Line 17:		Line 17:
	* The use of abbreviations should be avoided when they would be confusing to the reader. Do not invent abbreviations or acronyms.		* The use of abbreviations should be avoided when they would be confusing to the reader. Do not invent abbreviations or acronyms.
	* Use the simplest markup to display information in a useful and comprehensible way. Markup may appear differently in different browsers. Use HTML and CSS markup sparingly and only with good reason. Minimizing markup in entries allows easier editing.		* Use the simplest markup to display information in a useful and comprehensible way. Markup may appear differently in different browsers. Use HTML and CSS markup sparingly and only with good reason. Minimizing markup in entries allows easier editing.

	~~== Categorization ==~~
	* Every page should belong to at least one category. An article's category or categories should reflect the topics and classes that are directly related to the subject. In writing an article, use the most likely categories in which the reader would look for, if they are not sure of where to find the article.

Laibsch at 08:52, 25 February 2009

2009-02-25T08:52:03Z

← Older revision		Revision as of 08:52, 25 February 2009
Line 1:		Line 1:
	'''This page describes principles and guidelines for using this wiki (not Openembedded itself). Understand this as a best-practice suggestion. ~~Try~~ to follow it. ~~But nobody will punish you if not.''' ;-)~~		'''This page describes principles and guidelines for using this wiki (not Openembedded itself). Understand this as a best-practice suggestion. We'd appreciate if you tried to follow it.

	== Naming ==		== Naming ==

Sledz: principles and guidelines for using this wiki

2009-02-16T13:28:34Z

principles and guidelines for using this wiki

New page

'''This page describes principles and guidelines for using this wiki (not Openembedded itself). Understand this as a best-practice suggestion. Try to follow it. But nobody will punish you if not.''' ;-)

== Naming ==
* The names of articles should be optimized for ''readers'' over ''editors''.
* Use the original, ''official'' naming from the outer world (for example, Openmoko instead of OpenMoko) with a reasonable minimum of ambiguity.
* Do not capitalize second and subsequent words unless the title is almost always capitalized in English (for example, proper names).
* In general only create page titles that are in the singular, unless that noun is always in a plural form in English.
* Avoid the use of abbreviations, including acronyms, in page naming unless the term you are naming is almost exclusively known only by its abbreviation and is widely known and used in that form.
* Page names should not begin with non-alphanumeric characters.
* Do not use an article name that suggests a hierarchy of articles.

== Style ==
* Style and formatting should be applied consistently within articles, though not necessarily throughout the wiki as a whole.
* Titles should be short—preferably fewer than ten words.
* Section names should preferably be unique within a page.
* For acronyms and abbreviations write out both the full version and the abbreviation at first occurrence.
* The use of abbreviations should be avoided when they would be confusing to the reader. Do not invent abbreviations or acronyms.
* Use the simplest markup to display information in a useful and comprehensible way. Markup may appear differently in different browsers. Use HTML and CSS markup sparingly and only with good reason. Minimizing markup in entries allows easier editing.

== Categorization ==
* Every page should belong to at least one category. An article's category or categories should reflect the topics and classes that are directly related to the subject. In writing an article, use the most likely categories in which the reader would look for, if they are not sure of where to find the article.