fix(public): replace internal submission-prep notes visible on four pages - #186
Conversation
The Promptly and Drishti privacy pages still carried internal editorial
and submission-prep notes as visible copy on main: H1s spoke to the
launch calendar ('already public ahead of release', 'already in place
before launch'), the hero lead referenced the 'current planned launch
scope' and 'final App Store privacy disclosures before release', the
aside was labeled 'Current release scope' with 'not publicly released
yet' and 'currently planned launch configuration', the first card
eyebrow said 'At launch', and the important note told visitors the
page and App Store privacy answers 'should be updated before that
version is submitted'.
The terms page referenced the release pipeline ('if a released app
needs them', 'as new releases are prepared'), and the studio privacy
hub referenced submission-time App Store metadata and privacy
disclosures.
Rewrite those passages as visitor-facing copy that describes what each
page covers and how information is used, without referencing the
internal launch or submission process. Heading levels, links, meta
tags, chips, and JSON-LD are unchanged.
Public-site checks: heading hierarchy, structured data, link targets,
brand disambiguation, conversion signal, social preview, soft-404,
deploy bundle -- all passing.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (5)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughReplaced pre-launch and App Store submission references with current visitor-facing language across Promptly and Drishti privacy pages, the privacy hub, and terms. Added an internal report documenting the copy changes, validation, content sweep, and deployment status. ChangesPolicy copy updates
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This PR replaces internal submission-preparation wording with visitor-facing copy on four public pages while preserving page structure and metadata; no actionable merge-blocking risk remains after the reported checks. Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login. Comment |
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
Only conflict was the advertising/tracking paragraph on drishti/privacy, where PR #186 landed alternative wording on main. Took main wording; this branch remaining value is the two product-page rewrites and the test-public-app-copy-voice.mjs guard, which passes against main copy (62 checks, 0 failures).
1 participant
What
Four tinystudio.in public pages carried internal editorial and submission-prep notes as visible copy:
public/promptly/privacy/index.html— H1 "already public ahead of release", lead "current planned launch scope ... final App Store privacy disclosures before release", aside "Current release scope" / "Promptly is not publicly released yet", card eyebrow "At launch", note telling visitors the page and App Store answers "should be updated before that version is submitted".public/drishti/privacy/index.html— same pattern ("already in place before launch", "not publicly released yet", "should be updated before that version is submitted").public/terms/index.html— "if a released app needs them", "as new releases are prepared".public/privacy/index.html— "so App Store metadata can point to a more specific policy", "App Store privacy disclosures can stay connected to app-specific public documentation".Fix
Rewrote those passages as visitor-facing copy describing what each page covers and how information is used — no references to the internal launch calendar, release scope, planned launch configuration, or App Store submission process. Heading levels, links, meta tags, chips, and JSON-LD are unchanged.
Validation
All passing on this branch:
git diff --checkFresh sweep of
public/forlaunch scope|launch configuration|release scope|not publicly released|ahead of release|before launch|should be updated before|is submitted|releases are prepared|a released app needs|App Store metadata→ zero matches.Note: live tinystudio.in is still serving stale content (deploys blocked on the missing Cloudflare token); this source fix lands once deploys resume.
Summary by CodeRabbit