A practical guide for choosing clear public material.

Rights first

When the reuse terms are unclear, skip the item. The archive grows best through well-documented material, not through uncertainty.

Local copy, visible source

Keep the local file name near the source URL so the reader can connect the image and the credit without searching through the page.

No location clues

Map and city images should be discussed as documents. Let the labels, borders, and scale do the reading work.

No account references

Avoid links to handles, profiles, inboxes, or any other detail that shifts the note away from the object itself.

Short is safer

Compact notes are easier to trust than long captions that try to do everything at once. Keep the tone direct and specific.

Use repeated structure

Titles, credits, dates, and one short note create a stable reading pattern that still leaves room for variation between objects.

Use source dates well

Dates should describe the public record or the archive update. They should help the reader place the object, not tell a life story.

Keep titles exact

Use the title from the source page and avoid renaming the object just to make the note sound smoother.

Favor clear credits

A credit line should be readable at a glance. If the credit is too vague, the object should stay in the ledger until it is clearer.

Choose varied page roles

Use cards, tables, and essays for different jobs. Variation helps the archive feel edited rather than copied from one repeated pattern.

Check links before publish

A quick link check catches broken source pages and makes the archive easier to trust over time.

Moon Surface

Historical lunar material works well when the note stays close to surface texture, horizon line, and credit trail.

Library Room

A room image can support the reading shelf when the note points to layout, shelving, and the feel of the space.

City Map

A map record can stay focused on labels, blocks, scale bars, and edge details without needing extra framing.

Books and Maps

This set bridges the shelf and the map room because it naturally links reading, route logic, and catalog pages.

WPA Poster

Poster material gives the archive a public-message lane and keeps the shelf from leaning only on maps and skies.

Lighthouse

The silhouette reads clearly and gives the site a navigation image that still feels like a document.

Dwarf Galaxy

A small galaxy field is useful when the page needs scale and density without a dramatic caption.

Saturn Edge

Ring geometry and dark space give this image a useful horizontal frame for the archive.

Jupiter Crescent

Weather bands and a crisp edge line make this a good compact sky note with a clear source trail.

Orion Bow Shock

A nebula frame gives the archive a textured sky record that still reads well as a document.

Turning an image into a diary line

Start with the object, not with a personal story. The source page and the image itself already carry enough meaning.

A clean note is easier to trust than a note that tries to sound intimate.

Repeating one card everywhere

Different pages should do different jobs. If the same text keeps coming back, the site starts to feel flat.

Use the long note for argument, the shelf for grouping, and the guide for rules.

Overexplaining every object

Not every image needs a long caption. Some records work best when the title, credit, and one detail are enough.

Save the longer writing for the images that truly need it.

Using weak source pages

If the source page is hard to read or hard to trust, the item should stay out. Strong provenance matters more than volume.

The archive is better with fewer, clearer records.

Making the site too symmetrical

Perfect repetition can make a page feel mechanical. Vary the format when the page role changes.

Tables, cards, and essays each carry a different kind of weight.

Adding contact surfaces for no reason

Mail forms, signup boxes, and inbox language can distract from the archive and suggest that the page wants more than reading.

Keep the site focused on records and source notes.