fix: neutral inline code color and explicit github syntax themes for readability

[vihar]

Problem

Dark-mode inline code was nearly unreadable: styles.css hardcoded --vp-code-color: #006399 (the light-mode brand blue) in a block that also applies in dark mode, producing dark-blue-on-dark text. Even without that, VitePress defaults inline code to the brand color, which reads poorly on the dark pill background.

Before

After

Changes

• styles.css: replace the hardcoded --vp-code-color: #006399 with var(--vp-c-text-1) and add the same neutral override in the base :root block — inline code now uses the body-text color in both modes (GitHub-style). Code inside links keeps brand blue via --vp-code-link-color.
• config.mts: declare the syntax themes explicitly (github-light/github-dark) — same values VitePress defaults to, now pinned and consistent with makeplane/docs.

Verification

• Served the production build and checked the Download Docker config files page in both modes: inline code (prime-cli, docker-compose.yml, parameter table pills) is now high-contrast neutral; bash blocks render fine; links keep brand blue.
• pnpm check:format and pnpm build pass.

Companion PR: makeplane/docs#479

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
developer-docs	Ready	Preview, Comment	Jul 23, 2026 3:02pm

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 59 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 67f0f72b-6e65-4006-8e67-721efadc7708

📥 Commits

Reviewing files that changed from the base of the PR and between b8582bc and c72daca.

📒 Files selected for processing (2)

• docs/.vitepress/config.mts
• docs/.vitepress/theme/styles.css

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/dark-mode-code-readability

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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