fix: broken url in docs

[MrKou47]

Summary by CodeRabbit

• Documentation
  • Updated hyperlinks in multiple documentation files for enhanced clarity and navigation.
  • Changed link formats from relative paths, including placeholder variables, to absolute paths across various sections.
  • Improved user experience by ensuring all links point directly to the correct API documentation resources.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The recent documentation updates primarily focus on enhancing hyperlink clarity and accessibility across various files for the Galacean Engine. By replacing relative path references with absolute paths, the changes improve navigation for users, ensuring they reach the intended API documentation effortlessly. The overall content and functionality of the documents remain intact, emphasizing a cleaner, more user-friendly documentation experience.

Changes

Files Grouped	Change Summary
docs/en/core/canvas.md, docs/en/core/engine.md, docs/en/quick-start/core-concept.md, docs/en/quick-start/overview.md, docs/zh/core/canvas.md, docs/zh/core/engine.md	Updated hyperlinks to use direct paths instead of relative paths with ${api} placeholder, enhancing clarity and accessibility.
docs/en/graphics/camera/component.md, docs/en/graphics/camera/depthTexture.md, docs/zh/graphics/camera/component.md	Reformatted Markdown links for rendering-related properties for improved consistency and readability.
docs/en/graphics/particle/..., docs/zh/graphics/particle/...	Updated links from ${api} to absolute paths for various particle modules and properties, ensuring correct navigation to API documentation.
docs/zh/graphics/shader/...	Modified links from relative to absolute paths across multiple shader-related documents, improving accessibility while retaining content integrity.
docs/zh/graphics/texture/compression.md	Corrected a link reference from a variable path to a direct relative path, ensuring accurate resource navigation.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Documentation
    User->>Documentation: Access documentation links
    Documentation->>User: Provide accurate resources
    User->>Documentation: Navigate easily
    Documentation->>User: Enhanced user experience

Loading

Poem

🐇 In the garden of code, I hop with glee,
Links now clear as the sky, oh so free!
A path to knowledge, bright and wide,
No more confusion, let’s take the ride!
With every click, our wisdom grows,
Thank you, dear docs, for the lovely prose! 🌼

---

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.