Difference between revisions of "Guidë Shkrimi"

From Open Labs Hackerspace
Jump to navigation Jump to search
(Translate)
(Marked this version for translation)
Line 1: Line 1:
 
<languages />
 
<languages />
 
<translate>
 
<translate>
 +
<!--T:2-->
 
At Open Labs we strive to create a decentralized environment where every member is empowered and encouraged to help shape experiences for the whole community, that means that often every member has the same access privileges to our communication channels. While this creates a sustainable process of collaborating within a community, it can also lead to inconsistency in ways we communicate, frame documentation or generally percept things within the community. For this reason, we have started creating a Style Guide for the writing components of the communication channels Open Labs is present on. This includes (but is not limited to) event names, blog post titles and social media content.
 
At Open Labs we strive to create a decentralized environment where every member is empowered and encouraged to help shape experiences for the whole community, that means that often every member has the same access privileges to our communication channels. While this creates a sustainable process of collaborating within a community, it can also lead to inconsistency in ways we communicate, frame documentation or generally percept things within the community. For this reason, we have started creating a Style Guide for the writing components of the communication channels Open Labs is present on. This includes (but is not limited to) event names, blog post titles and social media content.
  
=Titles=
+
=Titles= <!--T:3-->
  
 +
<!--T:4-->
 
Titles should be straightforward and unbiased with no subjective tone (until necessary). Filler words should be avoided and the less the better, so try to cut down on words and distill the title of your content to how little possible.
 
Titles should be straightforward and unbiased with no subjective tone (until necessary). Filler words should be avoided and the less the better, so try to cut down on words and distill the title of your content to how little possible.
  
==Case==
+
==Case== <!--T:5-->
  
 +
<!--T:6-->
 
For any titles (including Menus, Wiki pages, Blog post titles and Event Names) we use Title Case.
 
For any titles (including Menus, Wiki pages, Blog post titles and Event Names) we use Title Case.
 
In general, the following capitalization rules apply across the four styles in title case:
 
In general, the following capitalization rules apply across the four styles in title case:
  
 +
<!--T:7-->
 
* Capitalize the first word in the title
 
* Capitalize the first word in the title
 
* Capitalize the last word in the title
 
* Capitalize the last word in the title
 
* Capitalize the important words in the title
 
* Capitalize the important words in the title
  
 +
<!--T:8-->
 
Important words in that last bullet generally refer to:
 
Important words in that last bullet generally refer to:
  
 +
<!--T:9-->
 
* Adjectives (tiny, large, etc.)
 
* Adjectives (tiny, large, etc.)
 
* Adverbs (quietly, smoothly, etc.)
 
* Adverbs (quietly, smoothly, etc.)
Line 25: Line 31:
 
* Verbs (write, type, create)
 
* Verbs (write, type, create)
  
 +
<!--T:10-->
 
While the above words are generally capitalized in titles regardless of style, there are some words that are generally not capitalized when using title case. These include short words and conjunctions:
 
While the above words are generally capitalized in titles regardless of style, there are some words that are generally not capitalized when using title case. These include short words and conjunctions:
  
 +
<!--T:11-->
 
* Articles (a, an, the)
 
* Articles (a, an, the)
 
* Coordinating Conjunctions (and, but, for)
 
* Coordinating Conjunctions (and, but, for)
 
* Short (less than 5 letters) Prepositions (at, by, from)
 
* Short (less than 5 letters) Prepositions (at, by, from)
  
===Example===
+
===Example=== <!--T:12-->
  
 +
<!--T:13-->
 
''WRONG:'' Open Labs members meeting - January
 
''WRONG:'' Open Labs members meeting - January
  
 +
<!--T:14-->
 
''CORRECT:'' Open Labs Members Meeting - January
 
''CORRECT:'' Open Labs Members Meeting - January
  
==And==
+
==And== <!--T:15-->
  
 +
<!--T:16-->
 
In Titles, we generally prefer to use the symbol & instead of the equivalent word "and".
 
In Titles, we generally prefer to use the symbol & instead of the equivalent word "and".
  
===Example===
+
===Example=== <!--T:17-->
  
 +
<!--T:18-->
 
''WRONG:'' LibreOffice Month 2017 - Collabora Online and Nextcloud  
 
''WRONG:'' LibreOffice Month 2017 - Collabora Online and Nextcloud  
  
 +
<!--T:19-->
 
''CORRECT:'' LibreOffice Month 2017 - Collabora Online & Nextcloud  
 
''CORRECT:'' LibreOffice Month 2017 - Collabora Online & Nextcloud  
  
==Relevant Order==
+
==Relevant Order== <!--T:20-->
  
 +
<!--T:21-->
 
To allow for better visual scanning, it is preferred to start the title with the name of the topic/project it is about. The type of activity or other details related to the former, should come afterwards.
 
To allow for better visual scanning, it is preferred to start the title with the name of the topic/project it is about. The type of activity or other details related to the former, should come afterwards.
  
===Example===
+
===Example=== <!--T:22-->
  
 +
<!--T:23-->
 
''WRONG:'' Workshop about Quad9
 
''WRONG:'' Workshop about Quad9
  
 +
<!--T:24-->
 
''CORRECT:'' Quad9 Workshop
 
''CORRECT:'' Quad9 Workshop
  
 +
<!--T:25-->
 
Note: Exceptions can be made and rules can be bent here. Consult with other members if unsure or just go with your gut feeling.  
 
Note: Exceptions can be made and rules can be bent here. Consult with other members if unsure or just go with your gut feeling.  
  
==Edition Numbers==
+
==Edition Numbers== <!--T:26-->
  
 +
<!--T:27-->
 
Often, especially for events, we numerize the edition of the event to indicate the event number. In the past we have been using inconsistent ways for this, ranging from "'''Nr1''' to '''nr 1''' and '''#'''". The correct way to indicate editions is '''Nr.1''' however. As it is Title Case friendly and '''#''' doesn't work on MediaWiki, it is the most suitable choice.
 
Often, especially for events, we numerize the edition of the event to indicate the event number. In the past we have been using inconsistent ways for this, ranging from "'''Nr1''' to '''nr 1''' and '''#'''". The correct way to indicate editions is '''Nr.1''' however. As it is Title Case friendly and '''#''' doesn't work on MediaWiki, it is the most suitable choice.
  
===Example===
+
===Example=== <!--T:28-->
  
 +
<!--T:29-->
 
''WRONG:'' Red Hat Career Day #2
 
''WRONG:'' Red Hat Career Day #2
  
 +
<!--T:30-->
 
''CORRECT:'' Red Hat Career Day Nr.2
 
''CORRECT:'' Red Hat Career Day Nr.2
 
</translate>
 
</translate>

Revision as of 21:16, 3 January 2018

Other languages:
English • ‎shqip

At Open Labs we strive to create a decentralized environment where every member is empowered and encouraged to help shape experiences for the whole community, that means that often every member has the same access privileges to our communication channels. While this creates a sustainable process of collaborating within a community, it can also lead to inconsistency in ways we communicate, frame documentation or generally percept things within the community. For this reason, we have started creating a Style Guide for the writing components of the communication channels Open Labs is present on. This includes (but is not limited to) event names, blog post titles and social media content.

Titles

Titles should be straightforward and unbiased with no subjective tone (until necessary). Filler words should be avoided and the less the better, so try to cut down on words and distill the title of your content to how little possible.

Case

For any titles (including Menus, Wiki pages, Blog post titles and Event Names) we use Title Case. In general, the following capitalization rules apply across the four styles in title case:

  • Capitalize the first word in the title
  • Capitalize the last word in the title
  • Capitalize the important words in the title

Important words in that last bullet generally refer to:

  • Adjectives (tiny, large, etc.)
  • Adverbs (quietly, smoothly, etc.)
  • Nouns (tablet, kitchen, book)
  • Pronouns (they, she, he)
  • Subordinating conjunctions (as, so, that)
  • Verbs (write, type, create)

While the above words are generally capitalized in titles regardless of style, there are some words that are generally not capitalized when using title case. These include short words and conjunctions:

  • Articles (a, an, the)
  • Coordinating Conjunctions (and, but, for)
  • Short (less than 5 letters) Prepositions (at, by, from)

Example

WRONG: Open Labs members meeting - January

CORRECT: Open Labs Members Meeting - January

And

In Titles, we generally prefer to use the symbol & instead of the equivalent word "and".

Example

WRONG: LibreOffice Month 2017 - Collabora Online and Nextcloud

CORRECT: LibreOffice Month 2017 - Collabora Online & Nextcloud

Relevant Order

To allow for better visual scanning, it is preferred to start the title with the name of the topic/project it is about. The type of activity or other details related to the former, should come afterwards.

Example

WRONG: Workshop about Quad9

CORRECT: Quad9 Workshop

Note: Exceptions can be made and rules can be bent here. Consult with other members if unsure or just go with your gut feeling.

Edition Numbers

Often, especially for events, we numerize the edition of the event to indicate the event number. In the past we have been using inconsistent ways for this, ranging from "Nr1 to nr 1 and #". The correct way to indicate editions is Nr.1 however. As it is Title Case friendly and # doesn't work on MediaWiki, it is the most suitable choice.

Example

WRONG: Red Hat Career Day #2

CORRECT: Red Hat Career Day Nr.2