VerseDB Content Standards

VerseDB relies on contributors to maintain accurate, well-sourced comic data. This guide covers standards for accuracy, handling conflicts between sources, mature content, and quality expectations.

Note

For detailed formatting rules, field-specific guidelines, and character limits, see our Content Edit Guidelines and Best Practices article.

Accuracy Standards#

Every submission must be based on verifiable facts, not guesses or assumptions.

Rule

If you can't verify something, leave it blank. Incomplete data is better than incorrect data.

  • Verify information against official publisher sources
  • Use printed comic credits as your primary reference
  • Cross-reference multiple sources for important details
  • Document your sources in submission notes
  • Submit speculation or fan theories as facts
  • Guess dates, credits, or publication details
  • Rely on a single unverified source
  • Add information just to fill in blanks

Verification Standards#

Different edits require different levels of verification:

Edit Type Sources Required Examples
Simple 1 source Typo fixes, formatting
Standard 2 sources Descriptions, dates, credits
Complex 3+ sources Relationship changes, major additions

Handling Conflicting Sources#

Sometimes sources disagree. When that happens, follow this hierarchy:

Example

If a printed comic credits Writer A but a website lists Writer B, trust the printed comic.

When Sources Conflict#

Check for context first:

  • Is one source newer and correcting an error?
  • Are they referring to different editions (original vs reprint)?
  • Could this be a retcon or editorial change?

If no clear resolution exists, document both versions:

"Note: Sources conflict on [detail]. [Source 1] states [X], while [Source 2] indicates [Y]."

Tip

Publisher corrections, reprints with updated credits, and retcons are common in comics. When documenting these, note the original version and when/where it was changed.

Writing Quality Standards#

Descriptions should be clear, neutral, and concise. See the Content Edit Guidelines and Best Practices article for character limits and content-specific guidelines.

Tone and Language#

  • Write in third person ("Batman is..." not "You play as...")
  • Use neutral, factual language
  • State verifiable claims ("Won the Eisner Award")
  • Keep present tense for current info, past tense for history
  • Include personal opinions ("the best run ever")
  • Use promotional language ("Don't miss this epic saga!")
  • Sensationalize content
  • Write in first or second person

Spoiler Policy#

Series and character descriptions:

  • General premise and setup are fine
  • Avoid major plot reveals
  • Historical events are acceptable for completed series

Issue descriptions:

  • Spoilers are allowed but should be marked
  • Use: "[SPOILERS] This issue reveals..."
  • Focus on setup rather than outcomes when possible

Mature Content Policy#

VerseDB uses content ratings to help users make informed choices.

Age Ratings#

Use the official rating provided by the publisher. Common systems include:

Marvel: All Ages, T (12+), T+ (15+), Parental Advisory (17+), Explicit (18+)

DC: Everyone, Teen (12+), Teen Plus (15+), Mature (17+)

Warning

Never create your own ratings. Use the publisher's official classification or leave the field blank if unknown.

NSFW Flag#

Set the is_nsfw flag for content containing:

  • Graphic violence or gore
  • Sexual content or nudity
  • Strong language throughout
  • Disturbing or intense themes

Note

The NSFW flag affects how content displays across the site. When in doubt, mark it.

Content Warnings#

For mature-rated content, mention themes factually in descriptions:

"Content Warning: Contains graphic violence and strong language."

Keep it brief and professional. Don't sensationalize or provide excessive detail about mature content.

Prohibited Content#

Rule

Never submit or link to: unauthorized scans, pirated comics, leaked previews, fan-made explicit content, or illegal download sites.

Allowed materials include official publisher previews, solicitation images, and verified promotional content.

Enforcement#

How Edits Are Reviewed#

Moderators evaluate submissions against these standards:

  • Is the information verifiable?
  • Are sources cited appropriately?
  • Does the content meet quality standards?
  • Are ratings and flags set correctly?

Consequences for Violations#

Repeated issues may result in:

  • Edit rejections with feedback
  • Slower review times
  • Contribution restrictions

Tip

Focus on quality over quantity. A strong approval rate shows moderators you're a reliable contributor.