Official NixOS Wiki:Contributing: Difference between revisions

Line 9:

# '''Networked''': the manuals are ''sequential'' with one chapter following another while the wiki is ''networked'', with various articles linked to one another in various ways, allowing the user to reach information in multiple ways.

# '''Community''': the manuals cover the more official and stable core of the Nix ecosystem, while the wiki can cover the whole Nix community with its diverse projects and communication channels.

==Style==

===Language===

Discussion articles should be written in clear, standard and professional language. To this end, the following considerations apply:

* ''Vocabulary'': use the simplest and most conventional words and expressions you can find to get your point across without oversimplifying.

* ''Organization'': keep your text structured in coherent sentences, paragraphs and sections, each with its own clear themes and topics.

* ''Citations'': citations aren't required, but definitely appreciated; when citing code, hardlink to a particular revision.

* ''Attribution'': where external material is quoted or utilized in the article, and/or licensing or common sense demands it, place clear and complete attribution and (where possible) a link.

* ''Code'': code examples should be cogent and illustrative of the surrounding text (otherwise they would normally go in one of the other article types).

== Tagging Articles ==

@@ Line 9: / Line 9: @@
 # '''Networked''': the manuals are ''sequential'' with one chapter following another while the wiki is ''networked'', with various articles linked to one another in various ways, allowing the user to reach information in multiple ways.
 # '''Community''': the manuals cover the more official and stable core of the Nix ecosystem, while the wiki can cover the whole Nix community with its diverse projects and communication channels.
+==Style==
+===Language===
+Discussion articles should be written in clear, standard and professional language. To this end, the following considerations apply:
+* ''Vocabulary'': use the simplest and most conventional words and expressions you can find to get your point across without oversimplifying.
+* ''Organization'': keep your text structured in coherent sentences, paragraphs and sections, each with its own clear themes and topics.
+* ''Citations'': citations aren't required, but definitely appreciated; when citing code, hardlink to a particular revision.
+* ''Attribution'': where external material is quoted or utilized in the article, and/or licensing or common sense demands it, place clear and complete attribution and (where possible) a link.
+* ''Code'': code examples should be cogent and illustrative of the surrounding text (otherwise they would normally go in one of the other article types).
 == Tagging Articles ==