Dead as Disco Source Library Naming Rules: File Names, Folders, and Review Workflow
Dead as Disco 素材库命名规则：文件名、文件夹和审核流程
A safe editorial workflow for naming Dead as Disco screenshots, videos, YouTube clips, source links, and review folders before any gameplay claim becomes final guide copy.
Evidence status
Partially verifiedThe topic and structure are reliable, but exact values or fight details still need gameplay capture.
Next: attach screenshots, timestamps, result screens, or official notes before final claims.
Use this for
Beginner Guides
Trust level
Partially verified
Reader mode
Read + verify
Editor Brief
This page is written as a working guide, not a finished wiki dump. Use the confirmed notes first, then treat source-pending rows as a checklist for what still needs gameplay proof.
Current source note: This page defines an editorial filing workflow and does not publish any confirmed gameplay facts.
Media status
No Public Gameplay Embed Yet
This article keeps the media area honest: no fake screenshots, no decorative gameplay claims, and no third-party stills republished as site assets. When a source clip is approved, this block becomes the video player and timestamp map.
Needed
timestamped clip
Needed
claim being tested
Needed
version/platform
One File Name Should Explain The Claim
A source library is a filing system, not a fact database. File names should explain the claim being reviewed, the source type, the platform, the capture date, and the spoiler level. They should not present Boss moves, BPM values, rewards, unlock conditions, or fixes as confirmed unless the matching evidence has already passed review.
- Use a predictable pattern: topic-source-platform-version-date-spoiler-review-status.
- Use neutral claim words such as boss-move-review, bpm-check, reward-proof, or save-path-source.
- Avoid final-sounding names such as confirmed-best-build or exact-final-bpm until verification is complete.
Folder Structure For Review
Keep incoming material separate from publishable guide copy. A simple library can split sources into inbox, needs-review, verified-public-info, needs-gameplay-check, source-pending, and retired folders. This keeps screenshots, long YouTube videos, clipped timestamps, official links, and notes traceable without turning them into unsupported SEO claims.
- Inbox: raw submissions that have not been reviewed.
- Needs-review: evidence with enough metadata to check but not enough to publish.
- Verified-public-info: official public source evidence, not gameplay capture.
- Needs-gameplay-check and source-pending: safe holding areas for incomplete claims.
Do Not Promote Raw Assets Into Facts
A screenshot or video can support a future page, but it should not automatically become final guide text. Editors should attach the source URL, timestamp range, claim being tested, platform, version, capture date, and reviewer note. If any field is missing, the guide can mention the topic as launch placeholder, needs gameplay verification, or source pending only.
- YouTube sources need exact timestamps and the specific visual/audio evidence to inspect.
- Local or R2 assets need filenames that preserve source, platform, date, and spoiler status.
- Retired evidence should stay linked to the version it came from so old claims can be audited later.
Evidence desk
Screenshot / Video Evidence Area
Source-library assets need source URL, timestamp, platform, version, capture date, spoiler status, and review status before they can support guide claims.
This page defines an editorial filing workflow and does not publish any confirmed gameplay facts.
FAQ
Does this page publish a real Dead as Disco source library?
No. It defines naming and review rules only. It does not publish any confirmed gameplay facts, private files, screenshots, or video assets.
Can file names include spoilers?
Use spoiler labels instead of explicit spoiler text whenever possible. If a spoiler must be named for internal review, keep it out of public pages until the article has the correct spoiler warning.