diff --git a/docs/core-concepts/common-configuration-mechanisms/overrides.md b/docs/core-concepts/common-configuration-mechanisms/overrides.md
index 01972ad..17a6e32 100644
--- a/docs/core-concepts/common-configuration-mechanisms/overrides.md
+++ b/docs/core-concepts/common-configuration-mechanisms/overrides.md
@@ -10,7 +10,7 @@
 在角色和角色组中，可以使用 `configOverrides` 字段覆盖默认配置。
 
 ```yaml
-apiVersion: hdfs.zncdata.dev/v1alpha1
+apiVersion: hdfs.kubedoop.dev/v1alpha1
 kind: HdfsCluster
 metadata:
   labels:
@@ -48,7 +48,7 @@ spec:
 在角色和角色组中，可以使用 `envOverrides` 字段覆盖默认环境变量。
 
 ```yaml
-apiVersion: hdfs.zncdata.dev/v1alpha1
+apiVersion: hdfs.kubedoop.dev/v1alpha1
 kind: HdfsCluster
 metadata:
   labels:
@@ -82,7 +82,7 @@ spec:
 在角色和角色组中，可以使用 `commandOverrides` 字段覆盖默认命令行参数。
 
 ```yaml
-apiVersion: hdfs.zncdata.dev/v1alpha1
+apiVersion: hdfs.kubedoop.dev/v1alpha1
 kind: HdfsCluster
 metadata:
   labels:
@@ -113,7 +113,7 @@ spec:
 在角色和角色组中，可以使用 `podTemplateOverrides` 字段覆盖默认 pod 模板。
 
 ```yaml
-apiVersion: hdfs.zncdata.dev/v1alpha1
+apiVersion: hdfs.kubedoop.dev/v1alpha1
 kind: HdfsCluster
 metadata:
   labels:
diff --git a/docs/core-concepts/common-configuration-mechanisms/roles-and-role-groups.md b/docs/core-concepts/common-configuration-mechanisms/roles-and-role-groups.md
index 50851d0..3f52665 100644
--- a/docs/core-concepts/common-configuration-mechanisms/roles-and-role-groups.md
+++ b/docs/core-concepts/common-configuration-mechanisms/roles-and-role-groups.md
@@ -16,7 +16,7 @@ title: 角色和角色组
 以 HDFS 为例，HDFS 有多个角色，如 NameNode，DataNode，JournalNode。其中，DataNode 是一个角色，DataNode 的多个实例组成一个角色组。NameNode 也是一个角色，NameNode 的多个实例组成一个角色组。可以根据业务需求为 NameNode 和 DataNode 定义不同配置的角色组。
 
 ```yaml
-apiVersion: hdfs.zncdata.dev/v1alpha1
+apiVersion: hdfs.kubedoop.dev/v1alpha1
 kind: HdfsCluster
 metadata:
   labels:
diff --git a/docs/core-concepts/resources/resource-manage.md b/docs/core-concepts/resources/resource-manage.md
index bc3bdcc..19c7b06 100644
--- a/docs/core-concepts/resources/resource-manage.md
+++ b/docs/core-concepts/resources/resource-manage.md
@@ -34,7 +34,7 @@ CPU 限制是程序运行时的 CPU 资源上限。如果程序使用的 CPU 资
 ### CPU 和内存
 
 ```yaml
-apiVersion: hdfs.zncdata.dev/v1alpha1
+apiVersion: hdfs.kubedoop.dev/v1alpha1
 kind: HdfsCluster
   name: hdfscluster-sample
 spec:
@@ -71,7 +71,7 @@ spec:
 ### 存储配置
 
 ```yaml
-apiVersion: hdfs.zncdata.dev/v1alpha1
+apiVersion: hdfs.kubedoop.dev/v1alpha1
 kind: HdfsCluster
   name: hdfscluster-sample
 spec:
diff --git a/docs/developer-manual/collaboration.md b/docs/developer-manual/collaboration.md
index 1b796de..b7c67bf 100644
--- a/docs/developer-manual/collaboration.md
+++ b/docs/developer-manual/collaboration.md
@@ -5,7 +5,7 @@
 
 ## 行为准则
 
-我们有一份[行为准则](https://github.com/zncdata.dev/zncdata-stack.git/CODE_OF_CONDUCT.md)，希望所有的贡献者都能遵守，请花时间阅读一遍全文以确保你能明白哪些是可以做的，哪些是不可以做的。
+我们有一份[行为准则](https://github.com/kubedoop.dev/zncdata-stack.git/CODE_OF_CONDUCT.md)，希望所有的贡献者都能遵守，请花时间阅读一遍全文以确保你能明白哪些是可以做的，哪些是不可以做的。
 
 ## 分支管理
 
diff --git a/docs/developer-manual/first-commiter.md b/docs/developer-manual/first-commiter.md
index cbd727a..89dcd7e 100644
--- a/docs/developer-manual/first-commiter.md
+++ b/docs/developer-manual/first-commiter.md
@@ -18,7 +18,7 @@ git clone https://github.com/<your_name>/zncdata-stack
 将本地个人仓库和上游仓库关联
 
 ```bash
-git remote add upstream https://github.com/zncdata.dev/zncdata-stack
+git remote add upstream https://github.com/kubedoop.dev/zncdata-stack
 ```
 
 同步最新源代码
diff --git a/docs/quick-start/installation.md b/docs/quick-start/installation.md
index d82fb36..aa18489 100644
--- a/docs/quick-start/installation.md
+++ b/docs/quick-start/installation.md
@@ -25,7 +25,7 @@ curl -sL https://github.com/operator-framework/operator-lifecycle-manager/releas
 OLM 通过 [Subscription](https://olm.operatorframework.io/docs/concepts/subscriptions/) 来管理 Operator 的安装。我们可以通过创建一个 Subscription 来安装 hive-metastore-operator：
 
 ```yaml
-kubectl apply -f https://raw.githubusercontent.com/zncdata.dev/kubedatastack/main/examples/hive/olm-subscriptions.yaml
+kubectl apply -f https://raw.githubusercontent.com/kubedoop.dev/kubedatastack/main/examples/hive/olm-subscriptions.yaml
 ```
 
 验证 operator 的 pod 是否正常运行：
@@ -47,7 +47,7 @@ kubectl create ns hive
 Hive 集群是通过 hive-operator 来管理的，我们可以通过创建一个 HiveCluster 对象来部署一个 Hive Metastore：
 
 ```yaml
-kubectl apply -f https://raw.githubusercontent.com/zncdata.dev/kubedatastack/main/examples/hive/hive-metastore.yaml
+kubectl apply -f https://raw.githubusercontent.com/kubedoop.dev/kubedatastack/main/examples/hive/hive-metastore.yaml
 ```
 
 ## 查看 Hive Metastore
@@ -63,11 +63,11 @@ kubectl exec -it hive-metastore-0 -n hive -- bash
 运行下面命令，清理 hive 集群：
 
 ```bash
-kubectl delete -f https://raw.githubusercontent.com/zncdata.dev/kubedatastack/main/examples/hive/hive-cluster.yaml
+kubectl delete -f https://raw.githubusercontent.com/kubedoop.dev/kubedatastack/main/examples/hive/hive-cluster.yaml
 ```
 
 运行下面命令，清理 operator：
 
 ```bash
-kubectl delete -f https://raw.githubusercontent.com/zncdata.dev/kubedatastack/main/examples/hive/olm-subscriptions.yaml
+kubectl delete -f https://raw.githubusercontent.com/kubedoop.dev/kubedatastack/main/examples/hive/olm-subscriptions.yaml
 ```
diff --git a/docusaurus.config.ts b/docusaurus.config.ts
index 8e2442d..f3cdd5e 100644
--- a/docusaurus.config.ts
+++ b/docusaurus.config.ts
@@ -8,7 +8,7 @@ const config: Config = {
   favicon: 'img/favicon.ico',
 
   // Set the production url of your site here
-  url: 'https://zncdata.dev/',
+  url: 'https://kubedoop.dev/',
   // Set the /<baseUrl>/ pathname under which your site is served
   // For GitHub pages deployment, it is often '/<projectName>/'
   baseUrl: '/',
@@ -68,7 +68,7 @@ const config: Config = {
       apiKey: '45b2515504bc6b7ec063dcef9d22e572',
       indexName: 'zncdata',
       contextualSearch: true,
-      externalUrlRegex: 'zncdata.dev',
+      externalUrlRegex: 'kubedoop.dev',
       // Optional: Replace parts of the item URLs from Algolia. Useful when using the same search index for multiple deployments using a different baseUrl. You can use regexp or string in the `from` param. For example: localhost:3000 vs myCompany.com/docs
       replaceSearchResultPathname: {
         from: '/docs/', // or as RegExp: /\/docs\//
@@ -141,7 +141,7 @@ const config: Config = {
           ],
         },
       ],
-      copyright: `Copyright © ${new Date().getFullYear()} zncdata.dev. Built with Docusaurus.`,
+      copyright: `Copyright © ${new Date().getFullYear()} kubedoop.dev. Built with Docusaurus.`,
     },
     prism: {
       theme: prismThemes.github,
diff --git a/i18n/en/docusaurus-theme-classic/footer.json b/i18n/en/docusaurus-theme-classic/footer.json
index f669b03..5b22192 100644
--- a/i18n/en/docusaurus-theme-classic/footer.json
+++ b/i18n/en/docusaurus-theme-classic/footer.json
@@ -20,7 +20,7 @@
     "description": "The label of footer link with label=GitHub linking to https://github.com/zncdatadev"
   },
   "copyright": {
-    "message": "Copyright © 2024 zncdata.dev. Built with Docusaurus.",
+    "message": "Copyright © 2024 kubedoop.dev. Built with Docusaurus.",
     "description": "The footer copyright"
   }
 }
diff --git a/i18n/zh/docusaurus-theme-classic/footer.json b/i18n/zh/docusaurus-theme-classic/footer.json
index 2bc1758..daf11e3 100644
--- a/i18n/zh/docusaurus-theme-classic/footer.json
+++ b/i18n/zh/docusaurus-theme-classic/footer.json
@@ -20,7 +20,7 @@
     "description": "The label of footer link with label=GitHub linking to https://github.com/zncdatadev"
   },
   "copyright": {
-    "message": "Copyright © 2024 zncdata.dev. Built with Docusaurus.",
+    "message": "Copyright © 2024 kubedoop.dev. Built with Docusaurus.",
     "description": "The footer copyright"
   }
 }
diff --git a/static/CNAME b/static/CNAME
index 4845e6c..8bdccd8 100644
--- a/static/CNAME
+++ b/static/CNAME
@@ -1 +1 @@
-zncdata.dev
\ No newline at end of file
+kubedoop.dev