Skip to content

Clean up docs landing page header - #998

Merged
bharvey88 merged 1 commit into
devfrom
landing-remove-logo-and-home
Jul 1, 2026
Merged

Clean up docs landing page header#998
bharvey88 merged 1 commit into
devfrom
landing-remove-logo-and-home

Conversation

@bharvey88

Copy link
Copy Markdown
Contributor

Remove the banner logo image from the top of the landing page and suppress the auto-injected Home H1 so the page opens directly on the welcome admonition. A hidden H1 preserves the document outline for SEO/accessibility (mkdocs-material only injects the nav-title H1 when the page body has no heading of its own).

🤖 Generated with Claude Code

Remove the banner logo image from the top of the landing page and
suppress the auto-injected "Home" H1 so the page opens directly on the
welcome admonition. A hidden H1 preserves the document outline for SEO
and accessibility.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
@bharvey88
bharvey88 merged commit eda1c57 into dev Jul 1, 2026
@bharvey88
bharvey88 deleted the landing-remove-logo-and-home branch July 1, 2026 16:38
@coderabbitai

coderabbitai Bot commented Jul 1, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@bharvey88, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 19 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9d0a39be-990f-4601-8641-8ccda01c6ca3

📥 Commits

Reviewing files that changed from the base of the PR and between c5dc808 and 488ea27.

📒 Files selected for processing (1)
  • docs/index.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch landing-remove-logo-and-home

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant