Source and guide quality

Editorial and Source Policy

This page explains how the guide database collects public videos, official notes, screenshots, timestamps, and player-facing article structure.

What readers can use now

We publish player-facing guides built from official public facts, public videos, practical route structure, settings checklists, category indexes, and update notes.

  • Official store pages, official site copy, trailers, and public update posts can support general game facts.
  • Editorial practice advice is allowed when it does not invent exact frame data, rewards, unlocks, or boss mechanics.
  • Every guide should show update date, version context, difficulty, stage, spoiler level, video notes, and whether exact values are available.

How exact details are added

Public videos and articles are useful immediately, but exact values are added only when the clip, screen, or official note clearly supports the detail.

  • Boss moves, phase names, punish windows, score thresholds, BPM values, rewards, and unlock paths are written when there is a clear timestamp, result screen, or official note.
  • When the route is useful but exact values are still being collected, the page uses reader-friendly labels such as Guide in progress or Video-backed draft.
  • Early Access changes can make old guide notes stale, so version status is part of the content model.

Media evidence rules

Video and screenshots are treated as evidence, not decoration. A good media block should help readers verify the written steps.

  • YouTube embeds should include useful timestamps and explain which written step each timestamp supports.
  • Local or R2-hosted media should be tied to guide evidence notes, especially for menus, result screens, and unlocks.
  • Decorative artwork is allowed for identity and layout, but it must not be used to confirm exact game mechanics.

Corrections and maintenance

The database is built for ongoing correction. When a claim changes, the page should be updated rather than silently leaving stale advice in place.

  • Outdated notes should be marked, revised, or moved into a version history section.
  • Reader-facing pages should keep a clear separation between confirmed facts, practical advice, and planned capture work.
  • Internal capture checklists live in documentation until evidence is ready for public guide pages.

Reader promise

Disco Outlaw Guide should save players time: summarize the best public videos and articles, turn them into readable routes, and keep updating details as better material appears.