chore: Merge prod-staging into prod-stable

.gitignore

@@ -8,6 +8,7 @@
 /.pnp
 .pnp.*
 .yarn/*
+.pnpm-store/
 !.yarn/patches
 !.yarn/plugins
 !.yarn/releases
@@ -38,8 +39,13 @@ pnpm-debug.log*
 
 # build outputs
 dist/
+*.pyc
 
 # generated files
 apis/platform.yaml
 build.log
 .examples/
+pages/cli/kraft/
+pages/cli/unikraft/
+pages/cli/unikraft.mdx
+pages/kraftfile/

.vale/styles/config/vocabularies/Unikraft/accept.txt

@@ -25,6 +25,7 @@ FUSE
 ALIAS
 ANAME
 ASCII
+BYOC
 CNAME
 COPY
 DCO
@@ -49,6 +50,7 @@ TOML
 USA
 UTC
 WASI
+WSL
 YAML
 Unikraft Cloud
 POSIX
@@ -58,6 +60,9 @@ EROFS
 CPIO
 CDP
 FTP
+CIDR
+PATCH
+TAP
 
 # ==============================================================================
 # NAMES OF THINGS
@@ -267,6 +272,7 @@ FTP
 (?i)TypeDoc
 (?i)typeof
 (?i)TypeScript
+(?i)UDP
 (?i)ui
 (?i)uncached
 (?i)undefined

Dockerfile

@@ -37,6 +37,7 @@ RUN set -xe; \
     apk --no-cache add \
         ca-certificates \
         git \
+        python3 \
         wget \
     ;
 
@@ -67,6 +68,8 @@ COPY --from=build-kraft-docs /kraftkit/docs/kraft/cloud.mdx /docs/pages/cli/kraf
 COPY --from=build-cli-docs /cli/dist/docs/mdx/unikraft/ /docs/pages/cli/unikraft/
 COPY --from=build-cli-docs /cli/dist/docs/mdx/unikraft.mdx /docs/pages/cli/unikraft.mdx
 
+RUN python3 scripts/update_zudoku_cli.py pages/cli/unikraft zudoku.config.tsx
+
 RUN pnpm run build
 
 ################################################################################

README.md

@@ -12,6 +12,7 @@ Contributions to the documentation are welcome!
   - [Contributing to the docs](#contributing-to-the-docs)
     - [Table of contents](#table-of-contents)
     - [Introduction](#introduction)
+    - [Local development with Docker](#local-development-with-docker)
     - [Code contribution guidelines](#code-contribution-guidelines)
     - [Git commit message guidelines](#git-commit-message-guidelines)
     - [Copyright and license](#copyright-and-license)
@@ -22,17 +23,81 @@ The [`pages/`](./pages) directory contains all the [markdown](https://www.markdo
 
 To maintain consistency and accuracy across all documentation pages, [vale](https://vale.sh/) lints all written prose.
 
+### Local development with Docker
+
+Run the commands in this section from the root of this `docs/` repository.
+
+The checked-in [docker-compose.yaml](./docker-compose.yaml) builds the production site and does not provide hot reload.
+For live editing, first bootstrap the generated CLI, API, and Kraftfile reference content from the existing Docker build:
+
+```bash
+docker build --target build -t ukc-docs-bootstrap .
+
+cid=$(docker create ukc-docs-bootstrap)
+mkdir -p apis pages/cli pages/kraftfile
+docker cp "$cid":/docs/apis/platform.yaml ./apis/platform.yaml
+docker cp "$cid":/docs/pages/cli/unikraft ./pages/cli/unikraft
+docker cp "$cid":/docs/pages/cli/kraft ./pages/cli/kraft
+docker cp "$cid":/docs/pages/cli/unikraft.mdx ./pages/cli/unikraft.mdx
+docker cp "$cid":/docs/pages/kraftfile/v0.7.md ./pages/kraftfile/v0.7.md
+docker rm "$cid"
+```
+
+That bootstrap image pulls the OpenAPI specification from the [unikraft-cloud/openapi](https://github.com/unikraft-cloud/openapi) repository and materializes the API reference consumed by Zudoku at startup.
+If you only need to refresh the API reference, you can fetch that file directly without rebuilding the whole bootstrap image:
+
+```bash
+mkdir -p apis
+curl -fsSL \
+  https://raw.githubusercontent.com/unikraft-cloud/openapi/refs/heads/prod-staging/platform.yaml \
+  -o apis/platform.yaml
+```
+
+Then run the docs site in a bind-mounted Node container:
+
+```bash
+docker run --rm -it \
+  -p 3131:3131 \
+  -e CHOKIDAR_USEPOLLING=true \
+  -v "$PWD":/docs \
+  -v ukc-docs-node-modules:/docs/node_modules \
+  -w /docs \
+  node:24-bookworm \
+  sh -lc 'apt-get update >/dev/null \
+    && apt-get install -y ca-certificates >/dev/null \
+    && corepack enable >/dev/null \
+    && corepack prepare pnpm@10.33.0 --activate >/dev/null \
+    && pnpm install >/dev/null \
+    && pnpm dev -- --host 0.0.0.0'
+```
+
+Open `http://localhost:3131/docs` in your browser.
+Changes under this directory are bind-mounted into the container, and `CHOKIDAR_USEPOLLING=true` enables hot reload reliably from Docker.
+
+The bootstrap step is needed because this repository does not check in the generated `/apis/platform.yaml`, `/cli/unikraft`, `/cli/kraft`, and `/kraftfile/v0.7` source files that Zudoku expects at startup.
+The first run takes longer because Docker builds the bootstrap image, downloads the base Node image, and `pnpm` installs dependencies into the `ukc-docs-node-modules` volume.
+To reset that container-only dependency cache, remove the volume:
+
+```bash
+docker volume rm ukc-docs-node-modules
+```
+
 ### Code contribution guidelines
 
 To make the contribution process as seamless as possible, please follow these requirements:
 
-* Fork the project and make your changes.
-* When you’re ready to create a pull request, be sure to:
-  * Run `make lint` to check all documentation.
-  * Squash your commits into to logical, [atomic commits](https://en.wikipedia.org/wiki/Atomic_commit) (`git rebase -i`).
+- Fork the project and make your changes.
+- When you’re ready to create a pull request, be sure to:
+  - Run `make lint` to check all documentation.
+  - Squash your commits into to logical, [atomic commits](https://en.wikipedia.org/wiki/Atomic_commit) (`git rebase -i`).
     It's okay to force update your pull request with `git push -f`.
-  * Follow the **Git Commit Message Guidelines** below.
-* All commits must be signed off (`git commit -s`) by all authors in order to certify that the contributions are published under the [Developer Certificate of Origin (DCO)](https://wiki.linuxfoundation.org/dco).
+  - Follow the **Git Commit Message Guidelines** below.
+- All commits must be signed off (`git commit -s`) by all authors in order to certify that the contributions are published under the [Developer Certificate of Origin (DCO)](https://wiki.linuxfoundation.org/dco).
+- For consistency, you should follow these soft guidelines for writing docs (besides what `make lint` enforces):
+  - Where `unikraft` commands are used, provide `kraft` commands as well, if applicable.
+  - All code blocks should have 2 spaces indentation for multi-line code, and the language should be specified for syntax highlighting (for example, `bash` for shell commands).
+  - Code blocks used for listing output should have `title=""`, unless context clarifications are needed (e.g., it is tied to a specific CLI in a `CodeTabs`).
+  - Header titles should be concise and descriptive, starting with a capital letter on the first word only.
 
 ### Git commit message guidelines