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.
RACKWiki is a harm-reduction educational resource with user-created content. Any registered user can create or edit most articles on the wiki.
== Getting Started ==
== Getting Started ==
=== Create an Account ===
=== Create an Account ===
An account is required to contribute to RACKWiki.
An account is required to contribute to RACKWiki.
# [https://rackwiki.org/wiki/Special:CreateAccount Create an account] with username, password, and email. While you may use a pseudonym for your username, an active email is required.
# [https://rackwiki.org/wiki/Special:CreateAccount Create an account] with username, password, and email. While you may use a pseudonym for your username, an active email is required.
# 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.
# Confirm your email address. '''The confirmation email will almost certainly 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.
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 ==
== Contributing ==
=== Guidelines ===
=== Guidelines ===
In order to make RACKWiki as direct and useful as possible, we encourage authors to:
In order to make RACKWiki as direct and useful as possible, we encourage authors to:
Line 21:
Line 18:
* Include reference citations
* Include reference citations
* Frame articles through lens of harm-reductive practices
* Frame articles through lens of harm-reductive practices
* Use consistent style and language within an article
* [[File:Ezgif-1-1e3ba6cd32.gif|alt=Creating an article from search/red link|thumb|Creating an article from search/red link]]Use consistent style and language within an article
* Use bulleted lists and tables when possible
* Use bulleted lists and tables when possible
=== New Articles ===
[[File:Template.gif|thumb|How to find templates in editor]]
In order to create an article, first, [https://rackwiki.org/wiki/Special:UserLogin 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 ====
<nowiki>*</nowiki>Info about seeding an article/editing existing heading
* Info about using Article Templates
==== User levels ====
* User: Level upon creation of profile. Can create and edit articles, but any changes require editor approval prior to content being publishing.
* Author: Authors can create and edit articles which will publish immediately without editor approval. Users are usually promoted to authors after one or more high quality content submission was reviewed and published.
* Editor: Editors moderate content submissions from Users, promote users to authors, and can edit most protected pages.
* Administrator: Administrators can edit all protected pages and manage some aspects of other user accounts.
== Assessing risk ==
=== Risk level definitions ===
In order to encourage consistency and allow for relative risk assessment, RACKWiki uses the following standardized definitions of risk level when summarizing the risk of a given topic.
==== Health ====
Health risk relates to the likelihood of injury or death if the topic is practiced.
* <span class="infobox-risk-Mild">Mild</span>: Severe injury AND death unlikely
* <span class="infobox-risk-Moderate">Moderate</span>: Temporary or permanent severe injury conceivable AND death unlikely
* <span class="infobox-risk-High">High</span>: Temporary or permanent injury plausible OR death conceivable
* <span class="infobox-risk-Critical">Critical</span>: Permanent injury or death risk essentially unmitigable
==== Legal ====
Legal risk relates to the likelihood of legal ramifications to the practitioners if law enforcement becomes involved or civil liability is pursued related to the practice of the topic.
* <span class="infobox-risk-Mild">Mild</span>: Unlikely to result in legal ramifications for practitioners
'''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 ===
RACKWiki uses US English spelling in its articles.
=== Formatting ===
==== Abbreviations, emphasis ====
To make content accessible to a wide audience, avoid using '''kinky abbreviations''' (such as ''CBT'', ''TT'', ''PP'') even if they are in common use. Abbreviations should be created as redirects pointing to their respective articles in case a user searches for them.
Emphasis with ''italics'' and '''bold''' can be used to highlight individual terms. '''<u>Using emphasis to present important information, like this, is discouraged.</u>''' Instead, rearrange the paragraph or article structure to start with the important point first.
==== 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 (e.g. kilogram, meter, Celsius). Customary conversions (e.g. pounds, inches, Fahrenheit), 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.
=== Neutrality and factuality ===
'''Be careful when describing the safety of a particular activity.''' Avoid vague terms such as ''dangerous'', ''irresponsible'', and ''risky.'' Present risks in a neutral way, using well sourced data when available. For example:
Creating an Article
* '''Bad:''' ''Catheters are risky because they often cause urinary tract infections.''
* '''Better''': ''According to research<ref>{{Cite journal |last=Nicolle |first=Lindsay E. |date=2014-07-25 |title=Catheter associated urinary tract infections |url=https://doi.org/10.1186/2047-2994-3-23 |journal=Antimicrobial Resistance and Infection Control |language=en |volume=3 |issue=1 |pages=23 |doi=10.1186/2047-2994-3-23 |issn=2047-2994 |pmc=PMC4114799 |pmid=25075308}}</ref>, catheter use in a controlled medical setting carries a symptomatic infection risk of about one percent, although a higher percentage may experience an asymptomatic infection.''
'''Hypothesize and synthesize carefully'''. Many areas of BDSM and kink lack peer-reviewed research, and that's why RACKWiki does not have a policy of No Original Research like [[wikipedia:Wikipedia:No_original_research|Wikipedia does]]. Be careful when creating factual content not directly attributable to a reference.
Using Templates
* '''Bad:''' Shock collars are safe to use on humans. ''[there is no research directly targeting this, so this is an opinion]''
* '''Better:''' In medical literature, there are no documented cases of shock collars directly causing fatalities or permanent injury on humans ''[this could be easily disproven by finding a single reference, so it's a fair statement to make]''. However, injuries may be caused by loss of muscular control, such as falling down when the collar is activated ''[probably no scientific reference, but a news story probably can be referenced if someone disputes this]''.
=== Explicit, inflammatory, and divisive content ===
Since the majority of content on RACKWiki discusses sexual conduct, oftentimes esoteric, '''content warnings''' are not needed and should not be used.
Many concepts and terms in kink (such as ''master'', ''slave'', ''race play'', ''adult baby'', ''blackmail, female submission'', etc.) may evoke culturally specific connotations that individuals may find offensive. To maintain accuracy and clarity, you should not attempt to redefine, censor or discourage certain kind of language if it's otherwise descriptive and in common use.
== Organizing ==
=== Media files ===
== Style Guide ==
* Images, Other media files, Avoid using images to convey text, Captions Bulleted and numbered lists
== Author Credit ==
=== Links ===
Latest revision as of 03:22, 7 February 2024
RACKWiki is a harm-reduction educational resource with user-created content. Any registered user can create or edit most articles on the wiki.
Getting Started
Create an Account
An account is required to contribute to RACKWiki.
Create an account with username, password, and email. While you may use a pseudonym for your username, an active email is required.
Confirm your email address. The confirmation email will almost certainly 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
Creating an article from search/red linkUse consistent style and language within an article
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 and edit articles, but any changes require editor approval prior to content being publishing.
Author: Authors can create and edit articles which will publish immediately without editor approval. Users are usually promoted to authors after one or more high quality content submission was reviewed and published.
Editor: Editors moderate content submissions from Users, promote users to authors, and can edit most protected pages.
Administrator: Administrators can edit all protected pages and manage some aspects of other user accounts.
Assessing risk
Risk level definitions
In order to encourage consistency and allow for relative risk assessment, RACKWiki uses the following standardized definitions of risk level when summarizing the risk of a given topic.
Health
Health risk relates to the likelihood of injury or death if the topic is practiced.
Mild: Severe injury AND death unlikely
Moderate: Temporary or permanent severe injury conceivable AND death unlikely
High: Temporary or permanent injury plausible OR death conceivable
Critical: Permanent injury or death risk essentially unmitigable
Legal
Legal risk relates to the likelihood of legal ramifications to the practitioners if law enforcement becomes involved or civil liability is pursued related to the practice of the topic.
Mild: Unlikely to result in legal ramifications for practitioners
Moderate: Legal ramifications for practitioners conceivable, legal contingency planning recommended
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
RACKWiki uses US English spelling in its articles.
Formatting
Abbreviations, emphasis
To make content accessible to a wide audience, avoid using kinky abbreviations (such as CBT, TT, PP) even if they are in common use. Abbreviations should be created as redirects pointing to their respective articles in case a user searches for them.
Emphasis with italics and bold can be used to highlight individual terms. Using emphasis to present important information, like this, is discouraged. Instead, rearrange the paragraph or article structure to start with the important point first.
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 (e.g. kilogram, meter, Celsius). Customary conversions (e.g. pounds, inches, Fahrenheit), 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.
Neutrality and factuality
Be careful when describing the safety of a particular activity. Avoid vague terms such as dangerous, irresponsible, and risky. Present risks in a neutral way, using well sourced data when available. For example:
Bad:Catheters are risky because they often cause urinary tract infections.
Better: According to research[1], catheter use in a controlled medical setting carries a symptomatic infection risk of about one percent, although a higher percentage may experience an asymptomatic infection.
Hypothesize and synthesize carefully. Many areas of BDSM and kink lack peer-reviewed research, and that's why RACKWiki does not have a policy of No Original Research like Wikipedia does. Be careful when creating factual content not directly attributable to a reference.
Bad: Shock collars are safe to use on humans. [there is no research directly targeting this, so this is an opinion]
Better: In medical literature, there are no documented cases of shock collars directly causing fatalities or permanent injury on humans [this could be easily disproven by finding a single reference, so it's a fair statement to make]. However, injuries may be caused by loss of muscular control, such as falling down when the collar is activated [probably no scientific reference, but a news story probably can be referenced if someone disputes this].
Explicit, inflammatory, and divisive content
Since the majority of content on RACKWiki discusses sexual conduct, oftentimes esoteric, content warnings are not needed and should not be used.
Many concepts and terms in kink (such as master, slave, race play, adult baby, blackmail, female submission, etc.) may evoke culturally specific connotations that individuals may find offensive. To maintain accuracy and clarity, you should not attempt to redefine, censor or discourage certain kind of language if it's otherwise descriptive and in common use.
Media files
Images, Other media files, Avoid using images to convey text, Captions Bulleted and numbered lists
