docs: update v8 docs links to point to legacy site

[babu-ch]

fixes #2225

Summary by CodeRabbit

• Documentation
  • Updated documentation links to direct users to the new official site for improved access to guides and API references.

[coderabbitai]

Walkthrough

The documentation file docs/guide/extra/v8-docs.md was updated to replace all old GitHub-hosted markdown links with new URLs pointing to the kazupon.github.io/vue-i18n site. The link structure and section names remain unchanged, but all references now use the new hosting location and .html extensions.

Changes

File(s)	Change Summary
docs/guide/extra/v8-docs.md	Updated all documentation links from GitHub docs-old/*.md to kazupon.github.io/vue-i18n/*.html

Assessment against linked issues

Objective	Addressed	Explanation
Update v8 docs links to point to accessible location (#2225)	✅

Suggested labels

Type: Documentation

Suggested reviewers

• kazupon

Poem

🐇
Hopping through docs, I fix each link,
From markdown old to HTML in a blink.
Now every guide and API page
Opens anew, no broken cage!
With every hop, the docs delight—
A bunny’s work, done just right.
📚✨

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

docs/guide/extra/v8-docs.md (2)

7-20: Consider automating link verification for the long “Guide” section.

All anchors look fine at a glance, but 14 deep links is a lot to keep manually in sync with the legacy site.
A small CI check (e.g. linkinator, lychee, or a bash curl loop) would prevent silent rot.

No change required for this PR—just flagging the maintainability angle.

---

21-21: Nit: add trailing slash for directory URL for marginally faster redirects.

https://kazupon.github.io/vue-i18n/api/ avoids the extra 301 compared with .../api (no slash).
Low-impact but easy win.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4386900 and 3a0d7eb.

📒 Files selected for processing (1)

• docs/guide/extra/v8-docs.md (1 hunks)

🔇 Additional comments (1)

docs/guide/extra/v8-docs.md (1)

3-5: ✅ All top-level links resolve correctly

Verified each URL with a quick curl check—introduction.html, started.html, and installation.html all return HTTP 200. No path adjustments needed.

[kazupon]

Thank you so much!