Difference between revisions of "ZineWiki:Manual of Style"

From ZineWiki
Jump to navigationJump to search
 
Line 3: Line 3:
 
Clear, informative, and unbiased writing is always more important than presentation and formatting (it's eaier for other editors to reformat and entry than edit one that isn't clear and unbiased). ZineWiki does not require writers to follow all or any of these rules, but their efforts will be more appreciated when they do so.
 
Clear, informative, and unbiased writing is always more important than presentation and formatting (it's eaier for other editors to reformat and entry than edit one that isn't clear and unbiased). ZineWiki does not require writers to follow all or any of these rules, but their efforts will be more appreciated when they do so.
  
==General Editing Guidelines==
+
==General Editing Guidelines (Read this before you get started!)==
ZineWiki is designed to be an online encyclopedia of [[zines]], [[zinesters]], zine resources, small publishing history and zine culture. Entries should be encyclopedia-like in nature. Avoid profanity, inside jokes, too much praise, plugging or hyping, and blatant commercialism. The idea is to list information and document zine history, not sell issues or promote yourself and your projects (i.e. list the contents a zine's issues, but don't list the ordering price and information).  
+
ZineWiki is designed to be an online encyclopedia of [[zines]], [[zinesters]], zine resources, small publishing history and zine culture. Entries should be encyclopedia-like in nature. Avoid profanity, inside jokes, too much praise, plugging or hyping, and blatant commercialism. The idea is to list information and document zine history, not sell issues or promote yourself and your projects (i.e. list the contents a zine's issues, but don't list the ordering price and information).
  
 
==Article titles==
 
==Article titles==

Revision as of 20:01, 3 August 2006

This Manual of Style has the simple purpose of making the encyclopedia easy to read by following a consistent format. The following rules do not claim to be the last word on ZineWiki style, but if everyone does it the same way, Zine Wiki will be easier to read and use, not to mention easier to write and edit. The editors of new and existing articles should strive to have their articles follow these guidelines.

Clear, informative, and unbiased writing is always more important than presentation and formatting (it's eaier for other editors to reformat and entry than edit one that isn't clear and unbiased). ZineWiki does not require writers to follow all or any of these rules, but their efforts will be more appreciated when they do so.

General Editing Guidelines (Read this before you get started!)

ZineWiki is designed to be an online encyclopedia of zines, zinesters, zine resources, small publishing history and zine culture. Entries should be encyclopedia-like in nature. Avoid profanity, inside jokes, too much praise, plugging or hyping, and blatant commercialism. The idea is to list information and document zine history, not sell issues or promote yourself and your projects (i.e. list the contents a zine's issues, but don't list the ordering price and information).

Article titles

If possible, make the title the page the subject of the first sentence of the article. The title should appear as early as possible in the article; preferably in the first sentence. The first time the article mentions the title, put it in bold using three apostrophes — '''article title''' produces article title. For example: "This Manual of Style is a style guide for ZineWiki."

As a general rule, do not put links in:

  • the bold reiteration of the title in the article's lead sentence or
  • any section title.

Also, try not to put other phrases in bold in the first sentence. Finally, keep the first sentence straight and to the point as to what the page is about.

Headings

Use the == (two equal signs) style markup for headings, not the ''' (triple apostrophes) used to make words appear bold. Start with ==, add the heading title, then end with ==.

This page is a work in progress...