GitHub Pages Deployment Removed

The production workflow no longer publishes the static gallery build to GitHub Pages. .github/workflows/deploy.yml now stops after building apps/web/dist/, syncing photos to Cloudflare R2, and mirroring the static output into Jackyhq/Photography-Web.

Removed Automation

The deployment job no longer declares the github-pages environment or the Pages-specific permissions:

• pages: write
• id-token: write

The job also no longer runs these GitHub Pages actions:

• actions/configure-pages
• actions/upload-pages-artifact
• actions/deploy-pages

Local Build Equivalent

To reproduce the static gallery build locally:

pnpm install
git clone git@github.com:Jackyhq/Photography-Photos.git photos
pnpm run photos:standardize
pnpm run build:manifest
pnpm build

The deployable static files will be in:

apps/web/dist/

Current Workflow Output

During CI, the workflow builds:

apps/web/dist/

The same directory is mirrored into the external deployment repository Jackyhq/Photography-Web. The root web/ directory is ignored in this source repository and should not be treated as the canonical build output.

Photo source files stay in the private Jackyhq/Photography-Photos repository. The generated manifest lives at apps/web/src/data/photos-manifest.json during local builds and CI; packages/data/src/photos-manifest.json is a tracked symlink to that generated file.

If Re-Enabling Pages

If GitHub Pages is needed again, restore the Pages environment, pages: write, id-token: write, artifact upload, and actions/deploy-pages step in .github/workflows/deploy.yml. Also restore any Pages-specific output files such as .nojekyll only if the serving target requires them.