fix(public): remove internal editorial and submission-prep copy from the four app pages - #28
Conversation
…he four app pages
Promptly and Drishti product and support pages carried internal
submission-prep notes as visible copy: launch notes, App Store
Connect/submission readiness language, and editorial self-commentary
("already", "current build", "in the meantime", "what this page
already does").
Rewrite those passages as visitor-facing copy that describes the
product and the support route without referencing the internal
submission process. Heading levels, links, meta tags, and JSON-LD
are unchanged.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
Warning Review limit reached
Next review available in: 26 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
Comment |
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
…nternal-notes # Conflicts: # public/drishti/support/index.html
…es' into fix/public-app-copy-internal-notes
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
… support and contact pages (#31) The Studio-level /support/ and /contact/ pages still carried submission-prep notes as visible copy after the app pages were cleaned in #28: references to App Store Connect URLs, App Store submission readiness, app store reviewers, and launch-page staging rules. Rewrite those passages as visitor-facing copy that describes the support inbox, the app-specific pages, and the contact routes without referencing the internal submission process. Heading levels, links, meta tags, and JSON-LD are unchanged.
1 participant
What
Internal editorial and submission-prep notes were live as visible copy on the four public app pages. Visitors could read notes meant for the studio's own planning: launch notes, App Store Connect / submission-readiness language, and self-referential editorial commentary ("already", "current build", "in the meantime", "what this page already does").
Changed pages
/promptly//drishti//promptly/support//drishti/support/Each passage is rewritten as visitor-facing copy describing the product or the support route, keeping the site's truthful no-launch-claims stance. No titles, meta descriptions, heading levels, links, or JSON-LD changed.
Out of scope by design: the
/contact/page's "internal measurement marker" disclosure is a deliberate, test-enforced privacy disclosure (test-public-conversion-signal.mjspins it), and the shared footer tagline ("clean public foundation before launch") is identical studio copy across all twelve pages.Verification
npm test— exit 0 (full repo gate)test-public-heading-hierarchy— 18 checks, 0 failurestest-public-link-targets— 74 checks, 0 failurestest-public-structured-data— 31 checks, 0 failurestest-public-conversion-signal— 126 checks, 0 failuresgit diff --check— clean