chore: move doc to en/latest directory (#2443)

Author: AlinsRan

.github/workflows/golangci-lint.yml

@@ -60,7 +60,7 @@ jobs:
           make generate-crd-docs
       - name: Check CRD Docs Diff
         run: |
-          if ! git diff --exit-code -- docs/crd/api.md; then
-            echo "docs/crd/api.md has changed. Please run 'make generate-crd-docs' and commit the updated file."
+          if ! git diff --exit-code -- docs/en/latest/api-reference.md; then
+            echo "docs/en/latest/api-reference.md has changed. Please run 'make generate-crd-docs' and commit the updated file."
             exit 1
           fi

.github/workflows/lint-checker.yml

@@ -96,8 +96,7 @@ jobs:
           markdownlint '**/*.md' \
             --ignore node_modules \
             --ignore CHANGELOG.md \
-            --ignore docs/crd/api.md \
-            --ignore docs/gateway-api.md
+            --ignore docs/en/latest/api-reference.md
   markdown-link-check:
     needs: changes
     if: |

Makefile

@@ -37,7 +37,7 @@ TEST_DIR ?= ./test/e2e/apisix/
 CRD_REF_DOCS_VERSION ?= v0.1.0
 CRD_REF_DOCS ?= $(LOCALBIN)/crd-ref-docs
 CRD_DOCS_CONFIG ?= docs/crd/config.yaml
-CRD_DOCS_OUTPUT ?= docs/crd/api.md
+CRD_DOCS_OUTPUT ?= docs/en/latest/api-reference.md
 
 # go 
 VERSYM="github.com/apache/apisix-ingress-controller/internal/version._buildVersion"

docs/crd/api.md docs/en/latest/api-reference.mddocs/crd/api.md renamed to docs/en/latest/api-reference.md

@@ -31,12 +31,12 @@ The APISIX Ingress Controller is used to manage the APISIX Gateway as either a s
 
 In the traditional deployment approach, APISIX uses etcd as its configuration center, allowing administrators to dynamically manage routes, upstreams, and other resources through RESTful APIs. It supports distributed cluster deployments with real-time configuration synchronization.
 
-![Admin API Architecture](../assets/images/ingress-admin-api-architecture.png)
+![Admin API Architecture](../../../assets/images/ingress-admin-api-architecture.png)
 
 ## Standalone Mode (Experimental)
 
 APISIX runs independently without relying on etcd, supporting two sub-modes - file-driven (managing configuration through conf/apisix.yaml files) and API-driven (storing configuration in memory with full configuration management through the dedicated /apisix/admin/configs endpoint).
 
 This mode is particularly suitable for Kubernetes environments and single-node deployments, where the API-driven memory management approach combines the convenience of traditional Admin API with the simplicity of Standalone mode.
 
-![Standalone Architecture](../assets/images/ingress-standalone-architecture.png)
+![Standalone Architecture](../../../assets/images/ingress-standalone-architecture.png)

docs/concepts/deployment-architecture.md …test/concepts/deployment-architecture.mddocs/concepts/deployment-architecture.md renamed to docs/en/latest/concepts/deployment-architecture.md docs/concepts/deployment-architecture.md renamed to docs/en/latest/concepts/deployment-architecture.md

@@ -68,7 +68,7 @@ Enable additional features not included in the standard Kubernetes Gateway API,
 
 * HTTPRoutePolicy: Configures advanced traffic management and routing policies for HTTPRoute or Ingress resources, enhancing functionality without modifying the original resources.
 
-![Gateway API Extensions Overview](../assets/images/gateway-api-extensions-resources.png)
+![Gateway API Extensions Overview](../../../assets/images/gateway-api-extensions-resources.png)
 
 ## Ingress API Extensions
 
@@ -84,4 +84,4 @@ APISIX Ingress Controller CRDs extend Kubernetes functionality to provide declar
 
 * ApisixTls: Manages SSL/TLS certificates, supporting SNI binding and mutual TLS for secure APISIX gateway connections.
 
-![V2 CRDs Overview](../assets/images/v2-crds-api-resources.png)
+![V2 CRDs Overview](../../../assets/images/v2-crds-api-resources.png)

docs/concepts/gateway-api.md docs/en/latest/concepts/gateway-api.mddocs/concepts/gateway-api.md renamed to docs/en/latest/concepts/gateway-api.md

@@ -46,7 +46,7 @@ There were two main deployment architectures in 1.x.x:
 
 #### Architecture in 2.0.0
 
-![upgrade to 2.0.0 architecture](./assets/images/upgrade-to-architecture.png)
+![upgrade to 2.0.0 architecture](../../assets/images/upgrade-to-architecture.png)
 
 ##### Mock-ETCD Mode Deprecated