[Docs] fix glTF doc link error

[zhuxudong]

Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

Summary by CodeRabbit

• Documentation
  • Restructured and updated the plugin feature table for better clarity in glTF documentation.
  • Added new plugins: KHR_texture_basisu, KHR_materials_ior, and KHR_materials_anisotropy, enhancing engine functionality.
  • Updated URLs in the shader API documentation to point to the latest version on the main branch.
  • Adjusted hyperlink reference in the Entity Inspector documentation for consistency.

[coderabbitai]

Walkthrough

The documentation has undergone significant updates to improve clarity and usability. Notable changes include a restructured glTF plugin feature table, updated links to official resources, and the addition of new plugins for enhanced functionality. Additionally, URL updates in shader documentation ensure access to the latest versions. Minor adjustments to hyperlink references also standardize documentation paths, enhancing overall navigation for users.

Changes

Files	Change Summary
docs/zh/graphics/model/glTF.md	Restructured plugin feature table, added new plugins (KHR_texture_basisu, KHR_materials_ior, KHR_materials_anisotropy), updated links, and removed outdated references.
docs/zh/graphics/shader/shaderAPI.mdx	Updated URLs from dev/1.3 to main for consistency across shader files; no content changes.
docs/zh/interface/inspector.md	Adjusted hyperlink for the "实体" (Entity) documentation to reflect a standardized link path.

Poem

🐰 In the garden of code, changes bloom bright,
Plugins and links dance in the light.
A hop here, a skip there, clarity's found,
With each little tweak, new joy will abound!
So let’s celebrate, with a cheer and a cheer,
For the docs are now better, oh what a year! 🌸

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @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.

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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5e0791e and 6ca0019.

Files selected for processing (3)

• docs/zh/graphics/model/glTF.md (1 hunks)
• docs/zh/graphics/shader/shaderAPI.mdx (7 hunks)
• docs/zh/interface/inspector.md (1 hunks)

Files skipped from review due to trivial changes (2)

• docs/zh/graphics/shader/shaderAPI.mdx
• docs/zh/interface/inspector.md

Additional comments not posted (1)

docs/zh/graphics/model/glTF.md (1)

44-57: Ensure the accuracy of plugin links and descriptions.

The updated table of supported plugins includes new plugins and updated links. Verify that each link points to the correct resource and that the descriptions accurately reflect the plugin's functionality.

[cptbtptpbcptdtptp]

+1