Image folders

Images are grouped by the page that uses them, so this folder stays browsable on GitHub (a flat folder over 1,000 files gets truncated and you can't see the rest).

assets/
  inbox/    >>> UPLOAD EVERYTHING HERE (0 waiting)
  pages/    one folder per web page (80 folders)
  shared/   images used by 2-7 pages (203)
  common/   images used by 8+ pages (95)
  site/     header/footer images, on every page (8)
  unused/   images no page links to (2)
  dead/     the old pile, untouched, for sorting later

Adding a new image

You only ever need assets/inbox/. You don't have to know how many pages will end up using a picture — that gets sorted out afterwards.

1. Open assets/inbox/ → Add file → Upload files. Straight off your phone is fine; the photo can be any size and any format.
2. Use it on whatever pages you like: <IMG SRC="/assets/inbox/IMG_20260725_120000.jpg">
3. Later, the maintainer runs npm run organize:apply, which:
   • converts your photo to WebP and shrinks it to 650px (much faster to load)
   • builds the small phone-sized version and wires up srcset
   • tidies up common HTML slips on the pages you edited
   • looks at which pages actually use the image and files it away: one page → pages/<thatpage>/, a few pages → shared/, lots → common/
   • rewrites every <IMG SRC> for you, so your pages keep working

Anything you upload but haven't used yet just stays in inbox/ until you do. Old links keep working too — moved images get a redirect from their previous URL.

Filenames are never changed by any script, so whatever your phone named the file is fine.

Page folders

Generated by node scripts/reorganize-assets.js --readme-only — re-run it after adding or removing images to refresh these counts.