static-project-gallery-upload

Static Project Gallery Upload

Turn a loose folder of project images into a production-ready static-site gallery and upload package.

Core rule

Remove only exact duplicates unless the user explicitly asks for visual deduplication.

• Exact duplicate = same file bytes / same cryptographic hash, even if filenames differ.
• Similar image, same building, different angle, crop, lighting, render alternative, or facade view = keep it.
• If multiple views belong to the same building or design alternative, place them near each other in the gallery order.
• Do not delete the user's original source images unless explicitly instructed; create a clean derived output instead.

Workflow

1. Discover the project shape

Inspect the root before editing.

Check:

• Is the site static HTML/CSS/JS, Astro, React, Next, or another stack?
• Where are current gallery/project images referenced?
• Where are public assets served from?
• Does the project already have an upload/output folder convention such as UP FILE?
• Are image tools already available, e.g. sharp in package.json?

Completion criterion: you know which files must be edited, which folders are source-only, and which files must be copied to the host package.

2. Inventory and exact-dedupe the source images

List every image in the user-provided folder and compute SHA256 hashes.

Use exact-hash grouping as the authoritative duplicate test:

Get-ChildItem "<source-image-folder>" -File |
  Get-FileHash -Algorithm SHA256 |
  Group-Object Hash |
  Where-Object { $_.Count -gt 1 }

For each exact duplicate group, keep one representative. Prefer:

1. The filename without copy suffixes like (1), (2).
2. The filename already referenced by the site.
3. Otherwise the earliest/cleanest name.

Completion criterion: you have a source-to-output mapping where every exact hash appears once, and no visually distinct angle was removed.

3. Preserve visual families in gallery order

Sort the kept images intentionally.