chore: use relative link (#813)

Signed-off-by: rogerogers <[email protected]>

Author: rogerogers

content/en/blog/news/1st_RPCKitex/index.md

@@ -18,7 +18,7 @@ Kitex is CloudWeGo's first open-source microservice framework, designed to empow
 
 One notable feature of Kitex is its support for the gRPC protocol. Leveraging the official gRPC source code, Kitex optimizes the gRPC implementation, resulting in superior performance compared to the official gRPC framework. This sets Kitex apart from other Golang frameworks that offer open-source support for the gRPC protocol. Developers seeking both gRPC functionality and high-performance capabilities will find Kitex to be an excellent choice.
 
-In addition to Kitex, CloudWeGo has recently introduced two other projects to its open-source lineup: [Hertz](https://github.com/cloudwego/hertz), a Golang HTTP framework, and [Volo](https://github.com/cloudwego/volo), a Rust RPC framework. Alongside these microservice frameworks, CloudWeGo offers various high-performance foundational libraries and general microservice capabilities as open-source resources. To explore more of CloudWeGo's open-source sub-projects, visit the [official CloudWeGo website](https://www.cloudwego.io/) for additional information and resources.
+In addition to Kitex, CloudWeGo has recently introduced two other projects to its open-source lineup: [Hertz](https://github.com/cloudwego/hertz), a Golang HTTP framework, and [Volo](https://github.com/cloudwego/volo), a Rust RPC framework. Alongside these microservice frameworks, CloudWeGo offers various high-performance foundational libraries and general microservice capabilities as open-source resources. To explore more of CloudWeGo's open-source sub-projects, visit the [official CloudWeGo website](/) for additional information and resources.
 ![image](/img/blog/Kitex_architecture_explained_en/1.png)
 
 Based on feedback from the community, there have been discussions surrounding whether Kitex is an open-source Key Performance Indicator (KPI) project of ByteDance, as well as concerns about its stability and continuity. We can responsibly state that Kitex is not a KPI project, but rather a genuine project derived from ByteDance's extensive internal practical experience. Since its open-source release, we have consistently maintained consistency between the internal and external development efforts of Kitex. This consistency, coupled with the alignment of internal and external codebases, has ensured the continuous iteration and improvement of Kitex. To address any remaining concerns, let us provide you with a detailed overview of Kitex's development and open-source process.

content/en/blog/news/Hertz_Open_Source/index.md

@@ -30,7 +30,7 @@ Key features of Hertz include:
 ### High Usability
   Hertz prioritizes the ability to write correct code quickly during development. When designing the API, Hertz considers user usage habits and draws inspiration from the industry's mainstream framework API usage. Continuous iteration and user feedback contribute to the framework's refinement. For instance, many users hope that the Client also has the ability to trace. For this reason, Hertz Client supports middleware capabilities. Additionally, the Client supports stream processing in proxy scenarios. Middleware and stream processing are designed with the user's actual habits in mind, promoting faster development of correct code. Hertz also provides a one-click command-line tool for code generation, enhancing the framework's ease of use.
 ### Easy expandability
-  Hertz employs a layered design, offering a range of interfaces and default extension implementations for users to expand upon. Details regarding [Hertz extension](https://www.cloudwego.io/zh/docs/hertz/tutorials/framework-exten/) can be found on the [CloudWeGo official website](https://www.cloudwego.io). The framework's layered design enhances its scalability. Currently, only stable capabilities are open-sourced, with more planned for the future. Please refer to the [Hertz roadmap](https://github.com/cloudwego/hertz/blob/develop/ROADMAP.md) for further details.
+  Hertz employs a layered design, offering a range of interfaces and default extension implementations for users to expand upon. Details regarding [Hertz extension](/zh/docs/hertz/tutorials/framework-exten/) can be found on the [CloudWeGo official website](/). The framework's layered design enhances its scalability. Currently, only stable capabilities are open-sourced, with more planned for the future. Please refer to the [Hertz roadmap](https://github.com/cloudwego/hertz/blob/develop/ROADMAP.md) for further details.
 
 ### Low latency
   Hertz utilizes the internally developed high-performance network library,  [Netpoll](https://github.com/cloudwego/netpoll), by default. In certain special scenarios, Hertz demonstrates advantages in terms of QPS and delay compared to the go net package.
@@ -64,4 +64,4 @@ We welcome everyone to [contribute](https://github.com/cloudwego/hertz/blob/deve
 ## Related Links
 - Project [address](https://github.com/cloudwego/hertz)
 - Community [ecosystem](https://github.com/hertz-contrib)
-- Hertz benchmark [blog](https://www.cloudwego.io/blog/2023/02/24/getting-started-with-hertz-performance-testing-guide/)
+- Hertz benchmark [blog](/blog/2023/02/24/getting-started-with-hertz-performance-testing-guide/)

content/en/blog/news/Introducing CloudWeGo/index.md

@@ -10,7 +10,7 @@ author: <a href="https://github.com/vinijaiswal" target="_blank">Vini Jaiswal</a
 
 ## CloudWeGo Overview
 
-[CloudWeGo](https://www.cloudwego.io/) is a set of microservices middleware developed by ByteDance that can be used to quickly build enterprise-class cloud-native architectures. It is a collection of high-performance, high-extensible, and highly-reliable projects that are focused on microservices communication and governance. It contains many components, including the RPC framework [Kitex](https://github.com/cloudwego/kitex), the HTTP framework [Hertz](https://github.com/cloudwego/hertz), the basic network library Netpoll, inter-process communication library [shmipc](https://github.com/cloudwego/shmipc-go), Rust-based RPC framework [Volo](https://github.com/cloudwego/volo) etc.
+[CloudWeGo](/) is a set of microservices middleware developed by ByteDance that can be used to quickly build enterprise-class cloud-native architectures. It is a collection of high-performance, high-extensible, and highly-reliable projects that are focused on microservices communication and governance. It contains many components, including the RPC framework [Kitex](https://github.com/cloudwego/kitex), the HTTP framework [Hertz](https://github.com/cloudwego/hertz), the basic network library Netpoll, inter-process communication library [shmipc](https://github.com/cloudwego/shmipc-go), Rust-based RPC framework [Volo](https://github.com/cloudwego/volo) etc.
 
 ## CloudWeGo Background
 
@@ -61,7 +61,7 @@ Some of the applications include:
 
 ## Getting Started
 
-To begin your journey with CloudWeGo projects, you can refer to our [comprehensive documentation](https://www.cloudwego.io/docs/), which provides step-by-step instructions. Additionally, we regularly publish insightful blogs on various topics, including the latest innovations in [Kitex](https://github.com/cloudwego/kitex), [Hertz](https://github.com/cloudwego/hertz), [Monoio](https://www.cloudwego.io/blog/2023/04/17/introducing-monoio-a-high-performance-rust-runtime-based-on-io-uring/), [Shmipc](https://github.com/cloudwego/shmipc-go), and [Volo](https://github.com/cloudwego/volo). We also publish best practices blogs and have a dedicated blog that explores best practices for using [Kitex without a proxy](https://www.cncf.io/blog/2023/01/11/kitex-proxyless-practice-traffic-lane-implementation-with-istio-and-opentelemetry/). These resources serve as valuable references to help you make the most of CloudWeGo's offerings and stay up-to-date with the latest developments in the ecosystem.
+To begin your journey with CloudWeGo projects, you can refer to our [comprehensive documentation](/docs/), which provides step-by-step instructions. Additionally, we regularly publish insightful blogs on various topics, including the latest innovations in [Kitex](https://github.com/cloudwego/kitex), [Hertz](https://github.com/cloudwego/hertz), [Monoio](/blog/2023/04/17/introducing-monoio-a-high-performance-rust-runtime-based-on-io-uring/), [Shmipc](https://github.com/cloudwego/shmipc-go), and [Volo](https://github.com/cloudwego/volo). We also publish best practices blogs and have a dedicated blog that explores best practices for using [Kitex without a proxy](https://www.cncf.io/blog/2023/01/11/kitex-proxyless-practice-traffic-lane-implementation-with-istio-and-opentelemetry/). These resources serve as valuable references to help you make the most of CloudWeGo's offerings and stay up-to-date with the latest developments in the ecosystem.
 
 ## Contributing
 

content/en/blog/news/Kitex_Proxyless_OpenTelemetry/index.md

@@ -20,7 +20,7 @@ author: <a href="https://github.com/CoderPoet" target="_blank">CoderPoet</a>, <a
 
 [Kitex][Kitex] is a Golang RPC framework open-sourced by ByteDance that already natively supports the xDS standard protocol and can be managed by Service Mesh in Proxyless way. 
 Refer to this doc for detailed design: [Proposal: Kitex support xDS Protocol](https://github.com/cloudwego/kitex/issues/461). 
-Official doc is also available here at [Kitex/Tutorials/Advanced Feature/xDS Support](https://www.cloudwego.io/docs/kitex/tutorials/advanced-feature/xds/)
+Official doc is also available here at [Kitex/Tutorials/Advanced Feature/xDS Support](/docs/kitex/tutorials/advanced-feature/xds/)
 
 Kitex Proxyless Simply means that Kitex services can interact directly with istiod without envoy sidecar and dynamically obtain service governance rules delivered by the control plane based on the xDS protocol. 
 And those rules will be translated into Kitex corresponding rules to implement some service governance functions (such as traffic routing which is the focus of this blog).

content/en/blog/news/Kitex_performance_testing/index.md

@@ -76,7 +76,7 @@ Later, in order to accommodate the common scenario of open source users, Kitex s
 For RPC frameworks, regardless of service governance, the computation overhead is mainly generated in serialization and deserialization.
 
 Kitex uses the [Go protobuf library](https://github.com/golang/protobuf) to serialize Protobuf.
-And for serialization of Thrift, Kitex has specific performance optimization, which is introduced in the [blog post](https://www.cloudwego.io/blog/2021/09/23/performance-optimization-on-kitex/#serializationdeserialization-optimization-of-thrift) on our official web.
+And for serialization of Thrift, Kitex has specific performance optimization, which is introduced in the [blog post](/blog/2021/09/23/performance-optimization-on-kitex/#serializationdeserialization-optimization-of-thrift) on our official web.
 
 Most of the current open source frameworks support Protobuf in preference, and some built-in Protobuf are actually [gogo/protobuf](https://github.com/gogo/protobuf) versions with performance optimizations.
 However, gogo/protobuf is currently at risk of [maintenance absence](https://github.com/gogo/protobuf/issues/691).
@@ -124,10 +124,10 @@ We also encourage developers to use the testing guide provided in this article,
 
 ## Pertinent Links
 
-- CloudWeGo Official Website: https://www.cloudwego.io
-- Kitex: https://github.com/cloudwego/kitex
-- Netpoll: https://github.com/cloudwego/netpoll
-- kitex-benchmark: https://github.com/cloudwego/kitex-benchmark
-- netpoll-benchmark: https://github.com/cloudwego/netpoll-benchmark
-- Go Protobuf Library: https://github.com/golang/protobuf
-- Thriftgo：https://github.com/cloudwego/thriftgo
+- [CloudWeGo Official Website](/)
+- [Kitex](https://github.com/cloudwego/kitex)
+- [Netpoll](https://github.com/cloudwego/netpoll)
+- [kitex-benchmark](https://github.com/cloudwego/kitex-benchmark)
+- [netpoll-benchmark](https://github.com/cloudwego/netpoll-benchmark)
+- [Go Protobuf Library](https://github.com/golang/protobuf)
+- [Thriftgo](https://github.com/cloudwego/thriftgo)

content/en/blog/news/open_source_announcement/index.md

@@ -42,7 +42,7 @@ Kitex integrates Netpoll, a high-performance network library which offers signif
 
 - Extensibility
 
-Kitex employs a modular design and provides many interfaces with default implementation for users to customize. Users can then extend or inject them into Kitex to fulfill their needs. Please refer to the official [doc](https://www.cloudwego.io/docs/kitex/tutorials/framework-exten/) for the extensibility of Kitex. For their network library, developers can freely choose other network libraries aside from netpoll.
+Kitex employs a modular design and provides many interfaces with default implementation for users to customize. Users can then extend or inject them into Kitex to fulfill their needs. Please refer to the official [doc](/docs/kitex/tutorials/framework-exten/) for the extensibility of Kitex. For their network library, developers can freely choose other network libraries aside from netpoll.
 
 - Multi-message Protocol
 

content/en/blog/news/open_source_volo/index.md

@@ -80,8 +80,8 @@ We hope this article has provided you with a basic understanding of [Volo](https
 
 ### References
 
-- Volo overview: https://github.com/cloudwego/volo
-- Volo Tutorial: https://www.cloudwego.io/docs/volo/
-- Volo Documentation: https://docs.rs/volo
-- Volo-rs organization: https://github.com/volo-rs
+- [Volo overview](https://github.com/cloudwego/volo)
+- [Volo Tutorial](/docs/volo/)
+- [Volo Documentation](https://docs.rs/volo)
+- [Volo-rs organization](https://github.com/volo-rs)
 

content/en/blog/releases/Hertz/release-v050.md

@@ -36,7 +36,7 @@ At the same time, we have added an auxiliary function that can convert with the
 
 The Hertz core library capability has been released, and the specific implementation will be released in the form of [extension package](https://github.com/hertz-contrib/http3/pull/1), welcome to try~
 
-For more detailed design instructions, please refer to: [Hertz supports QUIC & HTTP/3](https://www.cloudwego.io/zh/blog/2023/08/02/hertz-%E6%94%AF%E6%8C%81-quic-http/3/)
+For more detailed design instructions, please refer to: [Hertz supports QUIC & HTTP/3](/zh/blog/2023/08/02/hertz-%E6%94%AF%E6%8C%81-quic-http/3/)
 
 ## Scaffolding tools support generating hertz client code
 

content/en/blog/releases/Kitex/release-v005.md

@@ -11,7 +11,7 @@ description: >
 
 - Add default ErrorHandler to wrap remote error when no ErrorHandler is specified.
 - Backward metainfo is supported.
-- JSON generic call is supported. Usage guide: [link](https://www.cloudwego.io/docs/kitex/tutorials/advanced-feature/generic-call/#4-json-mapping-generic-call).
+- JSON generic call is supported. Usage guide: [link](/docs/kitex/tutorials/advanced-feature/generic-call/#4-json-mapping-generic-call).
 
 ## Improvement:
 
@@ -35,7 +35,7 @@ description: >
 ## Docs:
 
 - English is available for README and all other documents.
-- Guide for generic call. [English](https://www.cloudwego.io/docs/kitex/tutorials/advanced-feature/generic-call) | [中文](https://www.cloudwego.io/zh/docs/kitex/tutorials/advanced-feature/generic-call/)
+- Guide for generic call. [English](/docs/kitex/tutorials/advanced-feature/generic-call) | [中文](/zh/docs/kitex/tutorials/advanced-feature/generic-call/)
 - Landscape and Roadmap in README.
 
 ## Dependency Change:

content/en/blog/releases/Kitex/release-v040.md

@@ -9,10 +9,10 @@ description: >
 ## **Introduction to Key Changes**
 
 ### **Feature**
-1. **Retry enhancement**: Support user-defined result retry; Support request-level configuration (priority is higher than Neptune). See [retry guide](https://www.cloudwego.io/docs/kitex/tutorials/service-governance/retry/) for details
-2. **Frugal (Thrift)**: Support default value of IDL; No codec code is supported by using frugal. See [frugal](https://www.cloudwego.io/docs/kitex/tutorials/advanced-feature/codec_frugal/) for details
-3. **Tool-Protobuf**: Support depend on external libraries with go_package, see [Notes for Using Protobuf IDLs](https://www.cloudwego.io/docs/kitex/tutorials/code-gen/code_generation/#notes-for-using-protobuf-idls);  Support Guess IDL type from the file extension, it is unnecessary to specify the type param when generating the protobuf code
-4. **Fastpb(protobuf)**: Support fastpb to optimize performance of protobuf, and it is integrated into Kite by default. See [fastpb](https://www.cloudwego.io/docs/kitex/tutorials/code-gen/fastpb/) for details
+1. **Retry enhancement**: Support user-defined result retry; Support request-level configuration (priority is higher than Neptune). See [retry guide](/docs/kitex/tutorials/service-governance/retry/) for details
+2. **Frugal (Thrift)**: Support default value of IDL; No codec code is supported by using frugal. See [frugal](/docs/kitex/tutorials/advanced-feature/codec_frugal/) for details
+3. **Tool-Protobuf**: Support depend on external libraries with go_package, see [Notes for Using Protobuf IDLs](/docs/kitex/tutorials/code-gen/code_generation/#notes-for-using-protobuf-idls);  Support Guess IDL type from the file extension, it is unnecessary to specify the type param when generating the protobuf code
+4. **Fastpb(protobuf)**: Support fastpb to optimize performance of protobuf, and it is integrated into Kite by default. See [fastpb](/docs/kitex/tutorials/code-gen/fastpb/) for details
 5. **Generic Call**: Support HTTP+Protobuf generic call
 6. **Kitex lib supports Windows**: You can use kitex running on Windows (Kitex tool still doesn't support)
 
@@ -28,7 +28,7 @@ description: >
 
 ### Feature
 
-* [[#571](https://github.com/cloudwego/kitex/pull/571)] feat(protobuf): integrate [fastpb](https://github.com/cloudwego/fastpb) into kitex, refer to [doc](https://www.cloudwego.io/docs/kitex/tutorials/code-gen/fastpb/).
+* [[#571](https://github.com/cloudwego/kitex/pull/571)] feat(protobuf): integrate [fastpb](https://github.com/cloudwego/fastpb) into kitex, refer to [doc](/docs/kitex/tutorials/code-gen/fastpb/).
 * [[#592](https://github.com/cloudwego/kitex/pull/592)] feat(generic): add default value defined in thrift idl for HTTP/Map/JSON generic call.
 * [[#600](https://github.com/cloudwego/kitex/pull/600)] feat(thrift): support no codec gen-code when using frugal.
 * [[#607](https://github.com/cloudwego/kitex/pull/607), [#610](https://github.com/cloudwego/kitex/pull/610)] feat(proxyless): add option for xDS extension. Support traffic route, timeout config and service discovery based on xDS.