Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some general tidy up #80

Merged
merged 13 commits into from
Aug 11, 2022
162 changes: 162 additions & 0 deletions guidelines/style-guidelines.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,162 @@
## Table of contents
Aerozol marked this conversation as resolved.
Show resolved Hide resolved
Aerozol marked this conversation as resolved.
Show resolved Hide resolved

1. [How we write](#how-we-write)
2. [Grammar and punctuation](#grammar-and-punctuation)
3. [Links](#links)
4. [Lists](#lists)
5. [Numbers](#numbers)
6. [Symbols, currency and abbreviations](#Symbols,-currency-and-abbreviations)
7. [Common terms](#common-terms)


## How we write

#### Voice and tone

MetaBrainz speaks in a friendly, direct and easily understandable manner. We:
* use plain, simple, language when possible
* use short sentences
* use an active voice (avoid the passive tense).
Aerozol marked this conversation as resolved.
Show resolved Hide resolved

#### Spelling

We use US English.
Aerozol marked this conversation as resolved.
Show resolved Hide resolved
Aerozol marked this conversation as resolved.
Show resolved Hide resolved

#### Active and passive writing

Active writing mentions the subject (the person or thing 'doing' the action) first in the sentence (for example, inflation pushed up house prices).

Passive writing mentions the object (the person or thing 'receiving' the action) first. Passive sentences often include 'by' (for example, house prices were pushed up by inflation).

Active writing is more direct and should be used most of the time. We use short, clear sentences.


## Grammar and punctuation

#### Exclamation marks

We don't use exclamation marks in most instances - for instance, we don't use exclamation marks in documentation or page content.
Aerozol marked this conversation as resolved.
Show resolved Hide resolved
Aerozol marked this conversation as resolved.
Show resolved Hide resolved

#### Colon and semi-colons

We avoid these. When possible we’ll write 2 sentences instead, or separate the clauses using a dash (with a space on either side).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why? :( I mean, dashes are ok, but I really don't like this obsession with it being a replacement for everything somehow. https://thenarrativearc.org/blog/2020/2/4/epic-grammar-battle-semicolon-versus-em-dash for example. Sometimes text just flows better with a colon or a semicolon.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Short sentences are always better, particularly for people who might be reading in a second language, or have other reading difficulties. Though I am a chronic long sentencer-er... I try and keep myself in check. So I think it's a good reminder that a colon/dash could often just be two sentences instead. I stand behind that bit.

Otherwise I don't think it's about never using a colon or a semi colon, just being consistent when you are choosing between the two. We could easily swap this to be 'avoid dashes'?

For me it is quite noticeable if someone is writing with a lot of dashes - it's pretty distinct - or if they're using a lot of semicolons; also very distinct. So either way it's nice to offer guidance if someone is wondering which to go with.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, trying to have shorter sentences is not a bad idea. Maybe this should be "Colons, semicolons and dashes": "If it makes sense, write two shorter sentences rather than using these" then?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to gently encourage one of these three over the others 'colons, semicolons and dashes'.
Not because I hate any of them, but for consistency across different authors.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was taught that em dashes are for interruptions of thought, not a replacement for the semicolon, though I suppose it's a matter of style. :) If I'm presenting a list of items, I'd usually use a colon. (As this document does several times.)

This part I agree with: "when possible we’ll write 2 sentences instead." But I'm not sure I'd encourage dashes as a catch-all replacement for colons and semicolons. I'd just say to avoid all three unless two separate sentences sounds clunky. (That's probably not often.)

Copy link

@jesus2099 jesus2099 Aug 3, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In French, dashes are apposition, that can also be written with (round) parenthesis or even with comma (but it's more oral style, then).
It is very different from colons and semi-colons.


#### Apostrophes

We generally don’t add an extra 's' after nouns or names ending in 's'.
For example: "The business’ work" – not "the business’s work."

We don’t use an apostrophe for dates, numbers, or plurals of abbreviations.
For example: 1960s.

#### Bold

We rarely use bold – using too much will make it difficult for users to know which parts of your content they need to pay the most attention to. To emphasise words or phrases, we:
Aerozol marked this conversation as resolved.
Show resolved Hide resolved
* put key information at the start of sentences
* use headings
Aerozol marked this conversation as resolved.
Show resolved Hide resolved

#### Capitals

We only use capitals for proper nouns, such as:
* names of people, places and things, including buildings and brands
* titles, such as: of books, albums, recordings
Aerozol marked this conversation as resolved.
Show resolved Hide resolved

'Types' of places are not capitalized, unless referring to a specific place.
For example: "I like the library" - and "I like my local Library"
Aerozol marked this conversation as resolved.
Show resolved Hide resolved
Aerozol marked this conversation as resolved.
Show resolved Hide resolved

Generally, terms are not proper nouns, so should not be capitalised. Technical terms are not proper nouns. But if a word or term is branded as a distinct thing, treat it as a proper noun.
Aerozol marked this conversation as resolved.
Show resolved Hide resolved

#### Headings

We use sentence case so only the first letter is upper case. We never link headings.
Aerozol marked this conversation as resolved.
Show resolved Hide resolved
Aerozol marked this conversation as resolved.
Show resolved Hide resolved

#### Quotation marks

We use double quotation marks for:
* exact quotations
* direct speech.

We use single quotation marks for:
* technical terms (the first time it is used)
* classification descriptors
Aerozol marked this conversation as resolved.
Show resolved Hide resolved
Aerozol marked this conversation as resolved.
Show resolved Hide resolved
* titles of documents or publications
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not just always use double quotation marks?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you write "technical term" with double guotes I assume you're quoting a line from someone else or from a specific source, which wouldn't be the case with these. Perhaps that's just what I learnt in school? But that makes sense to me

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, I guess my idea was "drop those two, use double quotes for titles". But if single quotes for that is a generally accepted convention, then fine by me.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I was taught to use single quotation marks for quotes-inside-quotes, but I don't remember them having special meaning otherwise. Is there an existing style guide that recommends this usage?



## Links

We:
* link to relevant content on our website before we link to external websites
* never link headings
Aerozol marked this conversation as resolved.
Show resolved Hide resolved
Aerozol marked this conversation as resolved.
Show resolved Hide resolved
* write descriptive links that tell you what you’ll find when you follow them - not 'click here'
* don't set links to open in a new tab or window, with exceptions to be decided case by case.
Aerozol marked this conversation as resolved.
Show resolved Hide resolved
Aerozol marked this conversation as resolved.
Show resolved Hide resolved


## Lists

We use bulleted lists (coded as unordered lists) to list items or points, and numbered lists (coded as ordered lists) for processes where the order of steps is important.

We try to:
* keep our lists short (2–7 items)
* only use 1 level of nesting.

We use 2 types of bulleted lists – single-sentence lists and multi-sentence lists.

When we’re writing a single-sentence list, we:
* start with a stem sentence that all the points have in common
* start each point in lower case, and only use a full stop on the last point
Aerozol marked this conversation as resolved.
Show resolved Hide resolved
* don't use 'and' or 'or' on the second-to-last point
Aerozol marked this conversation as resolved.
Show resolved Hide resolved
Aerozol marked this conversation as resolved.
Show resolved Hide resolved
* check that each point makes a full sentence when read with the stem.

Multi-sentence lists are introduced by a complete sentence.
* Each point in the list is also a complete sentence.
* Each point can be 1–3 sentences long.
* Each point begins with a capital letter and ends with a full stop.


## Numbers

In general:
* we use numerals instead of words when we write numbers – this helps you scan our content
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Even if it's "you have two options" or "you can pick up to three"?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was very curious about this too! I always learned to write out the number in words up until... 8? or 10?

I do like the point here about helping to scan content. Makes it very easy to pick out numbers in a paragraph if you're looking for them. But happy to replace with 'use words up until x, then use numbers', if you think that's better.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think "use words from 0-9" and "use digits for 10 and up" seems reasonable. I learned something similar (though I don't remember the exact cutoff). One situation where I think digits look odd (especially for small numbers) is at the beginning of a sentence: "Two options are available." vs. "2 options are available."

* we use commas and no spaces to separate thousands when the number is over 10,000
* when we’re talking about numbers in the millions, we use the word 'million' instead of writing out the number in full
* we use spaces to separate groups of numbers when we write phone numbers.


## Symbols, currency and abbreviations

#### Symbols

We use:
* % – not 'percent' or 'per cent'
* & – only if it’s part of a brand name
* KB for kilobyte, MB for megabyte, and GB for gigabyte, for example 122 KB.

#### Currency

We put both the currency code and currency symbol before any amounts of money we write.
We don't use spaces between the code, symbol and amount.

For example:
* 'If you’re a United States citizen, you pay USD$640'.
* 'If you’re an Australian citizen it costs AUD$890'.
Aerozol marked this conversation as resolved.
Show resolved Hide resolved
Aerozol marked this conversation as resolved.
Show resolved Hide resolved

#### Abbreviations

We expand all abbreviations when we use them for the first time on a page.
For example: 'Welcome to MusicBrainz (MB)'.

To make our content easier to read, we avoid using:
* e.g.
* i.e.
* etc.
Aerozol marked this conversation as resolved.
Show resolved Hide resolved
Aerozol marked this conversation as resolved.
Show resolved Hide resolved

These are often written in full, such as:
* for example
* such as
* that is
* and so on.


## Common terms

We refer to people who use our data, sites and applications as 'user'/'users'
Aerozol marked this conversation as resolved.
Show resolved Hide resolved
Aerozol marked this conversation as resolved.
Show resolved Hide resolved