docs: refine landing page — version badge format and mcpd logo - #293
Conversation
|
Warning Review limit reached
Next review available in: 11 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
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. Comment |
The landing-page badge read 'Version: v0.1.0 (documents mcpd v0.5.0)' -- leading with the docs version and jammed between the title and tagline. It now renders 'mcpd v0.5.0 (docs v0.1.0)' (or 'docs vX' when no mcpd release is resolved) and sits below the tagline, before the first divider, via an explicit marker in index.md. Replaces the heading-and-fence-scanning injection with a straightforward marker replacement, which also fails loudly if the marker is ever removed.
Sibling products on docs.mozilla.ai (encoderfile, llamafile) show their product logo on the home page for visual identification. Re-add the mcpd logo -- dropped in the migration because it depended on the old MkDocs custom CSS -- as a plain PNG image under the H1, which needs no theming. The SVG is also available if preferred.
1b18c31 to
bb8015b
Compare
The logo PNG is 1660x1697 (near square), so GitBook scaled it to the column width and rendered it huge. Cap it at width 200 with an <img> tag, matching the README's sizing and llamafile's git-synced pattern.
2 participants
Two landing-page refinements for the GitBook site.
Version badge
Before, the badge read
Version: v0.1.0 (documents mcpd v0.5.0)— leading with the docs version and jammed between the# mcpdtitle and the tagline. It now:mcpd v0.5.0 (docs v0.1.0)(ordocs vXwhen no mcpd release is resolved);<!-- version-badge -->marker inindex.md, so the title and tagline stay together and the badge gets its own space.The heading/fence-scanning injection is replaced with a straightforward marker replacement that fails loudly if the marker is ever removed.
Landing-page logo
Re-add the mcpd logo to the home page (
under the H1), matching sibling products on docs.mozilla.ai (encoderfile, llamafile) that show a product logo for visual identification. It was dropped in the migration because it relied on the old MkDocs custom CSS; as a plain PNG it needs no theming.