# Read-only shared-drive staging

When HTML sources live on a read-only shared drive, do not mutate that folder in place just to make the pages browsable.

## Recommended pattern
1. Inventory the HTML entry files and any sibling assets.
2. Create a writable local staging directory such as `~/site-deploy/<project>/`.
3. Copy only the files needed for the deployable site into staging.
4. Add an `index.html` landing page in staging when there are multiple HTML entry points.
5. Serve and publish from the staging directory rather than the shared-drive source.

## Why this matters
- Avoids permission failures on shared/NAS mounts.
- Keeps upstream project material pristine.
- Makes cleanup easier because the public copy is isolated.

## Verification checklist
- Source directory is read-only or treated as read-only
- Staging directory is writable
- All primary HTML pages open correctly from the staging copy
- The user receives URLs, not host-local filesystem paths
