fix(public): repair homepage managed-service heading hierarchy (H2->H3) - #143
Conversation
The homepage managed-service section jumped from the H2 section title straight to an H4 feature heading, skipping H3 and breaking the public heading-hierarchy check that covers every other page. Promote the feature heading to H3 (matching the sibling #teams block) and keep the former h4 scale via .team-feature :is(h3, h4) so the block renders identically. Extend scripts/test-public-heading-hierarchy.mjs with homepage coverage: the full outline must have no jump greater than one, and the #managed-service section must open H2 then H3. Also assert the .team-feature :is(h3, h4) CSS pairing. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
|
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.
|
Warning Review limit reached
Next review available in: 44 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: Free Run ID: 📒 Files selected for processing (4)
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.
1 participant
What
The homepage
#managed-servicesection skipped a heading level: the section title is an H2 and the feature heading was an H4, jumping straight over H3. The public heading-hierarchy test covered every other page but the homepage, so this went unguarded.Fix
public/index.html: promote the managed-service feature heading from H4 to H3 (matching the sibling#teamsblock outline H2 → H3).public/styles.css: keep the former h4 scale and margin for that heading via.team-feature :is(h3, h4)plus a.team-feature h3scale rule, so the block renders identically.scripts/test-public-heading-hierarchy.mjs: add homepage coverage — the full homepage outline must have no heading-level jump greater than one, the#managed-servicesection must open H2 then H3, and the.team-featureCSS pairing is asserted.Verification
node scripts/test-public-heading-hierarchy.mjs→ 89 checks, 0 failures (was 81 before, now includes homepage coverage). Full public-site test set passes. The only failing script innpm test(check-retention-automation.mjs) fails identically on cleanorigin/main— pre-existing data-parity issue unrelated to this change.