Self-contained, responsive HTML/CSS site. No JavaScript, build step, packages, remote fonts, tracking, or external asset requests. All website files live in this folder; the application source is unchanged.
Open index.html directly, or run python -m http.server 8088 --directory docs from the repository root and visit http://localhost:8088.
After committing and pushing this folder, open the repository’s Settings → Pages. Choose Deploy from a branch, select the branch containing these files, select /docs, and save. GitHub supplies the public URL once deployment completes. No custom domain is assumed. All asset URLs are relative so the site also works under a repository subpath.
The .nojekyll file keeps this a plain static site. You can alternatively upload the contents of docs/ as the Pages artifact in an existing GitHub Actions workflow. There is no need to publish the rest of the application repository as site content. See GitHub’s publishing-source instructions.
support/index.html and privacy/index.html provide the /support/ and
/privacy/ pages under the site’s published base URL. The homepage and both
pages include footer links to them. Directory-based pages and relative links
work with GitHub Pages project URLs as well as custom domains.
Both pages provide a clickable mailto:support.app.phototether@travels4pics.com
link. The privacy policy covers the apps’ local storage and local-network
transfers, no analytics or tracking, and users’ continued ownership of their
content. It distinguishes voluntary support emails from automatic app data
collection. Review and update the policy if the app’s data practices change.
The two entries in index.html under id="availability" deliberately show non-interactive Coming soon labels. When the store pages are live, replace each .release-status span with a descriptively labeled anchor to the correct listing (for example, Download for Windows or View on the App Store). Add separate anchors for each host platform as needed, update the release copy and header label, and verify each actual destination. No placeholder store URLs are included.
assets/host-gallery.png: unchanged app capture from artifacts/ui-preview/canon-crash-replay/canon-replay-0.png (1380 × 920).assets/host-setup.png: unchanged app capture from artifacts/ui-preview/connection-settings/connection-settings-collapsed.png (1380 × 920).assets/phototether-icon.png: existing host icon from src/PhotoTether/Assets/phototether-icon.png.assets/mirror-icon.png: existing native Mirror icon from mirror/PhotoTetherMirror/Assets.xcassets/AppIcon.appiconset/AppIcon.png.The two screenshots are real rendered host-app captures already present in the repository. They are not fabricated interfaces. They show a development session; setup ports, local addresses, and file paths are illustrative and must not be copied as camera settings. No native iOS Mirror screenshots were available in the repository, so the Mirror section uses its real icon and a connection diagram, not a mislabeled host or browser screenshot. A native iPad/iPhone gallery capture can replace that illustration when available.
Feature and compatibility copy is based on the root README.md, mirror/README.md, and native Mirror startup view. Keep these constraints visible when editing: network + FTP camera support, active host on the same LAN, format-dependent RAW decoding, and storage minimums. Windows/macOS describe the host platforms; iOS/iPadOS 16+ describes native Mirror. Store availability, pricing, and approval dates are intentionally not claimed.
The FAQ uses native HTML details elements. Navigation and screenshot links work without JavaScript. Responsive layouts, visible keyboard focus, a skip link, image descriptions, and reduced-motion support are included.