Add comprehensive documentation for CLICD features and operations

- Introduced Container Management documentation covering lifecycle operations, resource management, and console access.
- Added Dashboard documentation detailing metrics and related APIs.
- Created Host Report documentation summarizing host environment and resource status.
- Included Image Management documentation for template handling and management actions.
- Documented Networking and Routing features including NAT4 and IPv6 management.
- Added Security Alerts documentation outlining alert scenarios and API usage.
- Created Snapshot Management documentation for snapshot operations and scheduling.
- Documented Sub-user management for granting access to specific containers.
- Added Configuration guide detailing runtime settings and security recommendations.
- Created Installation guide for setting up CLICD with requirements and steps.
- Added Introduction and Quick Start guides for new users.
- Documented Upgrade process with version checking and pre-upgrade checklist.
- Created Deployment guide for service exposure and firewall recommendations.
- Added FAQ section addressing common questions and concerns.
- Documented Troubleshooting steps for common issues encountered.

docs/en/developer/architecture.md

@@ -0,0 +1,42 @@
+# Architecture
+
+CLICD consists of a Go backend, a React frontend, and host virtualization capabilities.
+
+## Backend
+
+The backend entry point is `backend/main.go`, and HTTP routes are centralized in `backend/internal/server/server.go`. Main modules:
+
+- `internal/api`: HTTP APIs for the web panel and `/api/v1`.
+- `internal/config`: configuration and SQLite storage.
+- `internal/lxc`: LXC container management.
+- `internal/kvm`: KVM/libvirt virtual machine management.
+- `internal/cli`: command-line management entry point.
+- `internal/server`: embedded frontend assets and HTTP service.
+- `internal/version`: version number.
+
+## Frontend
+
+The frontend entry point is `frontend/src/main.tsx`. Pages live in `frontend/src/pages`, and shared components live in `frontend/src/components`.
+
+Main pages:
+
+- Dashboard: `Dashboard.tsx`
+- Container list: `Containers.tsx`
+- Container details: `ContainerDetail.tsx`
+- Image Management: `ImageManagement.tsx`
+- Security Alerts: `Security.tsx`
+- Snapshot Management: `Snapshots.tsx`
+- Routing Management: `Routing.tsx`
+- API Integration: `ApiIntegration.tsx`
+- Host Report: `HostReport.tsx`
+- Sub-user Management: `SubUserManagement.tsx`
+
+## Frontend Embedding
+
+For production builds, frontend artifacts are placed in `backend/internal/server/web`. The backend serves them through Go embed and returns the SPA entry for non-API routes.
+
+## API Layers
+
+- `/api/*`: web panel and compatibility APIs.
+- `/api/v1/*`: versioned APIs recommended for external automation.
+- WebSSH and WebVNC use short-lived tickets before opening WebSocket connections.

docs/en/developer/build.md

@@ -0,0 +1,42 @@
+# Local Build
+
+## Frontend Build
+
+```bash
+cd frontend
+npm install
+npm run build
+```
+
+Build output is written to `frontend/dist`.
+
+## Backend Build
+
+```bash
+cd backend
+go test ./...
+go build -o ../build/clicd .
+```
+
+To package the embedded web panel, sync the frontend build output into the backend embed directory first.
+
+## One-command Build
+
+The project root provides a build script:
+
+```bash
+bash build.sh
+```
+
+The script chains frontend build, static asset sync, and Go binary build.
+
+## Docs Build
+
+```bash
+cd docs
+npm install
+npm run dev
+npm run build
+```
+
+`npm run dev` starts a local preview, and `npm run build` generates static documentation.

docs/en/developer/release.md

@@ -0,0 +1,44 @@
+# Release Process
+
+CLICD installation and upgrade rely on GitHub Release artifacts. Use semantic version tags such as `v1.1.6`.
+
+## Version Number
+
+Check the version in:
+
+- `backend/internal/version/version.go`
+- `frontend/package.json`
+- Release tag.
+
+## Release Artifacts
+
+The installer first tries to download the Linux AMD64 archive:
+
+```text
+clicd-linux-amd64.tar.gz
+```
+
+In some cases, it may also try the standalone binary:
+
+```text
+clicd-linux-amd64
+```
+
+## Installer Behavior
+
+- `CLICD_VERSION=latest`: use GitHub `releases/latest`.
+- `CLICD_VERSION=vX.Y.Z`: download artifacts from the specified release tag.
+
+Example:
+
+```bash
+CLICD_VERSION=v1.1.6 sh install.sh
+```
+
+## Post-release Verification
+
+- The installer can download the new version.
+- `systemctl status clicd` is healthy.
+- `/api/version` returns the new version.
+- The web panel can load frontend assets.
+- Container list, task queue, and API Key pages open correctly.