chrislgarry/Apollo-11

Choose upstream unless you explicitly want an old frozen snapshot. This fork adds no visible capabilities and is far behind on maintenance and content updates.

Prefer upstream unless you need this exact old snapshot. This fork adds no visible capabilities, is 70 commits behind, and misses recent preservation and documentation work, so it is a poor choice for adopters who want the most accurate or current version of the Apollo 11 archive.

Prefer upstream unless you specifically want the fork's older, simplified browsing experience or its syntax-highlighting/compilation notes. For archival accuracy, completeness, and recent fixes, upstream is the better default.

Prefer upstream unless you specifically want a frozen, minimally changed copy. This fork adds nothing visible beyond the upstream repo and is behind on recent maintenance, so it is only attractive as an archival snapshot.

Prefer upstream unless you specifically want this fork’s frozen 2018-era state; the fork is substantially behind and stale, so it trades active correction and documentation progress for historical stability.

Prefer upstream unless you specifically want a frozen, unchanged snapshot from this fork point. This fork adds no visible functionality and is materially behind on documentation and source-text cleanup.

Prefer this fork only if the scan-viewing addition is the specific workflow you want and you are comfortable giving up upstream's later proofreading and translation work. For most adopters who care about transcription accuracy, upstream is the better default.

Prefer upstream unless you explicitly want an old, unchanged fork snapshot. This fork offers no added capabilities and is materially behind on preservation-focused updates, so adopters should expect missing transcription, documentation, and maintenance work.

Prefer upstream unless you specifically need this older frozen snapshot. The fork adds no visible capabilities and is far behind on maintenance, proofing, and translation work.