Local Assets

This repo expects a local-assets/ folder at the repo root containing non-code local data (originals, exports, source design files, etc.). This folder is intentionally gitignored — it is NOT version controlled and is expected to be a symlink to wherever this project's local data is actually synced (cloud storage, network share, external drive — varies by project, check with the repo owner if unclear).

On a new machine:

Locate this project's synced local-assets folder (ask the repo owner or check for prior setup notes if not obvious).
Confirm it's fully synced/downloaded locally before proceeding.
Recreate the symlink, using $HOME/~ rather than a hardcoded username so this works across machines:
```
ln -s "<path to synced local-assets folder>" "$HOME/path/to/this/repo/local-assets"
```

What's inside

local-assets/img-source/ — full-resolution source photos (galleries and blog), one subfolder per gallery/post. npm run optimize:images reads from here and writes optimized, web-ready versions into assets/images/galleries/ and assets/images/blog/ (which ARE tracked in git and deployed).

Build-time dependency

The Eleventy build (npm run build) enumerates filenames under local-assets/img-source/galerie/<gallery>/ (see _data/galleryImages.js) to know which images to render in gallery pages — it does not read the image bytes themselves (only the optimized assets/images/... files are actually served), but it does need the file listing to match what optimize:images last produced. This means:

Local builds require local-assets/img-source/ to be present (synced) and up to date with assets/images/galleries/ and assets/images/blog/.
The Netlify build does not have access to local-assets/ (it's gitignored/symlinked, not part of the git checkout), so it relies entirely on the already-committed, pre-optimized files in assets/. Run npm run optimize:images and commit the results in assets/ before pushing whenever you add/remove/reorder source photos.