You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by ju...@apache.org on 2021/10/06 03:31:40 UTC

[apisix-website] branch master updated: docs: add Draft Property to newly added blogs (#637)

This is an automated email from the ASF dual-hosted git repository.

juzhiyuan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-website.git


The following commit(s) were added to refs/heads/master by this push:
     new 7b77f0e  docs: add Draft Property to newly added blogs (#637)
7b77f0e is described below

commit 7b77f0ed3044f0610d45a4cd873775cd15da0646
Author: Kishani Kandasamy <53...@users.noreply.github.com>
AuthorDate: Wed Oct 6 09:01:35 2021 +0530

    docs: add Draft Property to newly added blogs (#637)
---
 .../blog/2021-06-29-release-apache-apisix-2.7.md   |  61 ---------
 .../blog/2021-07-28-release-apache-apisix-2.8.md   | 152 ---------------------
 ...ors-the-golden-metric-of-openSource-projects.md |  94 -------------
 website/blog/2021-09-30-weekly-report.md           |   1 +
 website/blog/2021-10-01-openEuler.md               |   1 +
 .../2021-06-29-release-apache-apisix-2.7-en.md     |  61 ---------
 .../2021-07-28-release-apache-apisix-2.8-en.md     | 151 --------------------
 ...-the-golden-metric-of-openSource-projects-en.md |  97 -------------
 .../2021-09-29-release-apache-apisix-2.10.md       |   0
 .../2021-09-30-weekly-report.md                    |   0
 .../2021-10-01-openEuler.md                        |   0
 11 files changed, 2 insertions(+), 616 deletions(-)

diff --git a/website/blog/2021-06-29-release-apache-apisix-2.7.md b/website/blog/2021-06-29-release-apache-apisix-2.7.md
deleted file mode 100644
index 18a8e11..0000000
--- a/website/blog/2021-06-29-release-apache-apisix-2.7.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: "Apache APISIX 2.7.0-Release 正式发布"
-author: "罗泽轩"
-authorURL: "https://github.com/spacewander"
-authorImageURL: "https://avatars.githubusercontent.com/u/4161644?v=4"
-keywords:
-- Apache APISIX
-- Release Notes
-Description: Apache APISIX 2.7.0-Release 正式发布!
-tags: [Release]
-draft: true
----
-
-> Apache APISIX 2.7.0-Release 正式发布!
-
-<!--truncate-->
-
-Apache APISIX 2.7.0-Release 正式发布!欢迎大家下载使用。
-
-这个版本支持了多语言插件、增强了四层 TCP 代理、增强了 Nginx 功能,有 20+ 开发者参与,共提交了 70+ PR,下面是重点功能的介绍。
-
-## Release Notes
-
-### 多语言插件
-
-随着 apisix-java-plugin-runner 发布第一个版本,外加 apisix-go-plugin-runner 完成主体功能,APISIX 的多语言插件功能已经支持两大最广泛使用的后端编程语言。如果你还担忧 APISIX 的插件开发会受限于 Lua 生态,不妨试试使用我们的多语言 plugin runner 来开发 Java / Go 插件。
-
-### 增强四层 TCP 代理
-
-2.7 版本中,我们开发了 TCP 代理新功能,包括:
-
-* 允许 upstream 中配置域名
-* 允许 mqtt-proxy 插件配置域名
-* 支持接收 TLS over TCP 连接,这一块的证书自然是可以像 HTTPS 的证书一样动态配置的
-* 基于 SNI 的路由规则
-* 动态校验客户端证书
-
-在后续版本中,我们也会继续分配部分资源来完善现有的 TCP 代理功能,敬请期待!
-
-### 增强 Nginx 功能
-
-我们希望能够动态设置越来越多的 Nginx 配置,所以我们添加自己的补丁和 Nginx C 模块,增强原生 Nginx 的功能。
-
-目前包含了以下新功能:
-
-* 动态设置 mTLS
-* 动态设置 client_max_body_size
-
-在 APISIX 后续版本中,我们也会陆续允许下面的 Nginx 配置能够被动态设置:
-
-* upstream 的 keepalive
-* gzip
-* real_ip
-* proxy_max_temp_file_size
-
-## 下载
-
-下载 Apache APISIX 2.7.0-Release
-
-* 源代码:请访问[下载页面](https://apisix.apache.org/downloads/)
-* 二进制安装包:请访问[安装指南](https://apisix.apache.org/zh/docs/apisix/how-to-build/)
diff --git a/website/blog/2021-07-28-release-apache-apisix-2.8.md b/website/blog/2021-07-28-release-apache-apisix-2.8.md
deleted file mode 100644
index 6013243..0000000
--- a/website/blog/2021-07-28-release-apache-apisix-2.8.md
+++ /dev/null
@@ -1,152 +0,0 @@
----
-title: "Apache APISIX 2.8 正式发布,带来更多新功能!"
-author: "罗泽轩"
-authorURL: "https://github.com/spacewander"
-authorImageURL: "https://avatars.githubusercontent.com/u/4161644?v=4"
-keywords:
-- APISIX
-- Release Notes
-- Apache APISIX 
-description: Apache APISIX 2.8 版本正式发布!
-tags: [Release]
-draft: true
----
-
-> Apache APISIX 2.8 版本正式发布!
-
-<!--truncate-->
-
-Apache APISIX 2.8 版本正式发布!🎉 这个版本有 30+ 开发者参与,共提交了 100+ PR,支持了 **1 个新功能、1 个新体验、2 个新插件、2 个新玩法**,快去阅读了解 2.8 版本的新特性吧!
-
-👇👇👇
-
-## Release Notes
-
-### 新功能:独立的 Keepalive 连接池
-
-从[2.7 版本](https://apisix.apache.org/blog/2021/06/29/release-apache-apisix-2.7)开始添加 Apache APISIX 自己的补丁和 Nginx C 模块,增强原生 Nginx 的功能,希望能够动态设置越来越多的 Nginx 配置。在发布的最新版本中,Apache APISIX 已经支持在 Upstream 级别上配置独立的 Keepalive 连接池。
-
-目前包含了以下功能:
-
-- 动态设置 mTLS
-- 动态设置 client_max_body_size
-- Upstream 的 keepalive(2.8 新功能)
-- gzip (2.8 新插件)
-
-在 Apache APISIX 后续版本中,我们也会陆续允许下面的 Nginx 配置能够被动态设置:
-
-- real_ip
-- proxy_max_temp_file_size
-- ……
-
-Upstream 的配置举例:
-
-```JSON
-{
-    "id": "backend",
-    "nodes": {"host:80": 100},
-    "type":"roundrobin",
-    "keepalive_pool": {
-        "size": 4,
-        "idle_timeout": 8,
-        "requests": 16
-    }
-}
-```
-
-### 新体验:stream 代理功能增强
-
-在 2.8 版本中,把 [ip-restriction](http://apisix.apache.org/docs/apisix/plugins/ip-restriction/) 和 [limit-conn](http://apisix.apache.org/docs/apisix/plugins/limit-conn/) 两个插件从 HTTP 部分的移植到了 stream 部分,这么做的好处是丰富网关在 stream 代理的功能,增加对上游服务的安全性保障。
-
-ip-restriction 可以用来做 IP 黑白名单过滤,保证只有来自特定 IP 的请求才能访问到后端服务。
-
-limit-conn 可以用来限制特定路由上同时存在的连接个数,限制客户端的并发访问量。
-
-### 新插件:gzip 插件
-
-2.8 版本中新增了 gzip 插件,使用 gzip 插件可以**动态设置路由级别的 gzip 参数**。
-
-gzip 配置举例:
-
-```JSON
-{
-    "plugins": {
-        "gzip": {
-            "min_length": 20,
-            "http_version": 1.1,
-            "buffers": {
-                "number": 32,
-                "size": 4096
-            },
-            "types": [
-                "text/html"
-            ],
-            "comp_level": 1,
-            "vary": false
-        }
-    }
-}
-```
-
-### 新插件:ua-restriction
-
-`ua-restriction` 插件用于校验 User-Agent 是否处于黑白名单中,黑白名单是一个非常常见的需求,现在可以通过插件的方式启用了。
-
-`ua-restriction` 配置举例:
-
-```JSON
-{
-    "plugins": {
-        "ua-restriction": {
-            "denylist": [
-                "my-bot1",
-                "(Baiduspider)/(\\d+)\\.(\\d+)"
-            ]
-        }
-    }
-}
-```
-
-### 新玩法:支持通过插件的方式执行特定逻辑
-
-得益于 Apache APISIX 架构,许多功能都是通过插件的方式实现的。从 2.8 版本开始,插件又添加了新玩法。**现在 Apache APISIX 支持在选择上游节点之后,通过插件的方式执行特定逻辑。**  
-
-只需要在插件里定义下面的方法:
-
-```Lua
-function _M.balancer(conf, ctx)
-    core.log.notice("IP: ", ctx.balancer_ip, ", Port: ", ctx.balancer_port)
-end
-```
-
-在这个示例里,日志会输出上游的 IP 和 Port。
-
-**什么场景下会运行上述方法?**
-
-1. 选择上游节点之后,访问上游之前
-2. 每次重试之前
-
-出于性能考虑,上述方法首次运行在 OpenResty 的 access 阶段(实际上 APISIX 在 access 阶段就选好了上游节点),该方法并不与 OpenResty 的同名阶段重合。
-
-### 新玩法:支持自定义 balancer
-
-从 2.8 版本开始,用户可以自定义 balancer。**这里的 balancer,是指最少连接数、轮询、一致性哈希等负载均衡器。**
-
-虽然 Apache APISIX 已经提供了丰富的 balancer,但是用户可能需要用的 balancer 是和业务紧密相关的 balancer,比如:需要考虑机房、可用区等等。支持自定义 balancer,用户可以编写自己的 balancer,并通过 `require("apisix.balancer.your_balancer")`  加载到程序中。
-
-通常自定义的 balancer 需要 node 提供 host/port 以外的数据,可以把数据放到 metadata 里面,举个例子:
-
-```JSON
-{
-    "nodes": [
-        { "host": "0.0.0.0", "port": 1980, "weight": 1, "metadata": {"b": 1} }
-    ]
-}
-```
-
-## 下载
-
-下载 Apache APISIX 2.8
-
-- 源代码:请访问[下载页面](https://apisix.apache.org/downloads/)
-- 二进制安装包:请访问[安装指南](https://apisix.apache.org/zh/docs/apisix/how-to-build/)
diff --git a/website/blog/2021-08-14-contributors-the-golden-metric-of-openSource-projects.md b/website/blog/2021-08-14-contributors-the-golden-metric-of-openSource-projects.md
deleted file mode 100644
index 6512d74..0000000
--- a/website/blog/2021-08-14-contributors-the-golden-metric-of-openSource-projects.md
+++ /dev/null
@@ -1,94 +0,0 @@
----
-title: "贡献者,是衡量开源项目的金指标"
-author: "吴舒旸"
-authorURL: "https://github.com/Yiyiyimu"
-authorImageURL: "https://avatars.githubusercontent.com/u/34589752?v=4"
-keywords:
-- API 网关
-- APISIX
-- Apache APISIX
-- 贡献者图表
-- 开源项目
-description: 本文讲述了为什么贡献者数量变化是衡量开源项目的金指标。虽然 GitHub 已有的指标数量很多,例如 Star 数、Issue 数量和 PR 数量,但是这些指标都不能直观地反映出一个开源项目在一段时间内的变化趋势和活跃度。所以笔者 Yiyiyimu 提出了新的指标:贡献者增长和月度活跃贡献者,并创造了一款开源工具,其名为“献者图表”,方便 GitHub 用户使用这些指标来确认项目的活跃度。目前,多个开源项目已经在使用贡献者图表。
-tags: [Community]
-draft: true
----
-
-> 根据 GitHub 2020 年的统计显示,这一年新增了 6000 万个代码仓库,超过 5600 万的开发者参与到开源项目中。预计到 2025 年,在 GitHub 参与开源项目的开发者人数将会超过 1 亿。
-
-<!--truncate-->
-
-> Source:
-> https://github.com/api7/contributor-graph
-
-在这些快速增长的数字背后,隐藏的是开源项目为了赢得开发者而做出的各种宣传:硬核技术文章、社交活动、新媒体、周边礼物等,可以说是乱花渐欲迷人眼。那么对于开发者来说,如何能够在百花齐放的项目中,找出最适合自己公司的那一个呢?
-
-这就会涉及到开源项目的各种指标:
-
-- Star 数:这是最直接的指标,它代表的是这个项目吸引了多少开发者的关注,可以体现这个项目的 marketing 水平。如果这个项目有商业公司资金的支持、强力的 PR 团队,或者是水军刷 Star,那么这个指标就很容易失真;
-
-- Issue 和 PR 数:GitHub 提供了 Insights 功能,如下图所示:
-
-![Apache APISIX GitHub Insights](../static/img/blog_img/2021-08-14-1.webp)
-
-可以选择最近一周、最近一个月的时间内,这个开源项目的 Issue 和 PR 的新建和关闭数。上图是 Apache APISIX 最近一个月的数据。
-
-GitHub insights 提供了一个非常棒的开发者视角,但还不够完美:Issue 和 PR 的质量如何?这些是没有办法量化的;
-
-- Commit 频率和数据:下图是 Apache APISIX 从项目创建到现在的 Commit 频率统计,可以看出 Apache APISIX 保持了非常稳定和持续的开发,但这个指标也略显单薄:看不到提交这些 Commit 的开发者的数据;
-
-![Apache APISIX commits](../static/img/blog_img/2021-08-14-2.webp)
-
-看到这里,你是不是觉得选择一个开源项目好复杂,看了这么多指标都得不出答案。有没有一个“金指标”,一个通过 marketing 砸不出来的指标?一个能够体现“开发者为核心”的指标?
-
-作为开源项目的维护者和开发者,我们也需要这样的金指标来指引我们。所以,我们提出了 “贡献者增长” 和 “活跃贡献者”这两个维度,并将统计和分析的过程开源出来:https://github.com/api7/contributor-graph,你也可以通过 https://www.apiseven.com/zh/contributor-graph 直接进行检索。下面是 Apache APISIX 的示例:
-
-## 贡献者增长
-
-![Apache APISIX contributor growth](../static/img/blog_img/2021-08-14-3.webp)
-
-## 月度活跃贡献者
-
-![Apache APISIX Monthly Active Contributors](../static/img/blog_img/2021-08-14-4.webp)
-
-通过上面两个表格,你可以清晰的看到 Apache APISIX 从创办至今,贡献者都保持着稳定的增长,每个月都有 25 个左右的代码贡献者参与其中。
-
-## 多仓库对比
-
-“贡献者增长” 和 “活跃贡献者”图表都支持在多仓库之间比较。更重要的是,我们会拉取 Github API 每日/每月定时更新图表,只要一次性的复制使用我们提供的链接,您的仓库就可以始终显示实时的贡献者数据。
-
-贡献者增长曲线的数据来源是项目每个 contributor 首次提交 commit 的日期。通过贡献者增长曲线,我们可以在 Github 首页显示的贡献者总人数基础上观察贡献者增长情况,从而对社区的发展情况作出直观判断。
-
-通过同时展示同一领域中的多个仓库,我们也可以直观比较不同社区的发展情况。
-
-![Apache APISIX compare the development of different communities](../static/img/blog_img/2021-08-14-5.webp)
-
-在上图中,我们可以看到 Apache APISIX 的贡献者人数以非常快的速度增长,仅仅用了两年时间,贡献者人数就基本赶上甚至超越了其他开源网关项目。
-
-月度贡献者曲线数据则来自于每月提交 commit 的贡献者数量。
-
-相比贡献者增长曲线,月度贡献者可以更好衡量短时间内的社区发展情况。
-
-![Apache APISIX monthly contributors compare](../static/img/blog_img/2021-08-14-6.webp)
-
-例如在上图中,我们可以看到如今 Apache APISIX 是多个开源网关项目中的月度贡献者人数最多、最稳定的。
-
-这也解释了为何 Apache APISIX 可以在开源后如此短的时间内在总贡献者人数上赶上友商们。
-
-![Apache APISIX monthly contributors](../static/img/blog_img/2021-08-14-7.webp)
-
-上面这张比较开源消息中间件社区的月度贡献者的图,曾在推特引发热议。
-
-通过这张图,我们可以看到 Apache Pulsar 在月度贡献者上迎头赶上了 Apache Kafka。
-
-## 总结
-
-目前贡献者图表已经在 Apache APISIX 、Apache Skywalking、Apache DolphinScheduler、Apache Openwhisk、Apache ShardingSphere、awesome-docker、TiDB docs-dm 等多个开源项目中使用。
-
-在用户使用并反馈的过程中,我们实现了更多的需求,比如添加“匿名”贡献者,或是项目由 SVN 迁至 GitHub 后添加 SVN 侧的贡献者等。
-
-好程序都是起源于程序员要解决的切身之痛。当我们聊 Contributor Graph 时,我们不仅希望借助这个工具生产更加直观的展示 Apache APISIX 社区活跃度的图表,我们同时开源了这个小工具,希望这个工具可以帮助到其他的开源项目。
-
-欢迎大家使用贡献者趋势图表来跟踪您的社区活跃度,任何需求和问题都欢迎到 Contributor Graph 的 GitHub 仓库中反馈。
-
-访问 Contributor Graph [repository](https://github.com/api7/contributor-graph)。
diff --git a/website/blog/2021-09-30-weekly-report.md b/website/blog/2021-09-30-weekly-report.md
index d947572..dd699b9 100644
--- a/website/blog/2021-09-30-weekly-report.md
+++ b/website/blog/2021-09-30-weekly-report.md
@@ -8,6 +8,7 @@ keywords:
 - 贡献者
 description: “独行者速,众行者远”。Apache APISIX 社区周报希望可以帮助社区小伙伴们更好地掌握 Apache APISIX 社区的每周进展,方便大家参与到 Apache APISIX 社区中来。
 tags: [Events]
+draft: true
 ---
 > 从 9.13 到 9.30, 有 32 位开发者为 Apache APISIX 提交了 93 个 commits。感谢这些小伙伴为 Apache APISIX 添砖加瓦,是你们的无私付出,让 Apache APISIX 项目变得更好!
 <!--truncate-->
diff --git a/website/blog/2021-10-01-openEuler.md b/website/blog/2021-10-01-openEuler.md
index 472ca08..39aa206 100644
--- a/website/blog/2021-10-01-openEuler.md
+++ b/website/blog/2021-10-01-openEuler.md
@@ -9,6 +9,7 @@ keywords:
 - 欧拉
 description: 来自 Apache APISIX 社区的罗泽轩和温铭在 openEuler 9 月 30 日发布的第一个社区创新版( openEuler 21.09)中,为 OpenResty 迁移工作中做了非常多的贡献,让 OpenResty 可以在欧拉开源操作系统上平稳高效的运行。
 tags: [Events]
+draft: true
 ---
 > 来自 Apache APISIX 社区的[罗泽轩](https://github.com/spacewander)和[温铭](https://github.com/moonming)在 openEuler 9 月 30 日发布的第一个社区创新版( [openEuler 21.09](https://openeuler.org/) )中,为 [OpenResty](https://github.com/openresty/openresty) 迁移工作中做了非常多的贡献,让 OpenResty 可以在欧拉开源操作系统上平稳高效的运行。OpenResty 的稳定运行也意味着 [Apache APISIX](https://github.com/apache/apisix) 可以顺畅地运行在 openEuler 系统上,Apache APISIX 底层基于 OpenResty 做了一定开发。
 <!--truncate-->
diff --git a/website/i18n/zh/docusaurus-plugin-content-blog/2021-06-29-release-apache-apisix-2.7-en.md b/website/i18n/zh/docusaurus-plugin-content-blog/2021-06-29-release-apache-apisix-2.7-en.md
deleted file mode 100644
index bb52f7d..0000000
--- a/website/i18n/zh/docusaurus-plugin-content-blog/2021-06-29-release-apache-apisix-2.7-en.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: "Release Apache APISIX 2.7.0"
-author: "Ruofei Zhao"
-authorURL: "https://github.com/Serendipity96"
-authorImageURL: "https://avatars.githubusercontent.com/u/23514812?v=4"
-keywords:
-- Apache APISIX
-- Release Notes
-Description: Apache APISIX 2.7.0 has been released!
-tags: [Release]
-draft: true
----
-
-> Apache APISIX 2.7.0 has been released!
-
-<!--truncate-->
-
-Apache APISIX 2.7.0 has been released! Welcome to download and use it.
-
-This version supports multi-language plugins, enhances the four-layer TCP proxy and Nginx configuration. More than 20 developers participated, and 70 plus pull requests have been submitted. The following is an introduction to the key features.
-
-## Release Notes
-
-### Multi-language plugin
-
-With the release of the first version of apisix-java-plugin-runner, and apisix-go-plugin-runner completes its main functions, the multi-language plugin of Apache APISIX supports the two most widely used back-end programming languages. If you are still worried that the development of Apache APISIX plugin will be limited to Lua ecosystem, please try our multi-language plugin runner to develop Java / Go plugins.
-
-### Enhanced four-layer TCP proxy
-
-In version 2.7, we have developed new features of TCP proxy, including:
-
-- Allow domain name configuration in upstream
-- Allow mqtt-proxy plugin to configure domain name
-- Support for receiving TLS over TCP connections, the certificate of which can be dynamically configured just like HTTPS certificate
-- SNI-based route rules
-- Dynamic verification of client certificates
-
-In future releases, we will continue to improve TCP proxy, so stay tuned!
-
-### Enhanced Nginx configuration
-
-We hope to dynamically set more and more Nginx configurations, so we add our own patches and Nginx C modules to enhance the native Nginx.
-
-The following new features are currently included:
-
-- Dynamically set mTLS
-- Dynamically set client_max_body_size
-
-In future releases, we will continue to allow the following Nginx configurations to be set dynamically:
-
-- upstream keepalive
-- gzip
-- real_ip
-- proxy_max_temp_file_size
-
-## Download
-
-Download Apache APISIX 2.7.0-Release
-
-- Source code: please visit [download page](https://apisix.apache.org/downloads/)
-- Binary installation package: please visit [Installation Guide](https://apisix.apache.org/zh/docs/apisix/how-to-build/)
diff --git a/website/i18n/zh/docusaurus-plugin-content-blog/2021-07-28-release-apache-apisix-2.8-en.md b/website/i18n/zh/docusaurus-plugin-content-blog/2021-07-28-release-apache-apisix-2.8-en.md
deleted file mode 100644
index b9007f2..0000000
--- a/website/i18n/zh/docusaurus-plugin-content-blog/2021-07-28-release-apache-apisix-2.8-en.md
+++ /dev/null
@@ -1,151 +0,0 @@
----
-title: "Release Apache APISIX 2.8.0"
-author: "Ruofei Zhao"
-authorURL: "https://github.com/Serendipity96"
-authorImageURL: "https://avatars.githubusercontent.com/u/23514812?v=4"
-keywords:
-- APISIX
-- Release Notes
-- Apache APISIX 
-description: Apache APISIX version 2.8 is released!
-tags: [Release]
-draft: true
----
-
-> Apache APISIX version 2.8 is released!
-
-<!--truncate-->
-
-Apache APISIX version 2.8 is released! 🎉 This version has 30+ developers participated, more than 100 PRs had been submitted, and supports **1 new feature, 1 new experience, 2 new plugins, and 2 new ways to develop**. Read and learn about the new features in version 2.8!
-👇👇👇
-
-## Release Notes
-
-### New feature: Independent Keepalive connection pool
-
-Starting with [version 2.7](https://apisix.apache.org/blog/2021/06/29/release-apache-apisix-2.7), we have added Apache APISIX's own patches and the Nginx C module to enhance the native Nginx, allowing dynamic setup of increasing number of Nginx configurations. In version 2.8, Apache APISIX supports the configuration of independent Keepalive connection pools at the Upstream level.
-
-The following features are currently included:
-
-- Dynamically set mTLS
-- Dynamically set client_max_body_size
-- Upstream Keepalive (2.8 new feature)
-- gzip (2.8 new Plug-in)
-
-In future releases, we will continue to allow the following Nginx configurations to be set dynamically:
-
-- real_ip
-- proxy_max_temp_file_size
-- ……
-
-An example of Upstream configuration:
-
-```JSON
-{
-    "id": "backend",
-    "nodes": {"host:80": 100},
-    "type":"roundrobin",
-    "keepalive_pool": {
-        "size": 4,
-        "idle_timeout": 8,
-        "requests": 16
-    }
-}
-```
-
-### New experience: Enhance stream proxy
-
-In version 2.8, the [ip-restriction](http://apisix.apache.org/docs/apisix/plugins/ip-restriction/) and [limit-conn](http://apisix.apache.org/docs /apisix/plugins/limit-conn/) had been duplicated from the HTTP section to the stream section. The benefit of this way is to enhance gateway capabilities in the stream proxy and to increase the security of the upstream services.
-
-ip-restriction can be used to filter IP black and white list to ensure that only requests from a specific IP can access the backend service.
-
-limit-conn can be used to limit the number of simultaneous connections on a route, limiting the number of concurrent client accesses.
-
-### New plug-in: gzip
-
-Apache APISIX version 2.8 contains the gzip plug-in. Using the gzip plug-in, you can **dynamically set route-level gzip parameters**.
-
-An example of gzip configuration:
-
-```JSON
-{
-    "plugins": {
-        "gzip": {
-            "min_length": 20,
-            "http_version": 1.1,
-            "buffers": {
-                "number": 32,
-                "size": 4096
-            },
-            "types": [
-                "text/html"
-            ],
-            "comp_level": 1,
-            "vary": false
-        }
-    }
-}
-```
-
-### New plug-in: ua-restriction
-
-The `ua-restriction` plugin is used to check if the User-Agent is in the black and white list, which is a very common requirement and can be enabled by way of a plugin.
-
-An example of `ua-restriction` configuration:
-
-```JSON
-{
-    "plugins": {
-        "ua-restriction": {
-            "denylist": [
-                "my-bot1",
-                "(Baiduspider)/(\\d+)\\.(\\d+)"
-            ]
-        }
-    }
-}
-```
-
-### New way to develop: Support for executing specific logic by plug-ins
-
-Based on Apache APISIX architecture, many features are implemented by plug-ins. Starting from version 2.8, **Apache APISIX supports executing specific logic by plug-ins after selecting an upstream node.**
-
-Define the following method in the plug-in:
-
-```Lua
-function _M.balancer(conf, ctx)
-    core.log.notice("IP: ", ctx.balancer_ip, ", Port: ", ctx.balancer_port)
-end
-```
-
-In this example, the log will output the IP and Port of the upstream.
-
-**Which scenario does the above method apply to?**
-
-1. After selecting the upstream node and before accessing the upstream
-2. Before each retry
-
-For the best performance, the above method first runs in the access phase of OpenResty (APISIX actually selects the upstream node in the access phase) and the method does not overlap with the OpenResty phase of the same name.
-
-### New way to develop: Support for custom balancer
-
-In version 2.8, users can customize the balancer. **The balancer is loading with minimum number of connections, polling, consistency hash, etc.**
-
-Although Apache APISIX already provides a set of balancers, users may need to use balancers that are closely related to the business, such as: need to consider the server room, availability zone, etc. Supporting for custom balancer, users can develop their own balancer and load it via `require("apisix.balancer.your_balancer")`.
-
-Usually a custom balancer requires node to provide data which is from other than the host/port, you can put data in the metadata, for example:
-
-```JSON
-{
-    "nodes": [
-        { "host": "0.0.0.0", "port": 1980, "weight": 1, "metadata": {"b": 1} }
-    ]
-}
-```
-
-## Download
-
-Download Apache APISIX 2.8.0
-
-- Source code: please visit [download page](https://apisix.apache.org/downloads/)
-- Binary installation package: please visit [Installation Guide](https://apisix.apache.org/docs/apisix/how-to-build/)
diff --git a/website/i18n/zh/docusaurus-plugin-content-blog/2021-08-14-contributors-the-golden-metric-of-openSource-projects-en.md b/website/i18n/zh/docusaurus-plugin-content-blog/2021-08-14-contributors-the-golden-metric-of-openSource-projects-en.md
deleted file mode 100644
index 0cc0346..0000000
--- a/website/i18n/zh/docusaurus-plugin-content-blog/2021-08-14-contributors-the-golden-metric-of-openSource-projects-en.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-title: "Contributors — The Golden Metric of OpenSource Projects"
-author: "Lien"
-authorURL: "https://github.com/lilien1010"
-authorImageURL: "https://avatars.githubusercontent.com/u/3814966?v=4"
-keywords:
-- API gateway
-- APISIX
-- Apache APISIX
-- contributor graph
-- open-source project
-description: This article explains why changes in the number of contributors is the golden metric for measuring open source projects. While GitHub already has a number of metrics, such as Star count, Issue count, and PR count, none of these metrics can visually reflect the trends and activity of an open source project over time. So Yiyiyimu proposed new metrics, such as contributor growth and monthly active contributors, and created an open-source tool called the Contributor Graph that a [...]
-tags: [Community]
-draft: true
----
-
-> According to GitHub’s statistics in 2020, over 60 million new repositories were added, and more than 56 million developers worked on OpenSource projects. By 2025, the number of developers working on OpenSource projects on GitHub is expected to exceed 100 million.
-
-<!--truncate-->
-
-> Source:
-> https://github.com/api7/contributor-graph
-
-Behind these fast-growing numbers, open source maintainers did a lot of work on propaganda, article, media, Meetups, etc., to attract more developers for their projects, It’s a lot to take in.
-
-So for developers, how can they find out which one is the best fit for their company among the hundreds of projects on GitHub?
-
-Various indicators of open source projects needs to be considered.
-
-Star number: This is the most direct indicator, it represents the project has attracted the attention of a number of developers, can reflect the level of marketing of the project. If the project has the financial support of commercial companies, a strong PR team, or a water army to paint Star, then this indicator can easily be distorted.
-
-Issue and PR counts: Also GitHub provides the Insights feature, shown in the following image.
-
-![Apache APISIX GitHub Insights](../static/img/blog_img/2021-08-14-1.webp)
-
-You can select the number of new and closed issues and PRs for this open source project, can also filter by period.
-
-The above graph shows the data of Apache APISIX for the last month.
-
-GitHub insights provides a great developer perspective, but it’s not perfect: what about the quality of Issue and PR?
-
-The following graph shows the commit frequency statistics of Apache APISIX from it’s first day, which shows that Apache APISIX has maintained a very stable and continuous activities, but this metric is also a bit thin: you can’t see the data of which developers submitted these commits
-
-![Apache APISIX commits](../static/img/blog_img/2021-08-14-2.webp)
-
-after reading so many indicators, still you can’t get your answer, don’t you think that choosing an open source project is so complicated? Wait!
-
-Is there a “golden metric”, a metric that cannot be mocked by marketing? A core metric that can tell the truth of a project?
-As maintainers and developers of open source projects, we also need such golden metrics to guide us. Therefore, we propose two dimensions, “Contributor Growth” and “Active Contributors”, and open source the statistics and analysis process: https://github.com/api7/contributor-graph, you can also search directly through https://www.apiseven.com/zh/contributor-graph. Here is an example from Apache APISIX.
-
-## Contributor growth
-
-![Apache APISIX contributor growth](../static/img/blog_img/2021-08-14-3.webp)
-
-## Monthly Active Contributors
-
-![Apache APISIX Monthly Active Contributors](../static/img/blog_img/2021-08-14-4.webp)
-
-As you can clearly see from the two tables above, Apache APISIX has seen a steady growth in contributors since its first day, with about 25 contributors participating each month.
-
-## Comparison on Multi Repo
-
-Both the “Contributor Growth” and “Active Contributors” charts support comparisons across multiple repositories. What’s more, we pull the GitHub API to update the charts on a daily/monthly basis, so your repository can always display real-time contributor data by making a one-time copy using the link we provide.
-
-The contributor growth line plot is based on the date of the first commit by each contributor to the project. The contributor growth line chart allows us to see the growth of the community based on the total number of contributors shown on the GitHub homepage.
-
-By showing line plot for multiple repo in the same chart at the same time, we can also visually compare the development of different communities.
-
-![Apache APISIX compare the development of different communities](../static/img/blog_img/2021-08-14-5.webp)
-
-In the graph above, we can see that the number of contributors to Apache APISIX is growing at a very fast rate, and in just two years, the number of contributors has almost caught up with or even surpassed other open source API gateway projects.
-
-The monthly contributor line plot is derived from the number of contributors committing each month.
-
-Compared to the contributor growth line plot, the monthly contributors are a better measure of how the community has grown in a short period of time.
-
-![Apache APISIX monthly contributors compare](../static/img/blog_img/2021-08-14-6.webp)
-
-For example, in the graph above, we can see that Apache APISIX has the highest and most consistent number of monthly contributors of any open source API gateway project.
-
-This explains why Apache APISIX has been able to catch up with its friends in terms of total contributors in such a short period of time since it’s first day of open source.
-
-![Apache APISIX monthly contributors](../static/img/blog_img/2021-08-14-7.webp)
-
-The above graph is comparison of monthly contributors between different MQ community, which is also widely discussed on Twitter. With this chart, we can see that Apache Pulsar is catching up to Apache Kafka in terms of contributors of the month.
-
-## Conclusion
-
-The contributor graph is currently used in Apache APISIX, Apache Skywalking, Apache DolphinScheduler, Apache Openwhisk, Apache ShardingSphere, awesome-docker, TiDB docs-dm, and many other open source projects.
-
-Also, we implemented more features, such as adding “anonymous” contributors, or adding SVN-side contributors after the project was moved from SVN to GitHub.
-
-When we talked about the Contributor Graph, not only did we want to use this tool to produce a visual graph of how active the Apache APISIX community is, we also made this little tool open sourced in the hopes that it will help other open source projects.
-
-You are welcome to use the Contributor Graph to track your community activity, and any requests or questions are welcome in the Contributor Graph GitHub repository.
-
-You can visit the Contributor Graph [repository](https://github.com/api7/contributor-graph).
diff --git a/website/blog/2021-09-29-release-apache-apisix-2.10.md b/website/i18n/zh/docusaurus-plugin-content-blog/2021-09-29-release-apache-apisix-2.10.md
similarity index 100%
rename from website/blog/2021-09-29-release-apache-apisix-2.10.md
rename to website/i18n/zh/docusaurus-plugin-content-blog/2021-09-29-release-apache-apisix-2.10.md
diff --git a/website/blog/2021-09-30-weekly-report.md b/website/i18n/zh/docusaurus-plugin-content-blog/2021-09-30-weekly-report.md
similarity index 100%
copy from website/blog/2021-09-30-weekly-report.md
copy to website/i18n/zh/docusaurus-plugin-content-blog/2021-09-30-weekly-report.md
diff --git a/website/blog/2021-10-01-openEuler.md b/website/i18n/zh/docusaurus-plugin-content-blog/2021-10-01-openEuler.md
similarity index 100%
copy from website/blog/2021-10-01-openEuler.md
copy to website/i18n/zh/docusaurus-plugin-content-blog/2021-10-01-openEuler.md