Repository navigation
[iOS 1.0] Publish a marketing landing page, support site, and privacy policy #49
Description
Outcome
Publish a marketing landing page, support site, and privacy policy.
Release tracker: [iOS 1.0] First App Store release tracker
Acceptance criteria
- Create an accessible public landing page for the approved game identity, with genuine screenshots, supported devices/modes, offline and local-score behavior, and a clear download action. A static GitHub Pages site is sufficient if the owner approves that hosting choice.
- Publish stable HTTPS marketing, support, and privacy URLs that work without an account. Include rules/help, known limitations, app version/help locating the build, feedback options, and local-data reset/restore guidance.
- Do not expose developer account information, test data, private contacts not approved for publication, secrets, or signed build artifacts. Keep support issue templates and any private reporting channel linked and usable.
- Keep the website and App Store product-page claims consistent with the tested app. State that local high scores are not global multiplayer rankings. Do not advertise unimplemented cloud sync, remote players, Watch, or widgets.
- Use Apple badges and branding according to their current guidelines. Before public availability, use an honest release status rather than a broken or invented App Store link; replace it with the verified listing at launch.
- Test responsive layout, accessibility, link health, and privacy/support reachability from an unauthenticated browser. Document deployment and ownership so updates do not depend on one local checkout.
Dependencies
- [iOS 1.0] Confirm first-release scope, public name, and brand rights
- [iOS 1.0] Audit privacy, native SDK manifests, permissions, and export compliance
- [iOS 1.0] Create licensed iOS app icons, launch assets, and brand files
Validation and completion
Record the live HTTPS URLs and owner-approved published copy. Confirm the support and privacy pages contain the actual required information, not placeholders or a login wall.
Record the exact source revision, commands/artifacts, or sanitized App Store evidence as appropriate. Keep credentials and private contact/identity details out of this issue. Implementation changes must pass affected repository gates and receive review.
Activity
HemSoft commentedon Sep 27, 2026
Mission completion blocker
Approved public identity, public support contact, accurate privacy policy and publication authority for that copy.
Evidence and two self-serve paths checked:
Safe default: Do not publish a misleading product/privacy page or invent an App Store download URL.
Owner action: Approve the original identity, public contact, hosting choice and evidence-backed privacy copy after #48. Site implementation/publication remains pending.
This is a blocker to this issue's full acceptance contract, not a claim that its unfinished implementation is complete. Repository-only preparation continues through the linked PRs; this issue stays open.
HemSoft commentedon Sep 28, 2026
The unpublished companion preview merged in PR #58 at c801bbf. Its Validation section contains twelve source-bound screenshots and a played interaction recording: #58. Six site tests, browser checks, current-head Codex and all post-merge workflows passed. No website was deployed. Approved identity, contacts, final privacy copy, genuine approved native captures and stable public HTTPS destinations remain outstanding, so this issue stays open. Build and publication boundaries: https://github.com/HemSoft/yahtzee/blob/c801bbf9aa95246ff0147d371b406c74aa9577e5/site/README.md
HemSoft commentedon Oct 1, 2026
Updated acceptance blocker, October 1, 2026 EDT
This supersedes the September 27 preimplementation assumptions. Native local saves/resume/UI, original development assets, unsigned CI and packaged privacy inspection are now delivered. The static companion site is prepared but unpublished. Screenshot and release/reporting preparation exists in the open PRs, not as accepted store material.
Native foundation #57 and postmerge delivery, unpublished site #58, draft capture preparation #61, and draft release/reporting preparation #62. The last two PRs remain open; connected review capacity was explicitly refused on #61 and on #62. No purchase or substitute reviewer was used.
Remaining need: Explicit hosting/publication authority, approved original identity/contact and accepted privacy copy/stable HTTPS URLs.
Two self-service paths checked:
Safe reversible result: The static website is prepared and unpublished, not unimplemented. Do not upload unapproved policy/contact copy or invent a download link.
Exact owner action: Approve the original identity, contact/privacy text, host/domain/stable HTTPS marketing/support/privacy URLs and deployment/maintenance/rollback ownership before publication.
This issue remains open. Simulator, browser, fictional-fixture and unsigned evidence do not replace signed physical-device or legal/publication acceptance. CI waits and driver failures are still engineering work, not the owner block stated above. No credentials, private contacts or legal declarations are requested in this public issue.
HemSoft commentedon Nov 2, 2026
Left over from the rename in #96, for this issue: every generated page now shows Third Roll in its header, but the shared footer (
site/pages.mjs:13) still says no approved product name is announced, and the privacy page says the product identity hasn't been approved. SFL flagged it as a Low finding, and the site isn't published yet.Update those notices to reflect the name decision on #39, keeping the publisher, contact and privacy approvals pending. Also note that the public repository is still
hemsoft-dev/yahtzee, so any site or Help link to it will show the old name; renaming the repository isn't decided yet.HemSoft commentedon Nov 3, 2026
Delivered by PR #100, merge 754d0f9. Pages deployment https://github.com/hemsoft-dev/yahtzee/actions/runs/41574244090 succeeded. Verified all three stable HTTPS destinations return 200 with expected content, and a fresh unauthenticated Chromium context verified navigation and screenshot assets: https://hemsoft-dev.github.io/yahtzee/ , https://hemsoft-dev.github.io/yahtzee/support.html , https://hemsoft-dev.github.io/yahtzee/privacy.html . Prior repository browser qualification passed all 12 responsive/theme/large-text combinations. Private GitHub security reporting is enabled. No invented store link, new contact address or spending. Signed-device/privacy declaration acceptance remains in #48; this public policy explicitly describes the development app and hosting.