Primary sources first.
Prefer original papers, manuals, code, interviews and institutional archives over repeated mythology.
READMEAbout / Editorial protocol
A museum that
behaves like Git.
CodeHistory.org documents programming as a living human practice. That means sources, revisions, contested claims and room for new branches.
01 / Principles
Version the story.
Mark contested claims.
“First,” “invented,” and “pioneer” are often more complex than a plaque suggests. Say when priority is disputed.
Credit teams and infrastructure.
Software history is full of invisible labor. Operators, maintainers, testers, documentarians and standards communities belong in the frame.
Keep the present provisional.
The closer we are to an event, the less historical distance we have. Contemporary entries should show their evidence and invite revision.
02 / Built to publish
WordPress is the archive engine.
Use Posts for ongoing essays and field notes, Pioneers for profiles, and Timeline for milestones. The front-end keeps its museum-grade interaction while editors use familiar publishing tools.
WORDPRESSPHPHTMLCSSJAVASCRIPTTHREE.JSGSAPREMOTION SOURCE