Author guide

RACKWiki is a harm-reductive educational resource open to any contributors. While we acknowledge that we cannot eliminate accidents, we believe the more educated and well-rounded we are as practitioners, the more we can reduce harm in our community.

Getting Started

Create an Account

An account is required to contribute to RACKWiki.

1. Create an account with username, password, and email. While you may use a pseudonym for your username, an active email is required.
2. Confirm your email address. Confirmation email may be located in your spam folder. Resend confirmation email from the email portion of your preferences page if needed.

While new users may immediately begin editing and creating within the site, those changes will not be published until they have been approved by an editor. After multiple successful contributions, the user will be granted author level access which will allow the user to publish directly without review of an editor.

Contributing

Guidelines

In order to make RACKWiki as direct and useful as possible, we encourage authors to:

• Be thorough but concise
• Include reference citations
• Frame articles through lens of harm-reductive practices
• Use consistent style and language within an article
• Use bulleted lists and tables when possible

New Articles

In order to create an article, first, log in.

Begin by typing in the name of the article you want to create in the search bar at the top of the page.

Creating an article

*Info about seeding an article/editing existing heading

• Info about using Article Templates

User levels

User: Level upon creation of profile. Can create/edit, requires editor approval before publishing.

Author: Create/edit without editor approval, promoted with one or more substantive contributions

Editor: Can approve or reject User contributions, edit most protected pages

Administrator: Edit all protected pages and site set up.

Manual of Style

Title

The article title should be a recognizable name or description of the topic that is natural, sufficiently precise, concise, and consistent with those of related articles. Capitalize the initial letter, but otherwise follow sentence case. Do not use articles in titles unless they are inseparable part of the name.

The following naming conventions are followed for individual topics:

• Articles about drugs or medicines should use the International Nonproprietary Name (INN). Common trade names should be included in the lead section.
• Articles about chemicals should use IUPAC nomenclature if that name is in common use. If not, use the most common name, and mention the IUPAC name in the lead.

Sections

The content of the article should begin with an introductory lead section, which does not have a section heading. The rest of the article is divided into sections. There are several available boilerplate section lists for common themes (kink activity, medicine, and so on).Linguistic choices of English

Linguistic choices

RACKWiki uses US English spelling in its articles.

Formatting

Dates and time

Use the format 1 January 1970 or January 1, 1970 when writing out dates. For lists and tables, YYYY-MM-DD can also be used.

Units of measurement

Use SI measurements. Customary conversions can be provided in parenthesis.

Grammar and usage

By default, write articles in the present tense. Use past tense only for past events or topics that no longer meaningfully exist.

Gender-neutral language

Use gender-neutral language. Do not use generic he or she. Use pronouns to refer to people only when appropriate pronouns are clear. If it's not clear what pronouns are appropriate, avoid pronouns completely with alternative sentence construction. Do not use singular 'they' if it's not a clearly stated preferred pronoun.

Instructional and presumptuous language

Do not use unencyclopedic or presumptuous language. Avoid phrases such as of course, naturally, obviously, clearly, and actually. Do not address the reader with phrases like remember that and note that. Purely instructional content, and policy/meta pages are allowed to address the reader, just like this page does.

Technical language

Technical language may be unavoidable when an article describes a nuanced, complicated topic. However, the lead section of an article should always provide a simple overview, and overly esoteric terms should either be replaced with simpler ones, or explained either inline or in a link to a separate article.

Plurals, vocabulary

• Contractions

Contested vocabulary

• Avoid vague terms such as dangerous, irresponsible, and risky.

Media files

• Images, Other media files, Avoid using images to convey text, Captions Bulleted and numbered lists