lititzbmx-docs

Lititz BMX GitHub Visual Presentation Standard

Version: 1.0.0
Effective date: 2026-07-20
Applies to: All public-facing Lititz BMX GitHub project, collection, campaign, standard, and dossier landing pages.

1. Required principle

Preservation underneath. Clear public presentation on top.

A technically complete archive is not considered publication-ready when its landing pages are visually empty, inconsistent with neighboring Lititz BMX projects, or difficult to enter. Visual presentation is a required access layer—not optional decoration.

2. Mandatory landing-page elements

Every public project or category README must include:

1. a relevant opening visual or documented reason one cannot be used;
2. a concise title and plain-language purpose;
3. visible navigation to the principal records or sections;
4. descriptive link text rather than unexplained filenames;
5. visual parity among sibling records and categories;
6. accessible alt text for every displayed image;
7. provenance labeling for later-created repository covers or derivative visuals.

Every completed media dossier README must include:

1. the supplied title card or thumbnail at the top;
2. a direct link to the canonical recording;
3. an “At a glance” summary;
4. a museum-style record summary;
5. a statement explaining why the recording matters;
6. organized links into the dossier;
7. current preservation and transcript status.

3. Original and later-created visuals

• Original publication graphics remain source materials and should be displayed when rights and privacy review permit.
• A later repository access cover may be created when no original graphic survives.
• A later cover must never be presented as an original title card.
• The README and source inventory must identify the later cover’s role and creation date.
• No unrequested glow, shadow effect, color treatment, logo alteration, or decorative embellishment may be added to an original supplied visual.

4. Lititz BMX logo rule

Use only approved Lititz BMX logo assets and established variants. Do not redraw, approximate, restyle, or extract the logo from another image for a new standalone use. A new repository navigation graphic may omit the logo rather than use an unapproved reconstruction.

5. Restraint

Visual enhancement belongs primarily in:

• collection and category README files;
• campaign and project landing pages;
• individual dossier README files;
• public indexes where thumbnails improve navigation.

Technical records should remain restrained, including metadata, schemas, transcripts, fixity manifests, rights records, privacy records, source inventories, and verification notes.

6. Publication gate

A project may not be described as “GitHub-ready,” “complete,” or “ready to upload” until the Pre-Publication QA Checklist confirms both archival integrity and public visual presentation.

7. Change control

Visual enhancement must be additive and reviewable. It must not silently rewrite source material, alter original graphics, or restructure unrelated repository content. The change report must distinguish visual-access changes from archival-content changes.