Linguifex:Style policy: Difference between revisions

| file= Observe.png

| filesize= 100

| title1 = Policy

| title2 = Any suggestions or additions to this page's content shall be discussed on the page's discussion page.

:''See also: [[Linguifex:Policy]]''

This is the '''Style policy''', or Manual of Style, of '''Linguifex'''. This policy is a style guide for editing and creating articles, guides and languages on our wiki.

Any issues relating to style guidance can be discussed on the policy's talk page.

The standard and official language of Linguifex is [[wikipedia:English|English]].

*English is the language used in all articles on [[:Category:Conlangs|constructed languages]], [[:Category:Linguistics|linguistics]], [[:Category:Guides|guides]] et cetera. We prefer no major national variety of the language over any other. These varieties (e.g. [[w:British English|British English]], [[w:U.S. English|U.S. English]]) differ in vocabulary (''[[wiktionary:tap|tap]]'' vs ''[[wiktionary:faucet|faucet]]''), spelling (''[[wiktionary:centre|centre]]'' vs ''[[wiktionary:center|center]]''), and occasionally grammar.  

*Articles, guides, natural languages end FAQs may not be translated.

===Articles===

One of the most important parts of wiki editing is how to structure an article. The structure is a powerful thing: it dictates what information the reader reads and when he or she reads it. It can influence what people contribute, where it goes, and how it might be written. Structure has the power to inform or confuse the same way good or bad writing does. Keep a well structured article, and you're more likely to have a high quality one.

Use the <code>==</code> (two equal signs) style markup for main headings, equivalent to <code><nowiki><h2></nowiki></code>. '''Do not use a single <code>=</code>.''' This is because a single <code>=</code> creates an <code><nowiki><h1></nowiki></code> heading which is already used by the page header and would be bad coding. Also, do not use wikilinks in subject headings. When edited, these sections become confusing in the edit history because of the link code. Consider instead putting the word in the first or second sentence of the section and linking it there.

Avoid special characters in headings, such as an'' ampersand'' (&), a ''plus sign'' (+), ''curly brackets'' ({}), or ''square brackets'' ([]). In place of the ampersand, use the word "and" unless the ampersand is part of a formal name.