Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Direction Guidelines: Difference between revisions

From Delta-V Wiki
Vape (talk | contribs)
Content Rework due to new policies
Tags: Replaced Visual edit
Vape (talk | contribs)
CR
Line 1: Line 1:
=== Overview ===
=== Overview ===
Direction has two branches; Content management and Events. This page goes over both, as well as the policy on roadmaps, events, and content management.
This page goes over Content Review, and How to perform these. This goes into detail about CR policy, Design Documents, Content removal, and more.


===== Content Management Policy =====
== Content Review Policy ==
1. The '''Content Management Team''' is expected to submit a roadmap to the '''Game Director''' and '''Project Management''' for review when possible.
1. The '''Content Review Team''' is expected to submit a roadmap to the '''Content Director''' and '''Project Management''' for review when possible.


2. Content Managers are expected to fulfill their duties without bias. Submission of PR’s that can be considered without merit or otherwise heavily biased, should be considered for denial.
2. Content Reviewers are expected to fulfill their duties without bias. Submission of PR’s that can be considered without merit or otherwise heavily biased, should be considered for denial.


3. Content Managers are required to have a basic understanding of how PR Submission works, and how to use Github.
3. Content Reviewers are required to have a basic understanding of how PR Submission works, and how to use Github.


4. In order to vote on a PR, Content Managers must present adequate reasoning and explanations behind their votes.
4. In order to vote on a PR, Content Reviewers must present adequate reasoning and explanations behind their votes. <small>We urge all reviewers to make use of the poll, as well as explain their reasoning.</small>


5. Content Managers should be reasonably up to date and knowledgeable about the game and its intricacies.
5. Content Reviewers should be reasonably up to date and knowledgeable about the game and its intricacies.

Revision as of 11:15, 7 February 2026

Overview

This page goes over Content Review, and How to perform these. This goes into detail about CR policy, Design Documents, Content removal, and more.

Content Review Policy

1. The Content Review Team is expected to submit a roadmap to the Content Director and Project Management for review when possible.

2. Content Reviewers are expected to fulfill their duties without bias. Submission of PR’s that can be considered without merit or otherwise heavily biased, should be considered for denial.

3. Content Reviewers are required to have a basic understanding of how PR Submission works, and how to use Github.

4. In order to vote on a PR, Content Reviewers must present adequate reasoning and explanations behind their votes. We urge all reviewers to make use of the poll, as well as explain their reasoning.

5. Content Reviewers should be reasonably up to date and knowledgeable about the game and its intricacies.