exifcleaner-web/static
forgejo_admin 948af5433e
Some checks are pending
CI / E2E (Web) (push) Blocked by required conditions
CI / E2E (Standalone single-file) (push) Blocked by required conditions
CI / Lint, Typecheck & Unit Tests (push) Successful in 16m15s
docs(readme): web-first framing + standalone HTML build path (#90)
## Summary

Brings the README in line with the v5 codebase and the [`modernization-roadmap.md`](.claude/rules/modernization-roadmap.md) web-only direction. The previous README still framed ExifCleaner as a desktop app first — "Desktop app + browser webapp" tagline, a "Download and Install" section linking to upstream `szTheory/exifcleaner` .dmg / .exe / .AppImage from v3.6.0 (May 2021, pre-Phase-D).

## Changes

- **Tagline** → "Runs entirely in your browser — no uploads, no server."
- **Features list** → drops the cross-platform line; leads with "Browser-based: install as a PWA or run from a single self-contained HTML file." Also corrects the privacy-controls line — Phase F #83 enforces epoch timestamps, there is no "preserve timestamps" setting (per [`privacy-invariants.md`](.claude/rules/privacy-invariants.md) §6).
- **Remove "Download and Install" entirely** — the upstream desktop links pointed at the legacy v3.6.0 binaries (last released May 2021); they don't reflect the v5 codebase, and sending users there is misleading.
- **"Running the web app locally"** gets a new **Option 1: Single-file HTML** via `yarn build:web:standalone` (lands in [docs/standalone-html.md](docs/standalone-html.md), shipped in #89). Docker / Node dev server / build+preview shift to Options 2–4.
- **Drop the screenshot** — `static/screenshot.png` pre-dated the BEFORE/AFTER/RESULT columns (#88) and the overall v5 UI. File deleted; reference removed. A fresh screenshot is a separate task with its own decisions (mode, sample files, platform chrome).

## Out of scope (deliberately not in this PR)

- New screenshot — separate task.
- Touching the "Development" section. `yarn dev` still launches Electron and that path is functional until Phase G ships; the README's dev instructions match the current dev workflow even if they downplay the Web-first direction.
- Editing `CLAUDE.md`, `project-direction.md`, or `modernization-roadmap.md`. Those are internal docs for contributors and Claude; reframing them is a larger swing.

## Test plan

- [x] `yarn lint` (prettier) passes on README.md
- [ ] Reviewer eyeballs the rendered README in Forgejo's preview to confirm the option ordering and section flow read cleanly
- [ ] No broken intra-repo links (docs/standalone-html.md and the other doc paths all exist)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Randa <obuvuyoviz26@gmail.com>
Reviewed-on: http://localhost:3000/forgejo_admin/exifcleaner-web/pulls/90
2026-05-14 07:06:19 +04:00
..
icon.svg feat(quick-260402-nza): update app icon to teal brand colors (#286) 2026-04-02 17:28:54 -04:00