Article Text

Sample profile: The archive, people, artifacts, and reporting details below are fictional and provided to demonstrate the publishing system.

The safest first question is not “Who is this?” but “What do we know?” The fictional archivist places an undated photograph beside its envelope, notes the handwriting on the back, and resists a confident guess about the house in the background.

That patience separates a useful community archive from a collection of attractive images. Family memory provides leads, but dates, addresses, photographers, and ownership need evidence. Uncertainty belongs in the caption when the evidence runs out.

Keeping the clues together

Photographs often arrive with the materials that explain them: a receipt from a local studio, a letter mentioning a move, or a map with one parcel marked in pencil. Separating those items can erase the relationship that gives each one meaning.

The sample workflow assigns a simple identifier, records the donor and any restrictions, and scans the front and back. Digital filenames preserve that identifier instead of replacing it with a vague description. Original files remain untouched while smaller access copies are prepared for the web.

Publishing with permission

An archive article must answer questions beyond image quality. Does the contributor own the photograph? Are the people shown comfortable with publication? Does a caption expose private information? A newspaper should document permission and distinguish a donated original from a temporary loan.

The repository publishing system follows the same principle on a technical level. Source images stay beside the article that explains them. The build creates smaller formats for readers, but the Markdown file retains the caption, alternative text, and credit as part of the historical record.

In both cases, organization is a form of care. The goal is not simply to keep a box or fill a page. It is to make the material understandable to the next person who opens it.