From 1191897fa15fb92f0d43070208bbb039be51fefa Mon Sep 17 00:00:00 2001 From: Guangming Luo Date: Mon, 25 Mar 2024 19:21:08 +0800 Subject: [PATCH] chore: use permanent link for discord (#1048) --- config.toml | 2 +- content/en/_index.html | 2 +- ...ing_Performance_in_Microservice_Architecture_with_Kitex.md | 2 +- content/en/blog/news/Hertz_Open_Source/index.md | 2 +- content/en/blog/news/Introducing CloudWeGo/index.md | 2 +- content/en/community/_index.md | 2 +- content/zh/_index.html | 2 +- content/zh/community/overview/_index.html | 4 ++-- 8 files changed, 9 insertions(+), 9 deletions(-) diff --git a/config.toml b/config.toml index 973ef58749..73a85839b2 100644 --- a/config.toml +++ b/config.toml @@ -205,7 +205,7 @@ desc = "Development takes place here!" [[params.links.developer]] name = "Discord" -url = "https://discord.gg/UX7MPbh7" +url = "https://discord.gg/jceZSE7DsW" icon = "fab fa-discord" desc = "Chat with other project developers" diff --git a/content/en/_index.html b/content/en/_index.html index d9911f648b..0d2ba32254 100644 --- a/content/en/_index.html +++ b/content/en/_index.html @@ -223,7 +223,7 @@

Enterprise Users

Contact Us
diff --git a/content/en/blog/news/Enhancing_Performance_in_Microservice_Architecture_with_Kitex/Enhancing_Performance_in_Microservice_Architecture_with_Kitex.md b/content/en/blog/news/Enhancing_Performance_in_Microservice_Architecture_with_Kitex/Enhancing_Performance_in_Microservice_Architecture_with_Kitex.md index 7563d3024e..08b549d47d 100644 --- a/content/en/blog/news/Enhancing_Performance_in_Microservice_Architecture_with_Kitex/Enhancing_Performance_in_Microservice_Architecture_with_Kitex.md +++ b/content/en/blog/news/Enhancing_Performance_in_Microservice_Architecture_with_Kitex/Enhancing_Performance_in_Microservice_Architecture_with_Kitex.md @@ -543,4 +543,4 @@ Kitex has demonstrated its ability to outperform other frameworks in testing com We also briefly looked towards future optimizations, including kernel-level improvements, restructuring the TCP protocols, and further refinement of existing components. With continuous learning and improvements, we are driven to unlock the vast potential in microservice performance optimization, taking us one step closer to the realm of real-time computing. -For any questions or discussions, you're welcome to join our community on [GitHub](https://github.com/cloudwego) or [Discord](https://discord.gg/UX7MPbh7). +For any questions or discussions, you're welcome to join our community on [GitHub](https://github.com/cloudwego) or [Discord](https://discord.gg/jceZSE7DsW). diff --git a/content/en/blog/news/Hertz_Open_Source/index.md b/content/en/blog/news/Hertz_Open_Source/index.md index d4c3449d8b..2699380541 100644 --- a/content/en/blog/news/Hertz_Open_Source/index.md +++ b/content/en/blog/news/Hertz_Open_Source/index.md @@ -59,7 +59,7 @@ As mentioned earlier, Hertz has currently open sourced only the internally verif - **Enhanced ecosystem support**: Since Hertz does not adopt go net's data structure, additional ecosystem support is required. In the initial batch of open source releases, we have included CORS, Trace, and Metrics. In the future, we plan to support additional aspects such as reverse proxy and Session. - **Iteration based on user feedback**: Following the project's open sourcing, we will iterate based on developer feedback and requirements. -We welcome everyone to [contribute](https://github.com/cloudwego/hertz/blob/develop/CONTRIBUTING.md) by submitting issues and PRs to [Hertz](https://github.com/cloudwego/hertz), fostering collaborative development. We eagerly anticipate the involvement of more developers and anticipate Hertz aiding enterprises in swiftly constructing cloud-native architectures. Enterprise users are invited to migrate and utilize Hertz, and we will provide dedicated technical support and communication. Feel free to [join our Discord community](https://discord.gg/UX7MPbh7) for further consultations and assistance. +We welcome everyone to [contribute](https://github.com/cloudwego/hertz/blob/develop/CONTRIBUTING.md) by submitting issues and PRs to [Hertz](https://github.com/cloudwego/hertz), fostering collaborative development. We eagerly anticipate the involvement of more developers and anticipate Hertz aiding enterprises in swiftly constructing cloud-native architectures. Enterprise users are invited to migrate and utilize Hertz, and we will provide dedicated technical support and communication. Feel free to [join our Discord community](https://discord.gg/jceZSE7DsW) for further consultations and assistance. ## Related Links - Project [address](https://github.com/cloudwego/hertz) diff --git a/content/en/blog/news/Introducing CloudWeGo/index.md b/content/en/blog/news/Introducing CloudWeGo/index.md index c2a794177b..11e28ed095 100644 --- a/content/en/blog/news/Introducing CloudWeGo/index.md +++ b/content/en/blog/news/Introducing CloudWeGo/index.md @@ -78,7 +78,7 @@ Kitex is equipped with built-in governance strategies and expansion interfaces f We welcome you to [contribute](https://github.com/cloudwego/community/blob/main/CONTRIBUTING.md) by submitting issues and PRs to build CloudWeGo together. Contributing to CloudWeGo involves various roles and responsibilities within the project's GitHub organization. The roles include Member, Committer, Reviewer, Approver, and Maintainer. Members are active contributors in the community and are expected to participate in discussions and make multiple contributions to the project. Committers are active code contributors and play a role in reviewing and approving code contributions. Reviewers have expertise in the codebase and provide feedback on contributions. Approvers review and approve code contributions, ensuring their holistic acceptance. Maintainers are responsible for setting technical direction, making design decisions, and ensuring the overall health of a subproject. The responsibilities and privileges of each role vary, but they all contribute to the growth and success of CloudWeGo. The responsibilities of contributor roles in CloudWeGo are outlined in our [community membership document](https://github.com/cloudwego/community/blob/main/COMMUNITY_MEMBERSHIP.md). -We are excited for more developers to join, and also look forward to CloudWeGo helping more and more companies quickly build cloud-native architectures. Feel free to raise an issue in [Github](https://github.com/cloudwego) if you have any questions. Furthermore, you can join our [Discord](https://discord.gg/UX7MPbh7) to keep updated with the latest news. +We are excited for more developers to join, and also look forward to CloudWeGo helping more and more companies quickly build cloud-native architectures. Feel free to raise an issue in [Github](https://github.com/cloudwego) if you have any questions. Furthermore, you can join our [Discord](https://discord.gg/jceZSE7DsW) to keep updated with the latest news. ## Community and Support diff --git a/content/en/community/_index.md b/content/en/community/_index.md index 1bdf573003..4d5c1c6a55 100644 --- a/content/en/community/_index.md +++ b/content/en/community/_index.md @@ -34,7 +34,7 @@ You may participate in the community through GitHub, or simply by interacting wi Discord: diff --git a/content/zh/_index.html b/content/zh/_index.html index 71777e020f..dc78157143 100644 --- a/content/zh/_index.html +++ b/content/zh/_index.html @@ -266,7 +266,7 @@

谁在用

联系我们
diff --git a/content/zh/community/overview/_index.html b/content/zh/community/overview/_index.html index 41a298fbd6..3c6afd0083 100644 --- a/content/zh/community/overview/_index.html +++ b/content/zh/community/overview/_index.html @@ -123,10 +123,10 @@

讨论

关于项目的 issue 和pr 请在这里提交

- + Discord - Discord ▶ + Discord ▶

更适合海外同学参与社区