Style guide: Difference between revisions
No edit summary |
No edit summary |
||
Line 37: | Line 37: | ||
* '''Always run a spell check!''' Make sure that you have used international or UK English throughout your contribution. | * '''Always run a spell check!''' Make sure that you have used international or UK English throughout your contribution. | ||
* Have you referenced in footnotes? Don't! '''Make sure all references are at the end of the document''', and referred to in square brackets: [1]. | * Have you referenced in footnotes? Don't! '''Make sure all references are at the end of the document''', and referred to in square brackets: [1]. | ||
*APC, including GenderIT.org, follows the Chicago style of reference listing. If you're not sure, there's a | *APC, including GenderIT.org, follows the Chicago style of reference listing. If you're not sure, there's a [https://www.apc.org/en/system/files/APCReferenceGuide_200905.pdf guide] . | ||
Some examples of referencing: | Some examples of referencing: |
Revision as of 14:11, 8 January 2015
This page gives advice and guidelines on the technicalities of writing for both GenderIT.org and the Association for Progressive Communication.
Clear, simple writing should be the goal of all GenderIT.org contributors. Contributors need to keep in mind GenderIT.org's large audience, that it is international, and the majority of our readers are not native speakers of English. When writing it is important to ask, can my reader understand this? Using clear, simple language, making sure that you do not use phrases that might not make sense when directly translated. Examples include phrases such as 'keeping your hand in', 'putting a lid on it' or 'having a clear head'.
Never write gender blind, and try to use as few references as possible to gender blind material. It rarely matters what a women wears, what her age or marital status are, or her sexual orientation. These are only relevant if they are important for a point being made. Read an alternative paragraph/ sentence aloud, just to see if it makes sense without that material.
Always refer to people by their pronoun and gender of choice. Do not refer to any 'alternative' (such as 'born a woman') unless it is relevant to the point being made.
Refer to people in a way that empowers and strengthens – survivors of sexual abuse, people living with HIV/ AIDS. People are not defined by trauma, disease, disability or gender.
GenderIT.org strives to write in a style that is less formal, but avoid contractions (e.g. don’t, I’ll, isn’t) because they are often not used in other languages and might confuse non-native English speakers.
Do not capitalise technological terms because that makes them seem Far More Important and Impenetrable than they really are. So words like internet, information society, free/libre and open source software, gender or civil society should be not capitalised unless they are within proper nouns (e.g. name of programme “Gender Equality & Information Society National Plan”).
Refer to the Jargon section of the website if you are unsure how to use a technical term or phrase. If you are using a technical term or phrase that is not in jargon, please highlight it for the editorial team to consider adding to the Jargon section.
Before you start writing, make sure you are familiar with the APC editorial guidelines, which deals with house styles in terms of grammar and capitalisation.
In particular:
- Do not capitalise every single word in the titles and subtitles of the article.
- All acronyms must be spelled out in full when they are first mentioned in the article (remember that our primary audience are women’s organisation who are not focussed on ICTs, and who do not need to be familiar with commonly used acronyms in the field of ICTs).
- If you are citing material that is available online, always provide a link to the original source as a matter of courtesy and good internet conduct.
- Make sure you always have permission to republish any article(s) and/or photo(es) on the website from the original author/source (with the exception of writings that are sourced as APC, including APC programmes such as APC WNSP, and APC Africa, and LAC Monitor).
- Keep a record of the permission provided, and forward it to the Spanish or English language editors for documentation.
- You can quote 1-2 paragraphs of an article in your writing without needing prior author’s permission. Again provide a link to the original article as a matter of courtesy and good internet conduct.
- If you republish original articles written exclusively for genderIT.org, you must mention genderIT.org as a source. Please inform editorial team of external sites about this condition. Please refer to the APC Editorial Policy for more information.
- Consistently cite all resources and sources that you use in your writing.
- For interviews, please include in your submission, these information about the interviewees:
- Full name;
- Where s/he is based;
- Where s/he is attached to professionally;
- Her/his expertise in the field that is the focus of your article.
Final checklist:
- Always run a spell check! Make sure that you have used international or UK English throughout your contribution.
- Have you referenced in footnotes? Don't! Make sure all references are at the end of the document, and referred to in square brackets: [1].
- APC, including GenderIT.org, follows the Chicago style of reference listing. If you're not sure, there's a guide .
Some examples of referencing:
Books: Janet May-Chin, Women organising for change, (Kuala Lumpur: Women's Development Collective/ Persatuan Sains Sosial Malaysia, 2001) 23-25
Online journals/ newspapers: Danah m. boyd and Nicole B. Ellison “Social network sites: Definition, history, and scholarship” Journal of Computer-Mediated Communication 13, 1 (2007) jcmc.indiana.edu/vol13/issue1/boyd.ellison.html
Note: This is the same as print newspapers or journals, but with the URL, no http ://)
Website Cite the URL, without the 'http ://', only include the date accessed if the document is a wiki (to allow accurate tracking of information cited).
www.apc.org