fix(public): name the Website Correction buyer audience in the homepage hero - #91
Conversation
…ge hero The hero on / introduced the managed service as being 'for founders' without ever naming the audience PRODUCT.md defines: founder-led managed IT and cybersecurity companies with a live site. The contact page and the managed-service section already used that phrasing; the hero was the remaining gap. Name the audience in the hero lead and the hero-rail item so the first viewport on / states the actual buyer. Update the deploy-bundle snooze regex to keep stripping the hero lead from the publishable bundle.
![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.
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: 0 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 4 reviews per hour. 📝 WalkthroughWalkthroughThe homepage now targets founder-led managed IT and cybersecurity companies with live sites. The managed-service copy identifies the service as human-reviewed. The deployment-bundle script matches the revised hero text. ChangesManaged service messaging
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This PR clarifies the homepage hero audience and keeps the publishable bundle behavior aligned; no actionable merge-blocking risk remains after normal checks and review. Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@public/index.html`:
- Line 150: Update the rail copy near the managed-service audience description
to include “with a live site,” matching the eligibility language used by the
hero lead and managed-service section while preserving the rest of the sentence.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 4d36a1ec-2421-403f-bf2a-9330a48a10b1
📒 Files selected for processing (2)
public/index.htmlscripts/prepare-public-deploy-bundle.mjs
| <span class="rail-label">Managed service</span> | ||
| <strong><a data-measure-source="homepage-hero" href="/contact/?source=homepage-hero#website-correction-application">The Website Correction</a></strong> | ||
| <p>One human-reviewed correction pass for founders, by email.</p> | ||
| <p>One human-reviewed correction pass for founder-led managed IT and cybersecurity companies, by email.</p> |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Keep the managed-service audience description consistent.
The hero lead and managed-service section require companies with a live site. This rail copy omits that qualifier. Add with a live site so all homepage entry points describe the same eligibility criteria.
Proposed fix
- <p>One human-reviewed correction pass for founder-led managed IT and cybersecurity companies, by email.</p>
+ <p>One human-reviewed correction pass for founder-led managed IT and cybersecurity companies with a live site, by email.</p>📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| <p>One human-reviewed correction pass for founder-led managed IT and cybersecurity companies, by email.</p> | |
| <p>One human-reviewed correction pass for founder-led managed IT and cybersecurity companies with a live site, by email.</p> |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@public/index.html` at line 150, Update the rail copy near the managed-service
audience description to include “with a live site,” matching the eligibility
language used by the hero lead and managed-service section while preserving the
rest of the sentence.
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.
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.
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.
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.
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.
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.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
1 participant
What
The homepage hero on
/introduced The Website Correction as a managed service "for founders" without ever naming the audience PRODUCT.md defines: founder-led Managed IT/MSP/cybersecurity companies with a live site. The contact page and the homepage managed-service section already name that audience; the first viewport of the hero was the remaining gap.Change
public/index.htmlhero lead now names the buyer: "There is also one human-reviewed managed service for founder-led managed IT and cybersecurity companies with a live site: The Website Correction."scripts/prepare-public-deploy-bundle.mjssnooze regex (HOMEPAGE_HERO_LEAD) updated in lockstep so the publishable bundle still strips the buyer-path sentence.Verification
node scripts/test-public-deploy-bundle.mjs: 62 checks, 0 failuresnpm run ci: exit 0,"failures": []Summary by CodeRabbit