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)
CR
Vape (talk | contribs)
No edit summary
Line 1: Line 1:
=== Overview ===
=== 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.
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 ==
== Content Review Policy ==
Line 12: Line 13:


5. Content Reviewers 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.
==The Roadmap==
Developing a roadmap is a multi-step process. Concepts on the roadmap should be selected by the team privately, and the ideas should be established to a level of certainty before being presented for community feedback. Concepts can be specific or broad, as long as they have a “Solid final goal” that the team can guide contributors to. The creation of a roadmap can be broken down in specific steps.
1. '''Observation & Collection''' - Observe Discord channels, forums, and in-game interactions. Observing what players are discussing, what they enjoy, and what challenges they face. Monitor dedicated feedback channels, collect suggestions, and identify recurring themes or requests.
2. '''Conceptualization''' - after Observing & collecting data, rank Concepts by the following. This is done privately in the #roadmap-development forum.
*'''Content impact''' - Is the content aligned with our mission
*'''Technical Feasibility''' - What skills are needed for this?
*'''Breakdown''' - Break topics down into steps
*'''Community Interest''' - Is the community interested in this? Is this something that they would take kindly to?
*'''Priority''' - How necessary does the team believe this is? are there external pressures pushing for this?

Revision as of 11:18, 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.


The Roadmap

Developing a roadmap is a multi-step process. Concepts on the roadmap should be selected by the team privately, and the ideas should be established to a level of certainty before being presented for community feedback. Concepts can be specific or broad, as long as they have a “Solid final goal” that the team can guide contributors to. The creation of a roadmap can be broken down in specific steps.


1. Observation & Collection - Observe Discord channels, forums, and in-game interactions. Observing what players are discussing, what they enjoy, and what challenges they face. Monitor dedicated feedback channels, collect suggestions, and identify recurring themes or requests.


2. Conceptualization - after Observing & collecting data, rank Concepts by the following. This is done privately in the #roadmap-development forum.

  • Content impact - Is the content aligned with our mission
  • Technical Feasibility - What skills are needed for this?
  • Breakdown - Break topics down into steps
  • Community Interest - Is the community interested in this? Is this something that they would take kindly to?
  • Priority - How necessary does the team believe this is? are there external pressures pushing for this?