ARC Raiders Wiki:Editing guidelines

ARC Raiders Wiki editing guidelines are a set of principles for contributors to follow. Rather than acting as hard rules that must always be followed, they should be applied when reasonable by context.

Conduct

• Be civil and assume good faith. Strive to reach a resolution to disputes through dialogue and discussion. Do not harass, insult, or make personal attacks toward other editors.
• Do not vandalize, spam, or otherwise edit disruptively.
• Do not get involved in edit warring. Please use talk pages to discuss and resolve disagreements.
• A single editor's personal preference or opinion about what goes on the wiki should not override all others.
• Do not plagiarize content from other websites or forums.

In case of disagreements, editing conflicts, or disputes, start a discussion on the user's or related article's Talk page or the ARC Raiders Discord wiki channel.

Consensus

Consensus is the end result of productive discussion. It is not the result of a vote or the most popular opinion, but rather the end result of productive discussion and debate regarding the best practices for the wiki.

A consensus is never permanent, complete or unquestionable, and may always change following new discussion.

Consensus should not be confused with convention; just because something has always been done a certain way doesn’t mean it’s what people currently agree is best. A consensus could either support an existing convention or make changes to those conventions.

In the case of disputes and conflicts, it is always the goal to reach a consensus to improve the wiki.

Improving articles

Be bold and take initiative to add new content to articles. Articles are never considered complete, add additional information or perspectives to articles as needed.

Do not be afraid to add incomplete information to the wiki, but do not create empty or near-empty articles.

Do not outright remove correct information that could be relevant to an article, rephrase and rework it.

Use an encyclopedic writing style with a formal tone instead of essay-like, instructive, or opinionated writing.

Cosmetic edits

Edits that are purely cosmetic in nature and do not change the visible page for the reader should be combined with substantive content changes. While we appreciate "editor-only" edits that makes the source code easier to read, these should not be saved as standalone edits.

If a cosmetic change improves the page layout for the reader such as removing an awkward gap or fixing a broken line break, it is considered a valid improvement.

Preview button

We encourage frequent editing, but saving many small changes in a short window can flood the "Recent Changes" and article history logs, making it harder for the community to track updates.

The preview button (next to the save button) lets you check your formatting and typos before committing. If a moderator notices a pattern of frequent small saves within a short period of time, they’ll reach out to help you consolidate your workflow.

Summary box

Strive to be clear about your intentions. Describe the nature of your edits (e.g. "fixed typo", "added stats for weapon", "updated lore") by filling out the Summary field on the submission page. This helps other editors understand your changes without having to go through each revision to check what changed.

Keep summaries objective and descriptive. Use the summary box to simply summarize your edit; do not use it to vent, insult others, or justify why another editor is incorrect. You can use the article's Talk page or ARC Raiders Discord wiki chat to explain an edit in more depth if needed.

Formatting

Refining articles for clarity and readability is encouraged. However, please discuss major structural or site-wide formatting changes before making them.

Templates and modules that are used in multiple articles are considered major structural changes. This includes any logic, parameter, or styling changes. Please discuss any planned edits to them before editing, as these changes will affect multiple pages.