Sub-Editing
From Global Voices Wiki
Welcome to the Global Voices sub-editors guide. This is a reference document to help the community ensure high editorial standards across the entire GV site.
Contents |
Who is Who on Global Voices?
A lot of people are involved in making Global Voices tick day to day (including you!).
The easiest way to see who is who, is to visit:
What Sub-Editors Do
As volunteer sub-editors, we support the mission of Global Voices by helping all stories appear in a clear and professional manner. We have a feel for English as a second language, and we will do our best to perfect the language (grammar, style, and usage) without altering the structure or intent of the story. We have great respect and consideration for the author and editor of the stories, and communicate all doubts and significant changes directly to the editor.
Style Guide
For a comprehensive guide on GV style that all authors need to adhere to when posting, click here.
Sub-Editing Process
General Sub-Editing Process
The work between sub-editors and editors is organized as follows:
1. When an editor has finished preparing a story for publication he/she sends an email to gv-sub-editors@googlegroups.com with a link to the draft.
2. The first available sub-editor responds both to the Editor and to the Mailing List that he/she is available to edit.
3. The sub-editor makes changes and saves the post without publishing. He/she contacts the editor to let them know it's done, and includes any comments or advice for clarification or corrections by email.
Provisional Sub-Editing Process
New sub-editors undergo a provisional period, whereby they sub-edit three non-urgent posts as an 'author' so that they are unable to publish. These three posts are also double checked by a sub-editor.
1. When an editor has finished preparing a story for publication he/she sends an email to gv-sub-editors@googlegroups.com with a link to the draft.
2. If the story is non-urgent, a provisional sub-editor can email the group in response to accept.
3. The editor (or a manager) will assign the post to the provisional sub-editor's (author) account as soon as possible, and email back to indicate this has been done.
4. The provisional sub-editor makes their changes, saves them and notifies via email. A sub-editor now emails back to accept to double-check the post. He/she contacts the editor to let them know it's done, and includes any comments or advice for clarification or corrections by email.
5. The editor then publishes the post, once they have checked the corrections made and acted on any comments or advice for clarification or corrections flagged by provisional sub-editor/sub-editor.
Sub-Editors Checklist
The following items are reviewed and corrected by sub-editors.
1. The text (spelling, grammar, punctuation, language flow, formatting)
2. The title (max 8-10 words for the sake of embedded feeds)
3. The excerpt (see below text field, this appears on homepage)
4. Any thumbnail and featured images
Listing Contributors
It is important to credit everyone who helped create a post, not just the main Author. We have to do this by adding listing contributors text as there can only be one Author in the WordPress system.
A Contributor could be someone who helped translate the post, did a lot of sub-editing, or helped in any other way.
Place the ‘Contributors’ paragraph at the very end of every post, under even any ‘Extra Notes’ added. This allows it to match the Author credit directly below.
To add it please either use the ‘contributors’ button in the WordPress posting system, or just switch to html view and use the following code, although remember to replace the text with whatever is appropriate:
<p class="contributors">This post was proofread in English by Solana Larsen.</p>
If you are listing the name of someone who is part of Global Voices, please always link to their GV profile page (like this one) so that people can find their posts and bio information easily.
All sub-editors should be accredited at the bottom of a post with their name and a link to their online profile on Global Voices, using the following code:
