Skip to content

feat(website): Add Privacy Policy link to top navigation bar#1227

Closed
yamadashy wants to merge 1 commit intomainfrom
claude/add-privacy-policy-nav-cSiC4
Closed

feat(website): Add Privacy Policy link to top navigation bar#1227
yamadashy wants to merge 1 commit intomainfrom
claude/add-privacy-policy-nav-cSiC4

Conversation

@yamadashy
Copy link
Owner

@yamadashy yamadashy commented Mar 13, 2026

Add Privacy Policy as a top-level navigation item across all 15 language
configurations, linking to each locale's existing privacy policy page.

https://claude.ai/code/session_01JqMS8rRE7ZBWagNcHEwTVj


Open with Devin

Add Privacy Policy as a top-level navigation item across all 15 language
configurations, linking to each locale's existing privacy policy page.

https://claude.ai/code/session_01JqMS8rRE7ZBWagNcHEwTVj
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 13, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: c044f9a2-bbde-4c27-a40c-e850b6b45157

📥 Commits

Reviewing files that changed from the base of the PR and between d108075 and 87d72a2.

📒 Files selected for processing (15)
  • website/client/.vitepress/config/configDe.ts
  • website/client/.vitepress/config/configEnUs.ts
  • website/client/.vitepress/config/configEs.ts
  • website/client/.vitepress/config/configFr.ts
  • website/client/.vitepress/config/configHi.ts
  • website/client/.vitepress/config/configId.ts
  • website/client/.vitepress/config/configIt.ts
  • website/client/.vitepress/config/configJa.ts
  • website/client/.vitepress/config/configKo.ts
  • website/client/.vitepress/config/configPtBr.ts
  • website/client/.vitepress/config/configRu.ts
  • website/client/.vitepress/config/configTr.ts
  • website/client/.vitepress/config/configVi.ts
  • website/client/.vitepress/config/configZhCn.ts
  • website/client/.vitepress/config/configZhTw.ts

📝 Walkthrough

Walkthrough

Adds privacy policy navigation links across 15 language-specific VitePress configuration files. Each configuration file receives one new navigation entry with the appropriate language translation, linking to /[locale]/guide/privacy.

Changes

Cohort / File(s) Summary
Language-Specific Navigation Config Files
website/client/.vitepress/config/configDe.ts, configEnUs.ts, configEs.ts, configFr.ts, configHi.ts, configId.ts, configIt.ts, configJa.ts, configKo.ts, configPtBr.ts, configRu.ts, configTr.ts, configVi.ts, configZhCn.ts, configZhTw.ts
Added one navigation item per configuration file linking to the privacy policy in the respective language. Each entry includes localized text (e.g., "Privacy Policy", "Datenschutzrichtlinie", "Politique de confidentialité", etc.) and the appropriate locale-specific route.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • docs(website): Add Privacy Policy page #981 — Previously added privacy policy pages and community/sidebar links; this PR complements by adding corresponding top-navigation entries across all language configurations.
🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive The description explains the change intent and scope but does not follow the provided repository template, which requires checklist items for running tests and linting. Add a checklist section with items for running npm run test and npm run lint as specified in the repository template.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely summarizes the main change: adding Privacy Policy links to the top navigation bar across all supported languages.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
  • 📝 Generate docstrings (stacked PR)
  • 📝 Generate docstrings (commit on current branch)
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch claude/add-privacy-policy-nav-cSiC4
📝 Coding Plan
  • Generate coding plan for human review comments

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 and usage tips.

Tip

You can make CodeRabbit's review stricter and more nitpicky using the `assertive` profile, if that's what you prefer.

Change the reviews.profile setting to assertive to make CodeRabbit's nitpick more issues in your PRs.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly improves the website's user experience and legal compliance by integrating a readily accessible Privacy Policy link into the top navigation bar. This change is consistently applied across all supported language versions, ensuring that privacy information is easily found by users regardless of their preferred language.

Highlights

  • Privacy Policy Link Added: A new 'Privacy Policy' link has been added to the top navigation bar across all 15 language configurations of the website.
  • Internationalization: Each Privacy Policy link is localized, pointing to the appropriate privacy policy page for its respective language locale.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • website/client/.vitepress/config/configDe.ts
    • Added a 'Datenschutzrichtlinie' (Privacy Policy) link to the top navigation.
  • website/client/.vitepress/config/configEnUs.ts
    • Added a 'Privacy Policy' link to the top navigation.
  • website/client/.vitepress/config/configEs.ts
    • Added a 'Política de Privacidad' (Privacy Policy) link to the top navigation.
  • website/client/.vitepress/config/configFr.ts
    • Added a 'Politique de confidentialité' (Privacy Policy) link to the top navigation.
  • website/client/.vitepress/config/configHi.ts
    • Added a 'गोपनीयता नीति' (Privacy Policy) link to the top navigation.
  • website/client/.vitepress/config/configId.ts
    • Added a 'Kebijakan Privasi' (Privacy Policy) link to the top navigation.
  • website/client/.vitepress/config/configIt.ts
    • Added an 'Informativa sulla Privacy' (Privacy Policy) link to the top navigation.
  • website/client/.vitepress/config/configJa.ts
    • Added a 'プライバシーポリシー' (Privacy Policy) link to the top navigation.
  • website/client/.vitepress/config/configKo.ts
    • Added a '개인정보 처리방침' (Privacy Policy) link to the top navigation.
  • website/client/.vitepress/config/configPtBr.ts
    • Added a 'Política de Privacidade' (Privacy Policy) link to the top navigation.
  • website/client/.vitepress/config/configRu.ts
    • Added a 'Политика конфиденциальности' (Privacy Policy) link to the top navigation.
  • website/client/.vitepress/config/configTr.ts
    • Added a 'Gizlilik Politikası' (Privacy Policy) link to the top navigation.
  • website/client/.vitepress/config/configVi.ts
    • Added a 'Chính sách Bảo mật' (Privacy Policy) link to the top navigation.
  • website/client/.vitepress/config/configZhCn.ts
    • Added a '隐私政策' (Privacy Policy) link to the top navigation.
  • website/client/.vitepress/config/configZhTw.ts
    • Added a '隱私權政策' (Privacy Policy) link to the top navigation.
Activity
  • No specific activity (comments, reviews, or progress updates) has been recorded for this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.

Open in Devin Review

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds a 'Privacy Policy' link to the main navigation bar across all supported languages (German, English, Spanish, French, Hindi, Indonesian, Italian, Japanese, Korean, Brazilian Portuguese, Russian, Turkish, Vietnamese, Simplified Chinese, and Traditional Chinese) by updating their respective VitePress configuration files.

@claude
Copy link
Contributor

claude bot commented Mar 13, 2026

PR Review: feat(website): Add Privacy Policy link to top navigation bar

Overall Assessment

This is a clean, straightforward PR that adds a Privacy Policy link to the top navigation bar across all 15 locale configurations. The implementation is consistent and all referenced privacy pages exist.

Verdict: Looks good with one design consideration worth discussing.


Positive Aspects

  • All 15 locale configs are updated consistently
  • All linked privacy pages (/xx/guide/privacy) already exist — no broken links
  • Translations appear accurate for each locale
  • The change is minimal and low-risk (15 one-line additions, 0 deletions)

Design Consideration: Nav Bar vs Footer Placement

Details

The Privacy Policy link is added as a top-level nav item, making the nav bar go from 3 to 4 items:

  1. Guide (internal)
  2. Chrome Extension (external)
  3. Join Discord (external)
  4. Privacy Policy (internal) ← new

While 4 items is still reasonable, a privacy policy link is conventionally placed in the footer rather than the top navigation. The shared config (configShard.ts) already has a footer:

footer: {
  message: 'Released under the MIT License.',
  copyright: 'Copyright © 2024 Kazuki Yamada',
}

Suggestion: Consider whether the footer would be a more conventional location for this link. If placed in the footer's message field in configShard.ts, it could be done in a single file change rather than 15 — though it would lose per-locale translation of the link text.

This is a UX/design decision, not a code quality issue — either approach works. Just flagging for the maintainer's consideration.


Premortem: Potential Failure Scenarios

Scenario Risk Mitigation
Nav bar overflow on mobile Low 4 items is within typical VitePress limits; VitePress collapses to hamburger menu on mobile
Privacy page content missing for a locale None Verified — all 15 privacy.md files exist
Broken links after deployment Very Low Links follow the same /xx/guide/ pattern as existing nav items

Summary

No blocking issues. The PR is clean, consistent across all locales, and links are verified. The only point for discussion is whether the top nav or footer is the preferred placement — that's a product decision for the maintainer.

🤖 Generated with Claude Code

@codecov
Copy link

codecov bot commented Mar 13, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.14%. Comparing base (d108075) to head (87d72a2).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1227   +/-   ##
=======================================
  Coverage   87.14%   87.14%           
=======================================
  Files         115      115           
  Lines        4310     4310           
  Branches      998      998           
=======================================
  Hits         3756     3756           
  Misses        554      554           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@yamadashy yamadashy closed this Mar 14, 2026
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.

2 participants