lititzbmx-docs

Pre-Publication QA Checklist

Use this checklist before any Lititz BMX GitHub package is called complete or ready to upload.

A. Repository safety

• Destination repository and branch match the established workflow.
• Package adds only the intended top-level folder or files.
• Existing root files and unrelated folders are untouched.
• Root README update is separated from the project upload when that is the established protocol.
• No private supplement is included in the public package.

B. Archival integrity

• Required dossier files exist.
• Original recording is identified as the authority.
• Raw transcripts remain unchanged.
• Working and verified transcript layers are labeled accurately.
• Missing documentation is recorded rather than invented.
• Testimony is not silently converted into institutional fact.
• Rights, privacy, redaction, and transformation notes are complete.
• Fixity manifest and package integrity checks pass.

C. Visual presentation — mandatory

• Every public landing README opens with an appropriate visual.
• Original supplied title cards are actually displayed, not merely stored in assets/.
• Each completed dossier has visible canonical-recording access.
• Collection and category pages provide visual navigation.
• Sibling projects have reasonable visual parity.
• Every displayed image has useful alt text.
• Later-created repository covers are clearly labeled as later archival assets.
• Approved logo variants are used; no logo is reconstructed or restyled.
• No unrequested glow, shadow, recoloring, or decorative treatment has been added to supplied graphics.
• Technical files remain restrained and readable.

D. Link and render review

• All relative image paths resolve from their README locations.
• All relative document links resolve.
• No README depends on a local computer path.
• Images are legible at GitHub page width.
• Tables remain readable on a typical desktop display.
• The package has been inspected in a local Markdown preview or equivalent render check.

E. Final release statement

The package may be called ready only after sections A–D pass. Any known limitation must be stated in the validation report before upload.